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.
| Vendor | Product | Versions |
|---|---|---|
| linux | linux kernel | b48dbb998d70b7f48c2ec0a15c3cf47136808e4e, b48dbb998d70b7f48c2ec0a15c3cf47136808e4e, b48dbb998d70b7f48c2ec0a15c3cf47136808e4e, b48dbb998d70b7f48c2ec0a15c3cf47136808e4e, b48dbb998d70b7f48c2ec0a15c3cf47136808e4e, b48dbb998d70b7f48c2ec0a15c3cf47136808e4e, 6.0 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| open source | open source linux kernel | cert_advisory | 90% |
Loading…
Updated severity from HIGH to CRITICAL and corrected affected versions to 6.1.176, 6.6.143, 6.12.94, 6.18.37, and 7.1.2
Article clarifies this is CVE-2026-63795, a use-after-free/refcount underflow vulnerability affecting net/9p/client.c. Updated severity to HIGH with estimated CVSS 7.5 and added CWE-416 (use-after-free) and CWE-190 (integer overflow) classifications.
Initial creation
