CVE-2026-45996

Analyzed Analyzed - Analysis Complete

Use-After-Free in Linux Kernel SPI Subsystem

Publication date: 2026-05-27

Last updated on: 2026-06-19

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: spi: imx: fix use-after-free on unbind The SPI subsystem frees the controller and any subsystem allocated driver data as part of deregistration (unless the allocation is device managed). Take another reference before deregistering the controller so that the driver data is not freed until the driver is done with it.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-27

Last Modified

2026-06-19

Generated

2026-07-07

AI Q&A

2026-05-28

EPSS Evaluated

2026-07-05

NVD

CVE-2026-45996

EUVD

EUVD-2026-32292

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.7 (inc) to 6.12.86 (exc)
linux	linux_kernel	From 5.19 (inc) to 6.6.140 (exc)
linux	linux_kernel	From 6.13 (inc) to 6.18.27 (exc)
linux	linux_kernel	From 6.19 (inc) to 7.0.4 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Mitigation Strategies

The vulnerability is fixed in the Linux kernel by correcting the SPI subsystem's handling of controller deregistration to avoid use-after-free errors.

Immediate mitigation steps include updating your Linux kernel to a version that contains this fix.

Executive Summary

This vulnerability is a use-after-free issue in the Linux kernel's SPI subsystem, specifically related to the imx driver. When the SPI controller is deregistered, the driver data allocated by the subsystem is freed. However, the code did not properly take an additional reference before deregistering, which could lead to the driver data being freed while still in use.

Impact Analysis

The use-after-free vulnerability could cause system instability or crashes if the driver attempts to access freed memory. This can lead to unpredictable behavior in the SPI subsystem, potentially affecting devices relying on SPI communication.

Hi! I’m here to help you understand CVE-2026-45996. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70