Local service interruption via SPI resource leak
Published May 27, 2026 · Updated May 27, 2026
Resource leak in the Linux Kernel SPI subsystem allows local users to interrupt service through repeated device setup failures. During registration, the drivers/spi/spi.c error path returns after spi_setup() fails without invoking the controller cleanup() callback, leaving setup-allocated resources unreleased. Reachability requires low-privileged local access and a controller path that repeatedly fails SPI device setup; the documented consequence is resource exhaustion and loss of availability.
Summary
What happened
Resource leak in the Linux Kernel SPI subsystem allows local users to interrupt service through repeated device setup failures. During registration, the drivers/spi/spi.c error path returns after spi_setup() fails without invoking the controller cleanup() callback, leaving setup-allocated resources unreleased. Reachability requires low-privileged local access and a controller path that repeatedly fails SPI device setup; the documented consequence is resource exhaustion and loss of availability.
The record
- CVE
- CVE-2026-46083
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 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=3e7c190475d98099231ee8ae486d31b1e2e7535a
- Affected versionversion=4b8b7bc3a726268e5c15d9bafe27863a85fdfc8e
- Affected versionversion=5.10.44 <5.11
- Affected versionversion=5.12.11 <5.13
- Affected versionversion=5.13
- Affected versionversion=5.4.126 <5.5
- Affected versionversion=c7299fea67696db5bd09d924d1f1080d894f92ef <11baa8b24bcb07ae2048f2566a220021d766abe0
- Affected versionversion=c7299fea67696db5bd09d924d1f1080d894f92ef <1e774294b2f944f59e03a04eb438768a4b93c3ce
- Affected versionversion=c7299fea67696db5bd09d924d1f1080d894f92ef <a2c817c629430fbbd54273525b472dac96e2c8fd
- Affected versionversion=c7299fea67696db5bd09d924d1f1080d894f92ef <db357034f7e0cf23f233f414a8508312dfe8fbbe
- Affected versionversion=c7299fea67696db5bd09d924d1f1080d894f92ef <dbcead54b12468d9aa54c0e1f0042d838ec3b0ae
- Affected versionversion=e92ac9263b06c39f05526ad15c90d228cdab60fd
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.
Weakness, pattern, technique
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