CVE-2025-40272: mm/secretmem: fix use-after-free race in fault handler
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.15% (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 1e4643d6628edf9c0047b1f8f5bc574665025acb, 42d486d35a4143cc37fc72ee66edc99d942dd367, 4444767e625da46009fc94a453fd1967b80ba047; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1.
Low priority for now. Upgrade to Linux Linux 1e4643d6628edf9c0047b1f8f5bc574665025acb, 42d486d35a4143cc37fc72ee66edc99d942dd367, 4444767e625da46009fc94a453fd1967b80ba047; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-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: mm/secretmem: fix use-after-free race in fault handler When a page fault occurs in a secret memory file created with `memfd_secret(2)`, the kernel will allocate a new folio for it, mark the underlying page as not-present in the direct map, and add it to the file mapping. If two tasks cause a fault in the same page concurrently, both could end up allocating a folio and removing the page from the direct map, but only one would succeed in adding the folio to the file mapping. The task that failed undoes the effects of its attempt by (a) freeing the folio again and (b) putting the page back into the direct map. However, by doing these two operations in this order, the page becomes available to the allocator again before it is placed back in the direct mapping. If another task attempts to allocate the page between (a) and (b), and the kernel tries to access it via the direct map, it would result in a supervisor not-present page fault. Fix the ordering to restore the direct map before the folio is freed.
- Published
- Dec 6, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
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
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
—
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
- 5.14affected
- 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49 and later · before bb1c19636aedae39360e6fdbcaef4f2bcff25785affected · git
- 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49 and later · before 1e4643d6628edf9c0047b1f8f5bc574665025acbaffected · git
- 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49 and later · before 42d486d35a4143cc37fc72ee66edc99d942dd367affected · git
- 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49 and later · before 52f2d5cf33de9a8f5e72bbb0ed38282ae0bc4649affected · git
- 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49 and later · before 4444767e625da46009fc94a453fd1967b80ba047affected · git
- 1507f51255c9ff07d75909a84e7c0d7f3c4b2f49 and later · before 6f86d0534fddfbd08687fa0f01479d4226bc3c3daffected · git
- before 5.14not affected · semver
- 5.15.197 and later · up to and including 5.15.*not affected · semver
- 6.1.159 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.159-1 | 6.1.159-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.9-1 | 6.17.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40270Dec 6, 2025 · mm, swap: fix potential UAF issue for VMA readahead31Monitor
- ← EarlierCVE-2025-40271Dec 6, 2025 · fs/proc: fix uaf in proc_readdir_de()31Monitor
- Later →CVE-2025-40273Dec 6, 2025 · NFSD: free copynotify stateid in nfs4_free_ol_stateid()35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1e4643d6628edf9c0047b1f8f5bc574665025acb | Vendor (CNA) |
| Linux Linux | 42d486d35a4143cc37fc72ee66edc99d942dd367 | Vendor (CNA) |
| Linux Linux | 4444767e625da46009fc94a453fd1967b80ba047 | Vendor (CNA) |
| Linux Linux | 52f2d5cf33de9a8f5e72bbb0ed38282ae0bc4649 | Vendor (CNA) |
| Linux Linux | 6f86d0534fddfbd08687fa0f01479d4226bc3c3d | Vendor (CNA) |
| Linux Linux | bb1c19636aedae39360e6fdbcaef4f2bcff25785 | Vendor (CNA) |
| azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 | 6.6.117.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.159-1 · Debian:12 | Package 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.
No history yet (it accumulates with the daily EPSS job).
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 researchersFinders, 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.
No nightly-computed relations.
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
- 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)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/42d486d35a4143cc37fc72ee66edc99d942dd367
- git.kernel.org/stable/c/4444767e625da46009fc94a453fd1967b80ba047
- git.kernel.org/stable/c/52f2d5cf33de9a8f5e72bbb0ed38282ae0bc4649
- git.kernel.org/stable/c/6f86d0534fddfbd08687fa0f01479d4226bc3c3d
- git.kernel.org/stable/c/bb1c19636aedae39360e6fdbcaef4f2bcff25785
Vendor advisories and official records. Exploit/PoC links are deliberately left out.