CVE-2023-53758
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-08

Last updated on: 2025-12-08

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: spi: atmel-quadspi: Free resources even if runtime resume failed in .remove() An early error exit in atmel_qspi_remove() doesn't prevent the device unbind. So this results in an spi controller with an unbound parent and unmapped register space (because devm_ioremap_resource() is undone). So using the remaining spi controller probably results in an oops. Instead unregister the controller unconditionally and only skip hardware access and clk disable. Also add a warning about resume failing and return zero unconditionally. The latter has the only effect to suppress a less helpful error message by the spi core.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-08
Last Modified
2025-12-08
Generated
2026-05-07
AI Q&A
2025-12-08
EPSS Evaluated
2026-05-05
NVD
CVE-2023-53758
EUVD
EUVD-2023-60070
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
atmel quadspi *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability occurs in the Linux kernel's atmel-quadspi driver where an early error exit in the device removal function (atmel_qspi_remove) does not prevent the device from being unbound. This leads to a situation where the SPI controller has an unbound parent and its register space is unmapped, which can cause the system to crash (an oops) if the SPI controller is used afterward. The fix involves unregistering the controller unconditionally and handling hardware access and clock disable differently to avoid this issue.


How can this vulnerability impact me? :

If this vulnerability is triggered, it can cause the SPI controller to be left in an inconsistent state with an unbound parent and unmapped register space, which may lead to system crashes (kernel oops) when the SPI controller is accessed. This can affect system stability and reliability.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart