CVE-2026-637959p: avoid putting oldfid in p9_client_walk() error path
- 10.0CriticalCVSS base score
- 0.61%Exploitation in 30 daysEPSS · top 50% 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: 9p: avoid putting oldfid in p9_client_walk() error path When p9_client_walk() is called with clone set to false, fid aliases oldfid. If the walk subsequently fails after the request has been sent, the error path jumps to clunk_fid, which currently calls p9_fid_put(fid) unconditionally. This drops a reference to oldfid even though ownership of oldfid remains with the caller. If this is the last reference, oldfid can be clunked and destroyed while the caller still expects it to be valid. A later use or put of oldfid can then trigger a use-after-free or refcount underflow. Fix this by only putting fid in the clunk_fid error path when it does not alias oldfid, matching the existing guard in the error path below. This can be triggered when a multi-component walk is split into multiple p9_client_walk() calls and a later non-cloning walk fails. A reproducer and refcount warning logs are available on request.
Timeline
ID reserved
By Linux
Published
- 3 months later
· 3 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 | Critical10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Critical10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.61% · top 50% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 10.0.
Affected products
- affected b48dbb998d70b7f48c2ec0a15c3cf47136808e4e – < 99c379ca1e221c3d75c7c804ebbf4e5ee37a3070
- affected b48dbb998d70b7f48c2ec0a15c3cf47136808e4e – < b84f46179c806450b89821221ea5bd9a1698aba8
- affected b48dbb998d70b7f48c2ec0a15c3cf47136808e4e – < a61bdcba4f64c2f90d01461913f429ab151f1ca6
- affected b48dbb998d70b7f48c2ec0a15c3cf47136808e4e – < 6dbe9443d9f5f7fb6d319a7b77108853ae6c6bea
- affected b48dbb998d70b7f48c2ec0a15c3cf47136808e4e – < a7656d368265d085ac9bb85ab31b0cdb72ad8c38
- affected b48dbb998d70b7f48c2ec0a15c3cf47136808e4e – < 1a3860d46e3eb47dbd60339783cdad7904486b9f
- affected 6.0
- unaffected < 6.0
- unaffected 6.1.177 – ≤ 6.1.*
- unaffected 6.6.144 – ≤ 6.6.*
- unaffected 6.12.95 – ≤ 6.12.*
- unaffected 6.18.38 – ≤ 6.18.*
- unaffected 7.1.3 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/99c379ca1e221c3d75c7c804ebbf4e5ee37a3070 (opens in a new tab)
- https://git.kernel.org/stable/c/b84f46179c806450b89821221ea5bd9a1698aba8 (opens in a new tab)
- https://git.kernel.org/stable/c/a61bdcba4f64c2f90d01461913f429ab151f1ca6 (opens in a new tab)
- https://git.kernel.org/stable/c/6dbe9443d9f5f7fb6d319a7b77108853ae6c6bea (opens in a new tab)
- https://git.kernel.org/stable/c/a7656d368265d085ac9bb85ab31b0cdb72ad8c38 (opens in a new tab)
- https://git.kernel.org/stable/c/1a3860d46e3eb47dbd60339783cdad7904486b9f (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-45461 (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-63795)Record last updated .