CVE-2026-63795
Last modified
CVE-2026-63795 is a critical-severity vulnerability rated 10/10 on the CVSS scale. 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. EPSS estimates a 0.48% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.0, < 6.1.177 |
| Linux | Linux Kernel | >= 6.2, < 6.6.144 |
| Linux | Linux Kernel | >= 6.7, < 6.12.95 |
| Linux | Linux Kernel | >= 6.13, < 6.18.38 |
| Linux | Linux Kernel | >= 6.19, < 7.1.3 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-63795?
How severe is CVE-2026-63795?
How do I fix CVE-2026-63795?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-63770Glance through 0.8.5 contains an IP address spoofing vulnera…8.2
- CVE-2026-63771Adminer before 5.4.3 contains a cookie injection vulnerabili…7.1
- CVE-2026-6378The Maxi Blocks plugin for WordPress is vulnerable to Stored…6.4
- CVE-2026-6379The WP Photo Album Plus WordPress plugin before 9.1.11.001 d…8.6
- CVE-2026-63793In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63794In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63796In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-63797In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-63798In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-63799In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63800In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-63801In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2026-63795?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
