System crash via uninitialized 9P response tag
Published Jun 25, 2024 · Updated May 11, 2026
Improper initialization in affected Linux kernel branches from 3.2 allows local users to crash the system during a failing 9P mount. When p9_check_errors() returns early in p9_client_rpc(), req->rc.tag remains uninitialized, but trace_9p_client_res() still reads and prints it. Exploitation requires the ability to initiate a 9P mount, and the documented consequence is system availability loss without confidentiality or integrity impact.
Summary
What happened
Improper initialization in affected Linux kernel branches from 3.2 allows local users to crash the system during a failing 9P mount. When p9_check_errors() returns early in p9_client_rpc(), req->rc.tag remains uninitialized, but trace_9p_client_res() still reads and prints it. Exploitation requires the ability to initiate a 9P mount, and the documented consequence is system availability loss without confidentiality or integrity impact.
The record
- CVE
- CVE-2024-39301
- Published
- Jun 25, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-665, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=3.2
- Affected versionversion=348b59012e5c6402741d067cf6eeeb6271999d06 <124947855564572713d705a13be7d0c9dae16a17
- Affected versionversion=348b59012e5c6402741d067cf6eeeb6271999d06 <2101901dd58c6da4924bc5efb217a1d83436290b
- Affected versionversion=348b59012e5c6402741d067cf6eeeb6271999d06 <25460d6f39024cc3b8241b14c7ccf0d6f11a736a
- Affected versionversion=348b59012e5c6402741d067cf6eeeb6271999d06 <6c1791130b781c843572fb6391c4a4c5d857ab17
- Affected versionversion=348b59012e5c6402741d067cf6eeeb6271999d06 <72c5d8e416ecc46af370a1340b3db5ff0b0cc867
- Affected versionversion=348b59012e5c6402741d067cf6eeeb6271999d06 <89969ffbeb948ffc159d19252e7469490103011b
- Affected versionversion=348b59012e5c6402741d067cf6eeeb6271999d06 <ca71f204711ad24113e8b344dc5bb8b0385f5672
- Affected versionversion=348b59012e5c6402741d067cf6eeeb6271999d06 <fe5c604053c36c62af24eee8a76407d026ea5163
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