Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80827: USB: serial: option: fix slab OOB read in interrupt URB callback

Noroxi assessment

Priority: Monitor (action score 0/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.19% (FIRST EPSS).
  • Fixed version: Linux Linux 030e3a73d3c3aa67c44454649e984d6383cdb7d3, 060db7d48af1e650643c8b8319111a9ea2ce4486, 2ef5560387f2c0713cee975be2b24b281bd90f3e; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.

Low priority for now. Upgrade to Linux Linux 030e3a73d3c3aa67c44454649e984d6383cdb7d3, 060db7d48af1e650643c8b8319111a9ea2ce4486, 2ef5560387f2c0713cee975be2b24b281bd90f3e; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.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: serial: option: fix slab OOB read in interrupt URB callback The interrupt URB buffer is allocated in setup_port_interrupt_in() based on the endpoint's wMaxPacketSize: buffer_size = usb_endpoint_maxp(epd); port->interrupt_in_buffer = kmalloc(buffer_size, GFP_KERNEL); When a USB device declares wMaxPacketSize = 8 on its interrupt IN endpoint, the buffer is allocated from kmalloc-8 cache (exactly 8 bytes). If the device sends a short packet (actual_length < wMaxPacketSize), the URB completes with status == 0 and the callback proceeds to read: data[sizeof(struct usb_ctrlrequest)] which evaluates to data[8], accessing 1 byte beyond the allocated 8-byte buffer. This results in a slab out-of-bounds read. Fix this by adding the missing bounds check: first verify that the actual length is large enough to contain the struct usb_ctrlrequest header before accessing req_pkt->bRequestType and req_pkt->bRequest, and then verify that there is an additional byte for the modem signal state before reading data[sizeof(struct usb_ctrlrequest)] inside the conditional. Use sizeof(*req_pkt) instead of sizeof(struct usb_ctrlrequest) for consistency. [ johan: use dev_err(); split signals declaration and initialisation ]

—No exploit Fix available
Published
Sep 4, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
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-80827

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

—

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
    • 58cfe9113e485f7e04bd0eac4fc4251b330af501 and later · before fbe60fd2abc8a5561f39719a41ad9a01b5d8e567affected · git
    • 58cfe9113e485f7e04bd0eac4fc4251b330af501 and later · before 94e5525697b9e91ddc4071129874120a50a4f342affected · git
    • 58cfe9113e485f7e04bd0eac4fc4251b330af501 and later · before 6b8cf5422c7e96ed5b22a8368eff663f3f98b8ecaffected · git
    • 58cfe9113e485f7e04bd0eac4fc4251b330af501 and later · before 030e3a73d3c3aa67c44454649e984d6383cdb7d3affected · git
    • 58cfe9113e485f7e04bd0eac4fc4251b330af501 and later · before 060db7d48af1e650643c8b8319111a9ea2ce4486affected · git
    • 58cfe9113e485f7e04bd0eac4fc4251b330af501 and later · before 2ef5560387f2c0713cee975be2b24b281bd90f3eaffected · git
    • 58cfe9113e485f7e04bd0eac4fc4251b330af501 and later · before a72a13c83a652516a0e469d275b81d29a7429049affected · git
    • 58cfe9113e485f7e04bd0eac4fc4251b330af501 and later · before d762aef4eba354066be21a5d88eb2066e282f4c9affected · git
    • 58cfe9113e485f7e04bd0eac4fc4251b330af501 and later · before 885d802f544ca7bfa8f3984d94233cce715bb6b3affected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.1.13-17.1.13-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80825Sep 4, 2026 · wifi: mt76: mt7925: ensure tx headroom in usb_sdio_tx_prepare_skb
    0Monitor
  • ← EarlierCVE-2026-80826Sep 4, 2026 · USB: c67x00: fix use-after-free in c67x00_add_iso_urb()
    0Monitor
  • Later →CVE-2026-80828Sep 4, 2026 · ALSA: usb-audio: Complete cleanup after system-resume errors
    0Monitor

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 Linux030e3a73d3c3aa67c44454649e984d6383cdb7d3Vendor (CNA)
Linux Linux060db7d48af1e650643c8b8319111a9ea2ce4486Vendor (CNA)
Linux Linux2ef5560387f2c0713cee975be2b24b281bd90f3eVendor (CNA)
Linux Linux6b8cf5422c7e96ed5b22a8368eff663f3f98b8ecVendor (CNA)
Linux Linux885d802f544ca7bfa8f3984d94233cce715bb6b3Vendor (CNA)
Linux Linux94e5525697b9e91ddc4071129874120a50a4f342Vendor (CNA)
Linux Linuxa72a13c83a652516a0e469d275b81d29a7429049Vendor (CNA)
Linux Linuxd762aef4eba354066be21a5d88eb2066e282f4c9Vendor (CNA)
Linux Linuxfbe60fd2abc8a5561f39719a41ad9a01b5d8e567Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

Credits

All researchers

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.

No nightly-computed relations.

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).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records