PF driver crash via stale RVUM revision
Published Jun 3, 2026 · Updated Jun 3, 2026
State-cleanup failure in the octeontx2 AF driver in affected Linux Kernel releases allows local users to crash the PF driver during kexec. The AF shutdown path leaves the RVUM block revision uncleared, so a modular PF driver treats stale hardware state as proof that AF reinitialization finished. The failure requires Marvell OcteonTX2 hardware, modular AF and PF drivers, a kexec reboot, and CAP_SYS_BOOT in the initial user namespace; the consequence is an availability-only driver crash.
Summary
What happened
State-cleanup failure in the octeontx2 AF driver in affected Linux Kernel releases allows local users to crash the PF driver during kexec. The AF shutdown path leaves the RVUM block revision uncleared, so a modular PF driver treats stale hardware state as proof that AF reinitialization finished. The failure requires Marvell OcteonTX2 hardware, modular AF and PF drivers, a kexec reboot, and CAP_SYS_BOOT in the initial user namespace; the consequence is an availability-only driver crash.
The record
- CVE
- CVE-2026-46249
- Published
- Jun 3, 2026
- Updated
- Jun 3, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 3, 2026CVE publishedPublication date reported by the CVE source.
- Jun 3, 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=4.20
- Affected versionversion=54494aa5d1e68945dc79feb7c8461cd382e11d8a <1370736836a18b5e0cd74bcc9cffe11d21f1fe79
- Affected versionversion=54494aa5d1e68945dc79feb7c8461cd382e11d8a <2d2d574309e3ae84ee794869a5da8b4c38753a94
- Affected versionversion=54494aa5d1e68945dc79feb7c8461cd382e11d8a <57821d1436ba1c6a6973aa32d54166fdec35558c
- Affected versionversion=54494aa5d1e68945dc79feb7c8461cd382e11d8a <7d56ba306e93d04696718963fb4cda2883ee7585
- Affected versionversion=54494aa5d1e68945dc79feb7c8461cd382e11d8a <8b5ed7c5417b7013d35b6f2507dab739013ba1a9
- Affected versionversion=54494aa5d1e68945dc79feb7c8461cd382e11d8a <9769a09afda20a006b528b9e723effcae45965b2
- Affected versionversion=54494aa5d1e68945dc79feb7c8461cd382e11d8a <9c3398e5b3a914b74276d44ab54c49123b89c61a
- Affected versionversion=54494aa5d1e68945dc79feb7c8461cd382e11d8a <b7605b9301abc18fbbf2b0e23fdd281fc768955d
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Weakness, pattern, technique
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