Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2025-21871 | First vendor Publication | 2025-03-27 |
Vendor | Cve | Last vendor Modification | 2025-03-27 |
Security-Database Scoring CVSS v3
Cvss vector : N/A | |||
---|---|---|---|
Overall CVSS Score | NA | ||
Base Score | NA | Environmental Score | NA |
impact SubScore | NA | Temporal Score | NA |
Exploitabality Sub Score | NA | ||
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
In the Linux kernel, the following vulnerability has been resolved: tee: optee: Fix supplicant wait loop OP-TEE supplicant is a user-space daemon and it's possible for it be hung or crashed or killed in the middle of processing an OP-TEE RPC call. It becomes more complicated when there is incorrect shutdown ordering of the supplicant process vs the OP-TEE client application which can eventually lead to system hang-up waiting for the closure of the client application. Allow the client process waiting in kernel for supplicant response to be killed rather than indefinitely waiting in an unkillable state. Also, a normal uninterruptible wait should not have resulted in the hung-task watchdog getting triggered, but the endless loop would. This fixes issues observed during system reboot/shutdown when supplicant got hung for some reason or gets crashed/killed which lead to client getting hung in an unkillable state. It in turn lead to system being in hung up state requiring hard power off/on to recover. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21871 |
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-04-21 05:53:06 |
|
2025-04-21 05:52:40 |
|
2025-04-20 14:17:25 |
|
2025-04-20 14:17:11 |
|
2025-04-20 07:31:08 |
|
2025-04-20 07:30:49 |
|
2025-04-19 14:17:42 |
|
2025-04-19 14:17:27 |
|
2025-04-19 06:17:30 |
|
2025-04-19 06:17:15 |
|
2025-04-18 16:36:05 |
|
2025-04-18 16:35:52 |
|
2025-04-18 03:17:54 |
|
2025-04-18 03:17:37 |
|
2025-04-17 14:17:17 |
|
2025-04-17 14:17:03 |
|
2025-04-17 06:47:43 |
|
2025-04-17 06:47:26 |
|
2025-04-16 14:22:57 |
|
2025-04-16 14:22:43 |
|
2025-04-16 07:05:38 |
|
2025-04-16 07:05:23 |
|
2025-04-15 14:18:48 |
|
2025-04-15 14:18:33 |
|
2025-04-15 05:10:11 |
|
2025-04-15 05:09:57 |
|
2025-04-14 15:57:27 |
|
2025-04-14 15:57:14 |
|
2025-04-14 04:56:54 |
|
2025-04-14 04:56:05 |
|
2025-04-13 15:25:10 |
|
2025-04-13 15:24:56 |
|
2025-04-13 03:26:21 |
|
2025-04-13 03:26:06 |
|
2025-04-12 14:17:25 |
|
2025-04-12 14:17:11 |
|
2025-04-12 04:33:24 |
|
2025-04-12 04:32:58 |
|
2025-04-11 14:45:03 |
|
2025-04-11 14:44:49 |
|
2025-04-11 03:25:15 |
|
2025-04-11 03:25:01 |
|
2025-04-10 14:19:48 |
|
2025-04-10 14:19:34 |
|
2025-04-10 03:35:25 |
|
2025-04-10 03:35:09 |
|
2025-04-09 14:19:35 |
|
2025-04-09 14:19:21 |
|
2025-04-09 03:20:46 |
|
2025-04-09 03:20:31 |
|
2025-04-08 14:16:12 |
|
2025-04-08 14:15:58 |
|
2025-04-08 03:22:08 |
|
2025-04-08 03:21:53 |
|
2025-04-07 14:15:29 |
|
2025-04-07 14:15:15 |
|
2025-04-07 03:16:16 |
|
2025-04-07 03:16:02 |
|
2025-04-06 14:15:20 |
|
2025-04-06 14:15:06 |
|
2025-04-06 03:17:39 |
|
2025-04-06 03:17:25 |
|
2025-04-05 14:18:49 |
|
2025-04-05 14:18:35 |
|
2025-04-05 03:22:35 |
|
2025-04-05 03:22:21 |
|
2025-04-04 14:16:56 |
|
2025-04-04 14:16:42 |
|
2025-04-04 03:15:49 |
|
2025-04-04 03:15:35 |
|
2025-04-03 15:09:52 |
|
2025-04-03 15:09:32 |
|
2025-04-03 03:14:52 |
|
2025-04-03 03:14:38 |
|
2025-04-02 14:15:32 |
|
2025-04-02 14:15:19 |
|
2025-04-02 03:15:44 |
|
2025-04-02 03:15:30 |
|
2025-04-01 14:15:21 |
|
2025-04-01 14:15:07 |
|
2025-03-31 17:20:34 |
|
2025-03-27 17:20:57 |
|