CVE-2026-46167

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.

Is your site exposed to CVE-2026-46167?

Run a free security scan — no signup, results in seconds.

EPSS — Exploit Prediction

0.0013

Probability of exploitation

0.03%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other References

https://git.kernel.org/stable/c/087d97342c100138ea7d75a50977c9c2319f957b https://git.kernel.org/stable/c/0f7c41314ebf17049917a452684db371babf711a https://git.kernel.org/stable/c/6b0e7438e31c74b01514d31ff35c1e688c4baaba https://git.kernel.org/stable/c/762a6ccf391db0d629e590a803a3a2231e17dd3f https://git.kernel.org/stable/c/a502b997668401a6821501fc98b7f9220f9b6ff2 https://git.kernel.org/stable/c/b38e53cbfb9d84732e5984fbd73e128d592415c5 https://git.kernel.org/stable/c/cf24991619be317e2769310b4a367bf4a04b82bc https://git.kernel.org/stable/c/d06d937b0a4cdb8867f04275c8100a8b943da31a

Frequently Asked Questions

What is CVE-2026-46167? +

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.

How do I check if I'm vulnerable to CVE-2026-46167? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.