- 8.2HighCVSS base score
- 0.36%Exploitation in 30 daysEPSS · top 70% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: shmem: fix recovery on rename failures maple_tree insertions can fail if we are seriously short on memory; simple_offset_rename() does not recover well if it runs into that. The same goes for simple_offset_rename_exchange(). Moreover, shmem_whiteout() expects that if it succeeds, the caller will progress to d_move(), i.e. that shmem_rename2() won't fail past the successful call of shmem_whiteout(). Not hard to fix, fortunately - mtree_store() can't fail if the index we are trying to store into is already present in the tree as a singleton. For simple_offset_rename_exchange() that's enough - we just need to be careful about the order of operations. For simple_offset_rename() solution is to preinsert the target into the tree for new_dir; the rest can be done without any potentially failing operations. That preinsertion has to be done in shmem_rename2() rather than in simple_offset_rename() itself - otherwise we'd need to deal with the possibility of failure after successful shmem_whiteout().
Timeline
ID reserved
By Linux
Published
- 9 months later
· 9 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.36% · top 70% of all CVEs (9 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.
Affected products
- affected a2e459555c5f9da3e619b7e47a63f98574dc75f1 – < 8fdbc6f9a994eb327868a4aa74a58953f31a2d0f
- affected a2e459555c5f9da3e619b7e47a63f98574dc75f1 – < 4b0fe71fb3965d0db83cdfc2f4fe0b3227d70113
- affected a2e459555c5f9da3e619b7e47a63f98574dc75f1 – < 4642686699a46718d7f2fb5acd1e9d866a9d9cca
- affected a2e459555c5f9da3e619b7e47a63f98574dc75f1 – < e1b4c6a58304fd490124cc2b454d80edc786665c
- affected 6.6
- unaffected < 6.6
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.64 – ≤ 6.12.*
- unaffected 6.18.3 – ≤ 6.18.*
- unaffected 6.19 – ≤ *
References
4
- https://git.kernel.org/stable/c/8fdbc6f9a994eb327868a4aa74a58953f31a2d0f (opens in a new tab)
- https://git.kernel.org/stable/c/4b0fe71fb3965d0db83cdfc2f4fe0b3227d70113 (opens in a new tab)
- https://git.kernel.org/stable/c/4642686699a46718d7f2fb5acd1e9d866a9d9cca (opens in a new tab)
- https://git.kernel.org/stable/c/e1b4c6a58304fd490124cc2b454d80edc786665c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-2281 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-71072)Record last updated .