CVE-2026-46151: Linux kernel · usb: usblp: fix heap leak in IEEE 1284 device ID via short response
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 612640abbd9e0947fe8f37aaf0cf324265d7caa4 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:34 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in 612640abbd9e0947fe8f37aaf0cf324265d7caa4, 8247f52d822180e94ccbfdab91613af386a4e34d, 4650cce898fcd0bb8c33e529984687a8caed10c3 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: usb: usblp: fix heap leak in IEEE 1284 device ID via short response usblp_ctrl_msg() collapses the usb_control_msg() return value to 0/-errno, discarding the actual number of bytes transferred. A broken printer can complete the GET_DEVICE_ID control transfer short and the driver has no way to know. usblp_cache_device_id_string() reads the 2-byte big-endian length prefix from the response and trusts it (clamped only to the buffer bounds). The buffer is kmalloc(1024) at probe time. A device that sends exactly two bytes (e.g. 0x03 0xFF, claiming a 1023-byte ID) leaves device_id_string[2..1022] holding stale kmalloc heap. That stale data is then exposed: - via the ieee1284_id sysfs attribute (sprintf("%s", buf+2), truncated at the first NUL in the stale heap), and - via the IOCNR_GET_DEVICE_ID ioctl, which copy_to_user()s the full claimed length regardless of NULs, up to 1021 bytes of uninitialized heap, with the leak size chosen by the device. Fix this up by just zapping the buffer with zeros before each request sent to the device.
References
- git.kernel.org/stable/c/4650cce898fcd0bb8c33e529984687a8caed10c3 (opens in a new tab)
- git.kernel.org/stable/c/612640abbd9e0947fe8f37aaf0cf324265d7caa4 (opens in a new tab)
- git.kernel.org/stable/c/4220d4dd062ea3d3eb056a6cbe0b568e740d20b1 (opens in a new tab)
- git.kernel.org/stable/c/6e29c32a27218f2dcd4a4e9b0b3c5e7728640698 (opens in a new tab)
- git.kernel.org/stable/c/6d8142141c942c0d8e79343cffda9c44bb1f3f4f (opens in a new tab)
- git.kernel.org/stable/c/8247f52d822180e94ccbfdab91613af386a4e34d (opens in a new tab)
- git.kernel.org/stable/c/522d17e93a85575256894212d10e5a1fa6f36529 (opens in a new tab)
- git.kernel.org/stable/c/7a400c6fe3617e31e690e3f7ca37bb335e0498f3 (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)