CVE-2026-46167
Heap Leak in Linux Kernel USBLP Driver via LPGETSTATUS
Publication date: 2026-05-28
Last updated on: 2026-05-28
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved by fixing the usblp driver in the Linux kernel to properly initialize the memory buffer at probe time, preventing uninitialized heap leaks via the LPGETSTATUS ioctl.
To mitigate this vulnerability immediately, you should update your Linux kernel to a version that includes this fix.
How can this vulnerability impact me? :
This vulnerability can lead to unintended disclosure of kernel heap memory contents to user space. An attacker controlling a malicious USB printer or able to manipulate printer responses could exploit this flaw to read uninitialized memory, potentially exposing sensitive information residing in kernel memory.
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's usblp driver, which handles USB printers. The issue arises because a memory buffer (statusbuf) allocated during device probe is not initialized before use. When the LPGETSTATUS ioctl command is called, if a malicious printer responds with zero bytes, the driver may leak uninitialized heap memory to the user by copying stale data from this buffer. This happens because the driver collapses the return value of usb_control_msg() and does not properly detect short or incorrect responses, leading to potential exposure of leftover kernel memory.
The fix involves zeroing out the memory buffer when it is allocated, ensuring that if a short read occurs later, no sensitive or stale data is leaked.