Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-46167: usb: usblp: fix uninitialized heap leak via LPGETSTATUS ioctl

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 087d97342c100138ea7d75a50977c9c2319f957b, 0f7c41314ebf17049917a452684db371babf711a, 6b0e7438e31c74b01514d31ff35c1e688c4baaba; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 087d97342c100138ea7d75a50977c9c2319f957b, 0f7c41314ebf17049917a452684db371babf711a, 6b0e7438e31c74b01514d31ff35c1e688c4baaba; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 28, 2026
Updated
Oct 15, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-46167

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.12.1 and later · before 5.10.258
  • linux linux kernel5.11 and later · before 5.15.209
  • linux linux kernel5.16 and later · before 6.1.175
  • linux linux kernel6.2 and later · before 6.6.140
  • linux linux kernel6.7 and later · before 6.12.88
  • linux linux kernel6.13 and later · before 6.18.30
  • linux linux kernel6.19 and later · before 7.0.7
  • linux linux kernel2.6.12
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.12affected
    • 7.1 and laternot affected · original_commit_for_fix
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 0f7c41314ebf17049917a452684db371babf711aaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before cf24991619be317e2769310b4a367bf4a04b82bcaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 087d97342c100138ea7d75a50977c9c2319f957baffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before d06d937b0a4cdb8867f04275c8100a8b943da31aaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a502b997668401a6821501fc98b7f9220f9b6ff2affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 762a6ccf391db0d629e590a803a3a2231e17dd3faffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6b0e7438e31c74b01514d31ff35c1e688c4baabaaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b38e53cbfb9d84732e5984fbd73e128d592415c5affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.176-16.1.176-1
Debian:13linuxbefore 6.12.88-16.12.88-1
Debian:14linuxbefore 7.0.7-17.0.7-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-46165May 28, 2026 · openvswitch: vport: fix self-deadlock on release of tunnel ports
    22Monitor
  • ← EarlierCVE-2026-46166May 28, 2026 · wifi: mac80211: use safe list iteration in radar detect work
    35Monitor
  • Later →CVE-2026-46168May 28, 2026 · mptcp: fix scheduling with atomic in timestamp sockopt
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux087d97342c100138ea7d75a50977c9c2319f957bVendor (CNA)
Linux Linux0f7c41314ebf17049917a452684db371babf711aVendor (CNA)
Linux Linux6b0e7438e31c74b01514d31ff35c1e688c4baabaVendor (CNA)
Linux Linux762a6ccf391db0d629e590a803a3a2231e17dd3fVendor (CNA)
Linux Linuxa502b997668401a6821501fc98b7f9220f9b6ff2Vendor (CNA)
Linux Linuxb38e53cbfb9d84732e5984fbd73e128d592415c5Vendor (CNA)
Linux Linuxcf24991619be317e2769310b4a367bf4a04b82bcVendor (CNA)
Linux Linuxd06d937b0a4cdb8867f04275c8100a8b943da31aVendor (CNA)
azl3 kernel 6.6.139.1-1 on Azure Linux 3.06.6.141.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-5298927 days apartnvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers
    39Monitor
  • CVE-2026-5322528 days apartsctp: fix uninit-value in __sctp_rcv_asconf_lookup()
    36Monitor
  • CVE-2026-5317028 days apartaccel/ethosu: reject DMA commands with uninitialized length
    35Monitor
  • CVE-2026-4313922 days apartxfrm6: fix uninitialized saddr in xfrm6_get_saddr()
    34Monitor
  • CVE-2026-4329120 days apartnet: nfc: nci: Fix parameter validation for packet data
    33Monitor
  • CVE-2026-4345620 days apartbonding: fix type confusion in bond_setup_by_slave()
    31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records