CVE-2026-80971

Kernel memory corruption via stale URB pointers

Published Sep 11, 2026 · Updated Sep 11, 2026

Use-after-free in the Linux ALSA bcd2000 driver allows physically proximate attackers to corrupt kernel memory by unplugging an active device. The resource cleanup function frees the input and output URBs without clearing their pointers, so later send or completion paths access and can resubmit freed objects. An open raw MIDI substream and device disconnection are required; the demonstrated consequence is invalid kernel-memory access detected by KASAN.

CVSS severityUnavailable
Unscored
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in the Linux ALSA bcd2000 driver allows physically proximate attackers to corrupt kernel memory by unplugging an active device. The resource cleanup function frees the input and output URBs without clearing their pointers, so later send or completion paths access and can resubmit freed objects. An open raw MIDI substream and device disconnection are required; the demonstrated consequence is invalid kernel-memory access detected by KASAN.

The record

CVE
CVE-2026-80971
Published
Sep 11, 2026
Updated
Sep 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
physical
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 11, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 11, 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.

  1. Affected versionversion=3.16
  2. Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <459d3a64766f5ca2f1886daeaf24582831a5f5ab
  3. Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <7df3194bdb7479cad9199889655a566a2c0c1d1b
  4. Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <b06ebc7fe25a6af4a9f6e4a3d4236a4178ad4b01
  5. Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <eb482a06791d6168beb8c78cc904ac5a5ed96a55

What conditions does exploitation require?

Attack vectorphysical
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=3.16; version=b47a22290d581277be70e8a597824a4985d39e83 <459d3a64766f5ca2f1886daeaf24582831a5f5ab; version=b47a22290d581277be70e8a597824a4985d39e83 <7df3194bdb7479cad9199889655a566a2c0c1d1b; version=b47a22290d581277be70e8a597824a4985d39e83 <b06ebc7fe25a6af4a9f6e4a3d4236a4178ad4b01; version=b47a22290d581277be70e8a597824a4985d39e83 <eb482a06791d6168beb8c78cc904ac5a5ed96a55

Published CVSS scores

No CVSS assessment is available in this record.

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

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