Kernel crash via tampered EEPROM length
Published Jul 10, 2025 · Updated May 11, 2026
Out-of-bounds write in the Linux p54 driver before 6.16 allows physically proximate attackers to crash the kernel using a malicious USB device. The p54_rx_eeprom_readback function passes the device-controlled eeprom->v1.len or eeprom->v2.len directly to memcpy, allowing the copy to exceed the allocated priv->eeprom buffer. The path is reached only after p54 firmware is uploaded, and that proprietary firmware is absent from most distributions by default; successful exploitation causes a kernel crash or panic.
Summary
What happened
Out-of-bounds write in the Linux p54 driver before 6.16 allows physically proximate attackers to crash the kernel using a malicious USB device. The p54_rx_eeprom_readback function passes the device-controlled eeprom->v1.len or eeprom->v2.len directly to memcpy, allowing the copy to exceed the allocated priv->eeprom buffer. The path is reached only after p54 firmware is uploaded, and that proprietary firmware is absent from most distributions by default; successful exploitation causes a kernel crash or panic.
The record
- CVE
- CVE-2025-38348
- Published
- Jul 10, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1200, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=2.6.28
- Affected versionversion=7cb770729ba895f73253dfcd46c3fcba45d896f9 <0e4dc150423b829c35cbcf399481ca11594fc036
- Affected versionversion=7cb770729ba895f73253dfcd46c3fcba45d896f9 <12134f79e53eb56b0b0b7447fa0c512acf6a8422
- Affected versionversion=7cb770729ba895f73253dfcd46c3fcba45d896f9 <1f7f8168abe8cbe845ab8bb557228d44784a6b57
- Affected versionversion=7cb770729ba895f73253dfcd46c3fcba45d896f9 <6d05390d20f110de37d051a3e063ef0a542d01fb
- Affected versionversion=7cb770729ba895f73253dfcd46c3fcba45d896f9 <714afb4c38edd19a057d519c1f9c5d164b43de94
- Affected versionversion=7cb770729ba895f73253dfcd46c3fcba45d896f9 <9701f842031b825e2fd5f22d064166f8f13f6e4d
- Affected versionversion=7cb770729ba895f73253dfcd46c3fcba45d896f9 <da1b9a55ff116cb040528ef664c70a4eec03ae99
- Affected versionversion=7cb770729ba895f73253dfcd46c3fcba45d896f9 <f39b2f8c1549a539846e083790fad396ef6cd802
What conditions does exploitation require?
What is affected?
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