LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43126: ALSA: mixer: oss: Add card disconnect checkpoints

In the Linux kernel, the following vulnerability has been resolved: ALSA: mixer: oss: Add card disconnect checkpoints ALSA OSS mixer layer calls the kcontrol ops rather individually, and pending calls might be not always caught at disconnecting the device. For avoiding the potential UAF scenarios, add sanity checks of the card disconnection at each entry point of OSS mixer accesses. The rwsem is taken just before that check, hence the rest context should be covered by that properly.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A local user may trigger a memory-safety failure in the Linux ALSA OSS mixer while an audio device is disconnecting. Successful exploitation could potentially compromise confidentiality, integrity, and availability. The supplied CVSS score is 7.8, but the source bundle provides no evidence of remote reachability or active exploitation.

Executive priority

Prioritize affected multi-user systems, developer workstations, and hosts running untrusted local workloads. Treat remediation as high priority but below remotely exploitable or confirmed-active threats. Require asset inventory and vendor-version confirmation because the supplied version mapping is incomplete.

Technical view

Pending ALSA OSS mixer kcontrol operations may continue during card disconnection, creating potential use-after-free conditions. The kernel fix adds card-disconnection checks at OSS mixer entry points after acquiring the read-write semaphore. The supplied vector indicates local access, low complexity, low privileges, no user interaction, and potentially high impact.

Likely exposure

Exposure is most likely on Linux systems using affected kernels and the ALSA OSS mixer compatibility layer, particularly where audio devices can disconnect during mixer access. Exact vulnerable version ranges are unclear because the supplied affected-version data is ambiguous; confirm against distribution advisories and the cited stable commits.

Exploitation context

The supplied record is not listed in KEV and contains no evidence of exploitation in the wild. Exploitation would require local low-privileged access according to the CVSS vector. The bundle does not establish exploit reliability, affected configurations, or whether common distributions expose the vulnerable path by default.

Researcher notes

The issue is a potential use-after-free caused by insufficient disconnect checkpoints around individually invoked kcontrol operations. Four stable-kernel commits are cited, apparently covering separate maintained branches. No CWE, reproducer, exploit evidence, or precise branch-to-version mapping is supplied, limiting configuration-specific conclusions.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable cited stable fix.
  • Check Linux distribution advisories for corrected package versions and reboot requirements.
  • Restrict unnecessary local accounts and workloads until affected kernels are updated.
  • Disable unused ALSA OSS compatibility functionality if vendor guidance supports doing so.

Validation and detection

  • Record running kernel versions across Linux endpoints and compare them with vendor advisories.
  • Verify whether ALSA OSS mixer compatibility is enabled or used on each system.
  • Confirm installed kernel sources or packages include the applicable cited fix commit.
  • After updating, verify the corrected kernel is running following any required reboot.
Prepared
Confidence
medium
Sources
6

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-43126 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
5Source 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-43126Attack 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
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 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.