PatchSiren cyber security CVE debrief
CVE-2026-45883 Linux CVE debrief
A resource leak vulnerability in the Linux kernel's SCA3000 industrial I/O (IIO) driver has been resolved. The issue occurred in the `sca3000_probe()` function where `spi->irq` allocated via `request_threaded_irq()` was not released if `iio_device_register()` subsequently failed. The fix adds proper return value checking and error handling to ensure cleanup occurs on registration failure.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-05-27
- Original CVE updated
- 2026-06-25
- Advisory published
- 2026-05-27
- Advisory updated
- 2026-06-25
Who should care
System administrators running Linux kernels with SCA3000 accelerometer support; embedded systems using SCA3000 sensors via SPI; security teams tracking kernel driver stability issues
Technical summary
The SCA3000 IIO driver in the Linux kernel contained a resource leak in its probe function. When `iio_device_register()` failed after `request_threaded_irq()` had successfully allocated an IRQ for the SPI device, the IRQ was not freed, leading to resource leakage. The resolution adds proper error handling to jump to a common cleanup path when registration fails, ensuring `spi->irq` is released appropriately. This is a defensive coding fix that prevents resource exhaustion in error scenarios during device initialization.
Defensive priority
low
Recommended defensive actions
- Apply kernel updates containing the referenced stable branch commits when available from your Linux distribution
- Monitor vendor security advisories for kernel package updates addressing CVE-2026-45883
- Review systems using SCA3000 accelerometer sensors via SPI interface for potential resource exhaustion under error conditions
- Consider rebooting systems after kernel updates to ensure patched driver is loaded
Evidence notes
The vulnerability description indicates this is a resource leak fix in kernel driver probe code. The fix ensures IRQ resources are properly released when device registration fails, preventing resource exhaustion in error paths. Multiple stable kernel branch commits are referenced, indicating backports to supported kernel versions.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-45883 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-45883
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-45883 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-45883
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/103ac8e3a7f345a0966ef582b8a874ac31a92c7c
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/40c860ece22542178cddcf01b08644bcdbc597b3
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/517d9f2b963089b3d64c23accf7920d77f5a30c8
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/55e13abf22c27a3b0ab5cf941dd07a2d9786736c
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/597d749c5180f3e351837e851a6131b140324e9f
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/62b44ebc1f2c71db3ca2d4737c52e433f6f03038
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/84d3c396d8ae73c24dececfcc4e544ea09311e32
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.