CVE-2026-46226
Analyzed Analyzed - Analysis Complete
SPI Controller Deregistration Flaw in Linux Kernel

Publication date: 2026-05-28

Last updated on: 2026-06-10

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: spi: fsl: fix controller deregistration Make sure to deregister the controller before releasing underlying resources like DMA during driver unbind.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-28
Last Modified
2026-06-10
Generated
2026-06-17
AI Q&A
2026-05-28
EPSS Evaluated
2026-06-16
NVD
EUVD
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.13 (inc) to 6.18.32 (exc)
linux linux_kernel From 6.7 (inc) to 6.12.90 (exc)
linux linux_kernel From 6.19 (inc) to 7.0.9 (exc)
linux linux_kernel From 4.3 (inc) to 6.6.140 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability relates to the Linux kernel's SPI (Serial Peripheral Interface) driver for Freescale (fsl) controllers. The issue was that the controller was not properly deregistered before releasing underlying resources such as DMA (Direct Memory Access) during the driver unbind process. This could lead to improper resource management.

Impact Analysis

If the controller is not deregistered correctly before releasing resources, it could cause system instability or resource conflicts. This might lead to crashes or unpredictable behavior in systems using the affected Linux kernel SPI driver.

Mitigation Strategies

To mitigate this vulnerability, ensure that the Linux kernel is updated to a version where the issue with the spi: fsl controller deregistration is fixed.

Specifically, make sure the controller is properly deregistered before releasing underlying resources like DMA during driver unbind.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-46226. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart