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.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can leave systems stuck during reboot or shutdown when the OP-TEE supplicant process hangs, crashes, or is killed during a trusted execution RPC. The practical business risk is availability: affected devices may require hard power cycling to recover.
Executive priority
Treat as a targeted availability risk for OP-TEE-enabled Linux systems rather than a broad internet-facing emergency. Patch during normal kernel maintenance, with higher priority for devices where hard power recovery is costly or remote recovery is limited.
Technical view
The OP-TEE TEE driver could wait indefinitely for a userspace supplicant response, leaving a client process stuck in an unkillable kernel wait. The fix changes the wait behavior so the client can be killed instead of looping forever and triggering hung-task conditions.
Likely exposure
Exposure is most likely on Linux systems using OP-TEE trusted execution support. The source metadata lists Linux kernel stable lines and Debian LTS references, but package-level exposure depends on kernel version, configuration, and vendor backports.
Exploitation context
The provided sources do not show active exploitation, public weaponization, or CISA KEV listing. The described failure mode is operational disruption caused by supplicant crash, kill, or shutdown ordering issues, not confirmed remote compromise.
Researcher notes
Evidence supports an availability bug in the kernel OP-TEE supplicant wait path. CVSS and CWE data are absent in the bundle. Avoid assuming exploitability beyond inducing or encountering supplicant failure unless additional vendor analysis confirms an attack path.
Mitigation direction
Apply vendor kernel updates containing the referenced stable fixes.
Prioritize OP-TEE-enabled embedded, appliance, and edge systems.
Check Debian LTS advisories if running affected Debian kernels.
Review reboot and shutdown reliability on managed device fleets.
Monitor vendor advisories for backported package versions.
Validation and detection
Inventory Linux systems with OP-TEE support enabled.
Compare running kernel packages with vendor fixed advisories.
Review logs for hung-task watchdog or shutdown hangs involving OP-TEE.
Confirm updated kernels include the referenced stable commit lineage.
Test controlled reboot and shutdown after patching.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21871 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
11Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 27, 2025, 13:38 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.