Kernel heap corruption via unchecked device PBA
Published Dec 12, 2025 · Updated Dec 12, 2025
Out-of-bounds access in the Linux kernel sddr55 USB storage driver allows physically proximate attackers to corrupt kernel heap memory. After each write, sddr55 reads new_pba from the device status packet and indexes pba_to_lba[] without checking it against the capacity-derived block count. Physical attachment of a malicious SDDR55-compatible USB storage device and a write through the driver are required; the resulting out-of-range mapping access corrupts kernel memory.
Summary
What happened
Out-of-bounds access in the Linux kernel sddr55 USB storage driver allows physically proximate attackers to corrupt kernel heap memory. After each write, sddr55 reads new_pba from the device status packet and indexes pba_to_lba[] without checking it against the capacity-derived block count. Physical attachment of a malicious SDDR55-compatible USB storage device and a write through the driver are required; the resulting out-of-range mapping access corrupts kernel memory.
The record
- CVE
- CVE-2025-40345
- Published
- Dec 12, 2025
- Updated
- Dec 12, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1200
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 12, 2025CVE publishedPublication date reported by the CVE source.
- Dec 12, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <04a8a6393f3f2f471e05eacca33282dd30b01432
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <26e9b5da3231da7dc357b363883b5b7b51a64092
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5ebe8d479aaf4f41ac35e6955332304193c646f6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a20f1dd19d21dcb70140ea5a71b1f8cbe0c7e68f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <aa64e0e17e3a5991a25e6a46007770c629039869
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b59d4fda7e7d0aff1043a7f742487cb829f5aac1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d00a6c04a502cd52425dbf35588732c652b16490
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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