- 8.1HighCVSS base score
- 0.53%Exploitation in 30 daysEPSS · top 55% 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: nfsd: fix fcache_disposal UAF by inlining dispose state into nfsd_net nfsd_file_dispose_list_delayed() defers fput() to nfsd service threads via a per-net freeme queue, preventing the shrinker and GC worker from bearing the cost of closing files (see ffb402596147). However, the queue lives in a separately-allocated struct nfsd_fcache_disposal that is freed by nfsd_free_fcache_disposal_net() during per-net teardown. The global shrinker, laundrette, and fsnotify callbacks can still be inside nfsd_file_dispose_list_delayed() dereferencing that pointer, causing a use-after-free. Inline the spinlock and freeme list directly into struct nfsd_net (as fcache_dispose_lock and fcache_dispose_list), eliminating the separately allocated struct nfsd_fcache_disposal entirely. These fields now have the same lifetime as the net namespace itself, so there is no dangling pointer to chase. nfsd_file_cache_start_net() now just initializes the inline fields and cannot fail due to allocation. nfsd_file_cache_shutdown_net() drains the inline list directly instead of freeing a separate struct. The alloc/free helpers are removed.
Timeline
ID reserved
By Linux
Published
- 49 days later
· 49 days 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.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.53% · top 55% of all CVEs (11 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.
Affected products
- affected 1463b38e7cf34d4cc60f41daff459ad807b2e408 – < 41fe0e804bbf1110c0aba2ebdfc729efb240d8a6
- affected 1463b38e7cf34d4cc60f41daff459ad807b2e408 – < e6c3a43d0a41f03abae3764fc82a59369360c7e0
- affected 1463b38e7cf34d4cc60f41daff459ad807b2e408 – < 9c8ac7c2b9b150e13b7ad0d0fae54f17747dce67
- affected 1463b38e7cf34d4cc60f41daff459ad807b2e408 – < ba0ee9e04b7a0356c28d5a2fe445db675d24e572
- affected 1463b38e7cf34d4cc60f41daff459ad807b2e408 – < cadc9036d5a8209f89e7026ddba7cfb1c716b03c
- affected 1463b38e7cf34d4cc60f41daff459ad807b2e408 – < bbf13732f74351d21c5e0e8dd9bd8e1c48dc35d4
- affected e8f923e1e9fcc0832a12c8a2461792e5a9544c03
- affected 3bc94fb44f10ef852723e1aeaac6794c5ab16aec
- affected 5.10.220 – < 5.11
- affected 5.15.154 – < 5.16
- affected 5.17
- unaffected < 5.17
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/41fe0e804bbf1110c0aba2ebdfc729efb240d8a6 (opens in a new tab)
- https://git.kernel.org/stable/c/e6c3a43d0a41f03abae3764fc82a59369360c7e0 (opens in a new tab)
- https://git.kernel.org/stable/c/9c8ac7c2b9b150e13b7ad0d0fae54f17747dce67 (opens in a new tab)
- https://git.kernel.org/stable/c/ba0ee9e04b7a0356c28d5a2fe445db675d24e572 (opens in a new tab)
- https://git.kernel.org/stable/c/cadc9036d5a8209f89e7026ddba7cfb1c716b03c (opens in a new tab)
- https://git.kernel.org/stable/c/bbf13732f74351d21c5e0e8dd9bd8e1c48dc35d4 (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-76594 (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-2026-89682)Record last updated .