Kernel memory corruption via unbind work race
Published May 28, 2026 · Updated May 28, 2026
Use-after-free in the Linux kernel's mpc52xx SPI driver allows local users to corrupt kernel memory during driver unbind. The mpc52xx_spi_remove function cancels state-machine work before freeing its IRQs, so an interrupt can queue that work again after cancellation and leave teardown code using released state. Reachability requires local low-privileged access and a bound mpc52xx SPI device; exploitation can expose or modify kernel memory or crash the system.
Summary
What happened
Use-after-free in the Linux kernel's mpc52xx SPI driver allows local users to corrupt kernel memory during driver unbind. The mpc52xx_spi_remove function cancels state-machine work before freeing its IRQs, so an interrupt can queue that work again after cancellation and leave teardown code using released state. Reachability requires local low-privileged access and a bound mpc52xx SPI device; exploitation can expose or modify kernel memory or crash the system.
The record
- CVE
- CVE-2026-46219
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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=373d55a47dc662e5e30d12ad5d334312f757c1f1
- Affected versionversion=5.10.231 <5.11
- Affected versionversion=5.15.174 <5.16
- Affected versionversion=5.4.287 <5.5
- Affected versionversion=6.1.120 <6.2
- Affected versionversion=6.12.5 <6.12.90
- Affected versionversion=6.13
- Affected versionversion=6.6.66 <6.6.140
- Affected versionversion=90b72189de2cddacb26250579da0510b29a8b82b <ee52da0dd83ebcd89ecbbe2660c57b15a25489f2
- Affected versionversion=984836621aad98802d92c4a3047114cf518074c8 <6c3e413919a12627d04a31a4a5fccb9fc129bb02
- Affected versionversion=984836621aad98802d92c4a3047114cf518074c8 <706b3dc2ac7a998c55e14b3fd2e8f934c367e6e0
- Affected versionversion=984836621aad98802d92c4a3047114cf518074c8 <bbcd6dd8e9f264440eaf6167382bf404911c1c46
- Affected versionversion=cd5106c77d6d6828aa82449f01f4eb436d602a21
- Affected versionversion=d0cde3911cf24e1bcdd4caa1d1b9ef57589db5a1
- Affected versionversion=e0c6ce8424095c2da32a063d3fc027494c689817
- Affected versionversion=f65d85bc1ffd8a2c194bb2cd65e35ed3648ddd59 <bb6b50f709c5a01906ff72a07fdc070bb3357188
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