Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-21871: tee: optee: Fix supplicant wait loop

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0180cf0373f84fff61b16f8c062553a13dd7cfca, 21234efe2a8474a6d2d01ea9573319de7858ce44, 3eb4911364c764572e9db4ab900a57689a54e8ce.

Low priority for now. Upgrade to Linux Linux 0180cf0373f84fff61b16f8c062553a13dd7cfca, 21234efe2a8474a6d2d01ea9573319de7858ce44, 3eb4911364c764572e9db4ab900a57689a54e8ce or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Mar 27, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-21871

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.12 and later · before 5.4.291
  • linux linux kernel5.5 and later · before 5.10.235
  • linux linux kernel5.11 and later · before 5.15.179
  • linux linux kernel5.16 and later · before 6.1.130
  • linux linux kernel6.2 and later · before 6.6.80
  • linux linux kernel6.7 and later · before 6.12.17
  • linux linux kernel6.13 and later · before 6.13.5
  • linux linux kernel6.14

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.12affected
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before 3eb4911364c764572e9db4ab900a57689a54e8ceaffected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before 0180cf0373f84fff61b16f8c062553a13dd7cfcaaffected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before c0a9a948159153be145f9471435695373904ee6daffected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before ec18520f5edc20a00c34a8c9fdd6507c355e880faffected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before d61cc1a435e6894bfb0dd3370c6f765d2d12825daffected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before fd9d2d6124c293e40797a080adf8a9c237efd8b8affected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before 21234efe2a8474a6d2d01ea9573319de7858ce44affected · git
    • 4fb0a5eb364d239722e745c02aef0dbd4e0f1ad2 and later · before 70b0d6b0a199c5a3ee6c72f5e61681ed6f759612affected · git
    • before 4.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.133-16.1.133-1
Debian:13linuxbefore 6.12.17-16.12.17-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-21868Mar 27, 2025 · net: allow small head cache usage with large MAX_SKB_FRAGS values
    22Monitor
  • ← EarlierCVE-2025-21869Mar 27, 2025 · powerpc/code-patching: Disable KASAN report during patching via temporary mm
    31Monitor
  • Later →CVE-2024-58090Mar 27, 2025 · sched/core: Prevent rescheduling when interrupts are disabled
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0180cf0373f84fff61b16f8c062553a13dd7cfcaVendor (CNA)
Linux Linux21234efe2a8474a6d2d01ea9573319de7858ce44Vendor (CNA)
Linux Linux3eb4911364c764572e9db4ab900a57689a54e8ceVendor (CNA)
Linux Linux70b0d6b0a199c5a3ee6c72f5e61681ed6f759612Vendor (CNA)
Linux Linuxc0a9a948159153be145f9471435695373904ee6dVendor (CNA)
Linux Linuxd61cc1a435e6894bfb0dd3370c6f765d2d12825dVendor (CNA)
Linux Linuxec18520f5edc20a00c34a8c9fdd6507c355e880fVendor (CNA)
Linux Linuxfd9d2d6124c293e40797a080adf8a9c237efd8b8Vendor (CNA)
debian:linux6.1.133-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-31448391 days apartext4: avoid infinite loops caused by residual data
    37Monitor
  • CVE-2026-52933454 days apartio_uring/poll: fix signed comparison in io_poll_get_ownership()
    31Monitor
  • CVE-2026-23451372 days apartbonding: prevent potential infinite loop in bond_header_parse()
    30Monitor
  • CVE-2026-31552393 days apartwifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom
    30Monitor
  • CVE-2026-46052426 days apartceph: only d_add() negative dentries when they are unhashed
    30Monitor
  • CVE-2026-64148479 days apartpds_core: fix error handling in pdsc_devcmd_wait
    30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records