LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43279: ALSA: usb-audio: Add sanity check for OOB writes at silencing

In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Add sanity check for OOB writes at silencing At silencing the playback URB packets in the implicit fb mode before the actual playback, we blindly assume that the received packets fit with the buffer size. But when the setup in the capture stream differs from the playback stream (e.g. due to the USB core limitation of max packet size), such an inconsistency may lead to OOB writes to the buffer, resulting in a crash. For addressing it, add a sanity check of the transfer buffer size at prepare_silent_urb(), and stop the data copy if the received data overflows. Also, report back the transfer error properly from there, too. Note that this doesn't fix the root cause of the playback error itself, but this merely covers the kernel Oops.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux USB audio handling can write beyond a kernel buffer when mismatched capture and playback packet sizes are processed in implicit-feedback mode. The documented outcome is a kernel crash. Systems using affected kernels and relevant USB audio configurations deserve prompt patching, especially shared endpoints or devices exposed to untrusted local users or peripherals.

Executive priority

Treat this as a high-priority kernel stability and memory-safety update for systems using USB audio. Prioritize shared workstations, audio appliances, and endpoints accessible to untrusted local users or peripherals. Broader emergency action is not supported by the available exploitation evidence.

Technical view

ALSA usb-audio's prepare_silent_urb() trusted received packet sizes while silencing playback URBs. A capture/playback packet-size mismatch could cause an out-of-bounds transfer-buffer write and kernel Oops. The fix adds a buffer-size check, stops overflowing copies, and propagates the transfer error. It does not correct the underlying playback incompatibility.

Likely exposure

Exposure requires an affected Linux kernel and the ALSA USB-audio implicit-feedback playback path with inconsistent capture and playback packet sizing. The supplied affected-version data is ambiguous, so determine exposure using distribution package guidance and the referenced stable commits rather than version strings alone.

Exploitation context

The CVSS vector describes a local, low-complexity condition requiring low privileges and no user interaction. The supplied sources document crashes but provide no evidence of public exploitation, reliable code execution, or attacks in the wild. CVE-2026-43279 is not identified as KEV in the bundle.

Researcher notes

The record assigns CVSS 7.8 with confidentiality, integrity, and availability impacts rated high, but its narrative only establishes an out-of-bounds write and kernel crash. Do not infer practical privilege escalation or code execution without further evidence. The fix contains the Oops while leaving the underlying playback error unresolved.

Mitigation direction

  • Upgrade to a distribution kernel containing the applicable referenced Linux stable fix.
  • Use distribution or vendor guidance to map fixed commits to supported kernel packages.
  • Reboot after installation and confirm the patched kernel is running.
  • Until patched, limit untrusted access to affected endpoints and unnecessary USB audio use.

Validation and detection

  • Inventory running kernels on systems using ALSA USB audio.
  • Check package changelogs or kernel sources for the applicable referenced fix commit.
  • Confirm prepare_silent_urb() checks transfer-buffer bounds and returns transfer errors.
  • Review kernel logs for USB-audio-related Oops or crashes; absence does not prove safety.
  • After patching, test normal USB audio playback and capture in a controlled environment.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-43279 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
8Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-43279Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc75a8a7ae565d7cd9baa87a504ba9162e355b4b0, c75a8a7ae565d7cd9baa87a504ba9162e355b4b0, c75a8a7ae565d7cd9baa87a504ba9162e355b4b0, c75a8a7ae565d7cd9baa87a504ba9162e355b4b0, c75a8a7ae565d7cd9baa87a504ba9162e355b4b0, c75a8a7ae565d7cd9baa87a504ba9162e355b4b0, c75a8a7ae565d7cd9baa87a504ba9162e355b4b0unaffected
LinuxLinux3.5, 0, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.