Kernel heap disclosure via uninitialized status buffer
Published May 28, 2026 · Updated May 28, 2026
Information disclosure in affected Linux Kernel releases allows local users to read one stale kernel-heap byte through LPGETSTATUS. usblp_ctrl_msg() discards the byte count from usb_control_msg(), so a zero-byte printer reply leaves the probe-time statusbuf uninitialized and copy_to_user() returns its sign-extended first byte. Exploitation requires access to the USB printer device, an LPGETSTATUS request, and an attached printer that returns zero bytes; each request discloses one stale byte.
Summary
What happened
Information disclosure in affected Linux Kernel releases allows local users to read one stale kernel-heap byte through LPGETSTATUS. usblp_ctrl_msg() discards the byte count from usb_control_msg(), so a zero-byte printer reply leaves the probe-time statusbuf uninitialized and copy_to_user() returns its sign-extended first byte. Exploitation requires access to the USB printer device, an LPGETSTATUS request, and an attached printer that returns zero bytes; each request discloses one stale byte.
The record
- CVE
- CVE-2026-46167
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-908, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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=0 <6.12.88
- Affected versionversion=0 <6.18.30
- Affected versionversion=0 <6.6.140
- Affected versionversion=0 <7.0.7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6b0e7438e31c74b01514d31ff35c1e688c4baaba
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <762a6ccf391db0d629e590a803a3a2231e17dd3f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a502b997668401a6821501fc98b7f9220f9b6ff2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b38e53cbfb9d84732e5984fbd73e128d592415c5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d06d937b0a4cdb8867f04275c8100a8b943da31a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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