Kernel memory corruption via premature oldfid release
Published Jul 19, 2026 · Updated Jul 19, 2026
Use-after-free in the Linux kernel 9p client allows remote attackers to crash systems through a malicious mounted 9p server. The p9_client_walk() clunk_fid error path unconditionally calls p9_fid_put(fid) after a failed non-cloning walk even when fid aliases caller-owned oldfid, prematurely destroying the shared object. Reachability requires an existing 9p mount, a split multi-component walk, and a crafted failure during a later segment; reuse can expose or corrupt kernel memory, escalate privileges, or panic the kernel.
Summary
What happened
Use-after-free in the Linux kernel 9p client allows remote attackers to crash systems through a malicious mounted 9p server. The p9_client_walk() clunk_fid error path unconditionally calls p9_fid_put(fid) after a failed non-cloning walk even when fid aliases caller-owned oldfid, prematurely destroying the shared object. Reachability requires an existing 9p mount, a split multi-component walk, and a crafted failure during a later segment; reuse can expose or corrupt kernel memory, escalate privileges, or panic the kernel.
The record
- CVE
- CVE-2026-63795
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.0
- Affected versionversion=b48dbb998d70b7f48c2ec0a15c3cf47136808e4e <1a3860d46e3eb47dbd60339783cdad7904486b9f
- Affected versionversion=b48dbb998d70b7f48c2ec0a15c3cf47136808e4e <6dbe9443d9f5f7fb6d319a7b77108853ae6c6bea
- Affected versionversion=b48dbb998d70b7f48c2ec0a15c3cf47136808e4e <99c379ca1e221c3d75c7c804ebbf4e5ee37a3070
- Affected versionversion=b48dbb998d70b7f48c2ec0a15c3cf47136808e4e <a61bdcba4f64c2f90d01461913f429ab151f1ca6
- Affected versionversion=b48dbb998d70b7f48c2ec0a15c3cf47136808e4e <a7656d368265d085ac9bb85ab31b0cdb72ad8c38
- Affected versionversion=b48dbb998d70b7f48c2ec0a15c3cf47136808e4e <b84f46179c806450b89821221ea5bd9a1698aba8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo