Kernel crash via SPI teardown use-after-free
Published Apr 22, 2026 · Updated Apr 22, 2026
Use-after-free in Linux Kernel branches from 4.10 allows local users to crash the kernel during an SPI controller teardown. The fsl_lpspi driver delays controller unregistration until after fsl_lpspi_remove() synchronously releases its DMA channels, so an in-flight transfer dereferences freed state. Triggering the fault requires local access to the affected SPI device and a transfer concurrent with device removal; the published trace demonstrates a NULL-pointer kernel crash.
Summary
What happened
Use-after-free in Linux Kernel branches from 4.10 allows local users to crash the kernel during an SPI controller teardown. The fsl_lpspi driver delays controller unregistration until after fsl_lpspi_remove() synchronously releases its DMA channels, so an in-flight transfer dereferences freed state. Triggering the fault requires local access to the affected SPI device and a transfer concurrent with device removal; the published trace demonstrates a NULL-pointer kernel crash.
The record
- CVE
- CVE-2026-31485
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 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.10
- Affected versionversion=5314987de5e5f5e38436ef4a69328bc472bbd63e <15650dfbaeeb14bcaaf053b93cf631db8d465300
- Affected versionversion=5314987de5e5f5e38436ef4a69328bc472bbd63e <adb25339b66112393fd6892ceff926765feb5b86
- Affected versionversion=5314987de5e5f5e38436ef4a69328bc472bbd63e <b341c1176f2e001b3adf0b47154fc31589f7410e
- Affected versionversion=5314987de5e5f5e38436ef4a69328bc472bbd63e <ca4483f36ac1b62e69f8b182c5b8f059e0abecfb
- Affected versionversion=5314987de5e5f5e38436ef4a69328bc472bbd63e <d5d01f24bc6fbde40b4e567ef9160194b61267bc
- Affected versionversion=5314987de5e5f5e38436ef4a69328bc472bbd63e <e3fd54f8b0317fbccc103961ddd660f2a32dcf0b
- Affected versionversion=5314987de5e5f5e38436ef4a69328bc472bbd63e <e89e2b97253c124d37bf88e96e5e8ce5c3aeeec3
- Affected versionversion=5314987de5e5f5e38436ef4a69328bc472bbd63e <fbe6f40caeebb0b1ea9dfedc259124c1d3cda7a6
What conditions does exploitation require?
What is affected?
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