CVE-2026-46151
Description
A flaw was found in the Linux kernel's USB printer (usblp) driver. A malicious USB printer can exploit a heap leak vulnerability by sending a truncated device ID response. This can lead to the disclosure of up to 1021 bytes of uninitialized kernel memory, potentially exposing sensitive information to an attacker.
Statement
usblp cached the IEEE 1284 device ID in a kmalloc buffer and trusted the two byte length prefix even when the USB control transfer completed short. A malicious or malformed USB printer can return only the length prefix and cause the driver to expose stale heap bytes through the ieee1284_id sysfs attribute or the IOCNR_GET_DEVICE_ID ioctl. For the CVSS the PR:L is used for the paranoid score because a local user needs access to the usblp device node or sysfs data path, or an equivalent USB passthrough context. The main attack model is physical or local USB device access, not network reachability. Impact is kernel information disclosure only, up to roughly 1021 bytes per affected ID read, with no supported write primitive or privilege escalation path.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 2.1 | 5.5 | N/A |
| Attack Vector | Physical | Local | N/A |
| Attack Complexity | Low | Low | N/A |
| Privileges Required | Low | Low | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | Low | None | N/A |
| Integrity Impact | None | None | N/A |
| Availability Impact | None | High | N/A |
Vector
Red Hat: CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Confidentiality,Integrity,Availability,Other
Technical Impact: Varies by Context; Read Application Data
Uninitialized variables usually contain junk, which can not be trusted for consistency. Depending on the context, uninitialized variables could lead to denial of service conditions, or modify control flow in unexpected ways. They could also contain sensitive information that could be leaked if the variable is used in output. In some cases, an attacker can "pre-initialize" the variable using previous actions - i.e., control the contents of the variable - which might enable code execution.
Availability
Technical Impact: Alter Execution Logic; Unexpected State
This can cause a race condition if a lock variable check passes when it should not.
Authorization,Other
Technical Impact: Varies by Context
Strings that are not initialized are especially dangerous, since many functions expect a null at the end -- and only at the end -- of a string.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.