LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46157: ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger Currently the runtime.oss.trigger field may be accessed concurrently without protection, which may lead to the data race. And, in this case, it may lead to more severe problem because it's a bit field; as writing the data, it may overwrite other bit fields as well, which confuses the operation completely, as spotted by fuzzing. Fix it by covering runtime.oss.trigger bit fled also with the existing params_lock mutex in both snd_pcm_oss_get_trigger() and snd_pcm_oss_poll().

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in Linux’s ALSA OSS-compatible audio code can corrupt related control bits when accessed concurrently. A local, low-privileged user could potentially cause serious confidentiality, integrity, or availability impact. The supplied record rates it CVSS 7.8, but does not establish real-world exploitation.

Executive priority

Prioritize systems with untrusted local users, shared hosting, workstations, or exposed multi-user workloads. Treat remediation as high priority during normal emergency patching, while recognizing that exploitation requires local access and is not reported as active.

Technical view

Concurrent, unprotected access to runtime.oss.trigger in snd_pcm_oss_get_trigger() and snd_pcm_oss_poll() can race. Because trigger is a bit field, a write may overwrite adjacent fields and disrupt operation. The upstream fix protects these accesses with the existing params_lock mutex.

Likely exposure

Exposure is limited to Linux systems running an affected kernel where the ALSA PCM OSS functionality is present and reachable by a local low-privileged user. The supplied version data names affected releases but does not provide reliable distribution package or backport mapping.

Exploitation context

The CVSS vector requires local access, low privileges, low complexity, and no user interaction. Fuzzing identified the faulty behavior. The supplied record is not in KEV and provides no evidence of active exploitation, public weaponization, or a working proof of concept.

Researcher notes

The core issue is unsynchronized access to a bit field, creating risk beyond an isolated stale value because adjacent bits may be overwritten. Four stable-kernel fix commits are supplied. Exact affected ranges, distribution backports, exploitability conditions, and demonstrated security outcomes remain incomplete in the provided evidence.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable upstream fix or documented backport.
  • Check Linux distribution advisories for package-specific fixed versions before scheduling deployment.
  • Restrict unnecessary local account access while affected systems await remediation.
  • Assess whether ALSA PCM OSS compatibility is required on exposed systems.

Validation and detection

  • Inventory Linux kernel and distribution package versions across endpoints, servers, and appliances.
  • Confirm whether ALSA PCM OSS functionality is present and accessible to unprivileged local users.
  • Verify vendor package changelogs or source trees include one of the referenced fixes.
  • After updating, confirm the running kernel matches the remediated package.
Prepared
Confidence
medium
Sources
6

Public sources used

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-46157 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-46157Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 6.12.88, 6.18.30, 7.0.7, 7.1affected
Weakness

CWE details

No CWE listed

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