Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38349: eventpoll: don't decrement ep refcount while still holding the ep mutex

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/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.18% (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 263f5de8302a6f2f136d392e5d3f8b1edf922857, 5.15.222, 521e9ff0b67c66a17d6f9593dfccafaa984aae4c; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.

Low priority for now. Upgrade to Linux Linux 263f5de8302a6f2f136d392e5d3f8b1edf922857, 5.15.222, 521e9ff0b67c66a17d6f9593dfccafaa984aae4c; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1 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: eventpoll: don't decrement ep refcount while still holding the ep mutex Jann Horn points out that epoll is decrementing the ep refcount and then doing a mutex_unlock(&ep->mtx); afterwards. That's very wrong, because it can lead to a use-after-free. That pattern is actually fine for the very last reference, because the code in question will delay the actual call to "ep_free(ep)" until after it has unlocked the mutex. But it's wrong for the much subtler "next to last" case when somebody *else* may also be dropping their reference and free the ep while we're still using the mutex. Note that this is true even if that other user is also using the same ep mutex: mutexes, unlike spinlocks, can not be used for object ownership, even if they guarantee mutual exclusion. A mutex "unlock" operation is not atomic, and as one user is still accessing the mutex as part of unlocking it, another user can come in and get the now released mutex and free the data structure while the first user is still cleaning up. See our mutex documentation in Documentation/locking/mutex-design.rst, in particular the section [1] about semantics: "mutex_unlock() may access the mutex structure even after it has internally released the lock already - so it's not safe for another context to acquire the mutex and assume that the mutex_unlock() context is not using the structure anymore" So if we drop our ep ref before the mutex unlock, but we weren't the last one, we may then unlock the mutex, another user comes in, drops _their_ reference and releases the 'ep' as it now has no users - all while the mutex_unlock() is still accessing it. Fix this by simply moving the ep refcount dropping to outside the mutex: the refcount itself is atomic, and doesn't need mutex protection (that's the whole _point_ of refcounts: unlike mutexes, they are inherently about object lifetimes).

Published
Jul 18, 2025
Updated
Oct 3, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-38349

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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.

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

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

    • 6.4affected
    • f2451def095c1743adcfcb0cb5dadc86034e162a and later · before 263f5de8302a6f2f136d392e5d3f8b1edf922857affected · git
    • a1f93804449d13f97dabd4b996817de4bf1ed67a and later · before b0821ec902d39062356cb644c16e17a705d1c9f5affected · git
    • 58c9b016e12855286370dfb704c08498edbc857a and later · before 521e9ff0b67c66a17d6f9593dfccafaa984aae4caffected · git
    • 58c9b016e12855286370dfb704c08498edbc857a and later · before 6dee745bd0aec9d399df674256e7b1ecdb615444affected · git
    • 58c9b016e12855286370dfb704c08498edbc857a and later · before 605c18698ecfa99165f36b7f59d3ed503e169814affected · git
    • 58c9b016e12855286370dfb704c08498edbc857a and later · before 8c2e52ebbe885c7eeaabd3b7ddcdc1246fc400d2affected · git
    • 5.15.209 and later · before 5.15.222affected · semver
    • 6.1.175 and later · before 6.1.178affected · semver
    • before 6.4not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:9kernelbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.26.1.el9_75.14.0-611.26.1.el9_7

+96

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-38345Jul 10, 2025 · ACPICA: fix acpi operand cache leak in dswstate.c
    22Monitor
  • ← EarlierCVE-2025-38346Jul 10, 2025 · ftrace: Fix UAF when lookup kallsym after ftrace disabled
    31Monitor
  • Later →CVE-2025-38350Jul 19, 2025 · net/sched: Always pass notifications when child class becomes empty
    31Monitor

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 Linux263f5de8302a6f2f136d392e5d3f8b1edf922857Vendor (CNA)
Linux Linux5.15.222Vendor (CNA)
Linux Linux521e9ff0b67c66a17d6f9593dfccafaa984aae4cVendor (CNA)
Linux Linux6.1.178Vendor (CNA)
Linux Linux605c18698ecfa99165f36b7f59d3ed503e169814Vendor (CNA)
Linux Linux6dee745bd0aec9d399df674256e7b1ecdb615444Vendor (CNA)
Linux Linux8c2e52ebbe885c7eeaabd3b7ddcdc1246fc400d2Vendor (CNA)
Linux Linuxb0821ec902d39062356cb644c16e17a705d1c9f5Vendor (CNA)
azl3 kernel 6.6.96.2-2 on Azure Linux 3.06.6.104.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.26.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.41-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-611.26.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+5

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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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.

References

All records