CVE-2026-46167: Linux kernel · usb: usblp: fix uninitialized heap leak via LPGETSTATUS ioctl
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d06d937b0a4cdb8867f04275c8100a8b943da31a : 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 d06d937b0a4cdb8867f04275c8100a8b943da31a, cf24991619be317e2769310b4a367bf4a04b82bc, b38e53cbfb9d84732e5984fbd73e128d592415c5 +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 uninitialized heap leak via LPGETSTATUS ioctl Just like in a previous problem in this driver, usblp_ctrl_msg() will collapse the usb_control_msg() return value to 0/-errno, discarding the actual number of bytes transferred. Ideally that short command should be detected and error out, but many printers are known to send "incorrect" responses back so we can't just do that. statusbuf is kmalloc(8) at probe time and never filled before the first LPGETSTATUS ioctl. usblp_read_status() requests 1 byte. If a malicious printer responds with zero bytes, *statusbuf is one byte of stale kmalloc heap, sign-extended into the local int status, which the LPGETSTATUS path then copy_to_user()s directly to the ioctl caller. Fix this all by just zapping out the memory buffer when allocated at probe time. If a later call does a short read, the data will be identical to what the device sent it the last time, so there is no "leak" of information happening.
References
- git.kernel.org/stable/c/0f7c41314ebf17049917a452684db371babf711a (opens in a new tab)
- git.kernel.org/stable/c/cf24991619be317e2769310b4a367bf4a04b82bc (opens in a new tab)
- git.kernel.org/stable/c/087d97342c100138ea7d75a50977c9c2319f957b (opens in a new tab)
- git.kernel.org/stable/c/d06d937b0a4cdb8867f04275c8100a8b943da31a (opens in a new tab)
- git.kernel.org/stable/c/a502b997668401a6821501fc98b7f9220f9b6ff2 (opens in a new tab)
- git.kernel.org/stable/c/762a6ccf391db0d629e590a803a3a2231e17dd3f (opens in a new tab)
- git.kernel.org/stable/c/6b0e7438e31c74b01514d31ff35c1e688c4baaba (opens in a new tab)
- git.kernel.org/stable/c/b38e53cbfb9d84732e5984fbd73e128d592415c5 (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)