CVE-2025-21871
Last modified
CVE-2025-21871 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.12, < 5.4.291 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.235 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.179 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.130 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.80 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.17 | — |
| Linux | Linux Kernel | >= 6.13, < 6.13.5 | — |
| Linux | Linux Kernel | 6.14 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-21871?
How severe is CVE-2025-21871?
How do I fix CVE-2025-21871?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-21865In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21866In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21867In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-21868In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21869In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-21870In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21872In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21873In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21874In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21875In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21876In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21877In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-21871?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
