CVE-2026-46157: ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger
Noroxi assessment
Priority: Monitor (action score 31/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.10% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 49f9d048845be874df7997e4b1ce662de450c4b6, 6b01c1bc9a4748ab37548a700a8aaff910e298e6, 901ac0ff15edf9503162e2cf6579bd11a30f1ed4.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 49f9d048845be874df7997e4b1ce662de450c4b6, 6b01c1bc9a4748ab37548a700a8aaff910e298e6, 901ac0ff15edf9503162e2cf6579bd11a30f1ed4 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: 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().
- Published
- May 28, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 0th percentile
- CWE
- CWE-362
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.12.1 and later · before 6.12.88
- linux linux kernel6.13 and later · before 6.18.30
- linux linux kernel6.19 and later · before 7.0.7
- linux linux kernel2.6.12
- linux linux kernel7.1
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
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e718cecb73214f53fe8f48083eb7afe9b0921103affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before c937a494901df8fbfaa5037a5883a7cd44282ea8affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 49f9d048845be874df7997e4b1ce662de450c4b6affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ac3e9b55b7da6f0be51720bd330a0edc1a8b61f1affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6b01c1bc9a4748ab37548a700a8aaff910e298e6affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 901ac0ff15edf9503162e2cf6579bd11a30f1ed4affected · git
- before 2.6.12not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.88-1 | 6.12.88-1 |
| Debian:14 | linux | before 7.0.7-1 | 7.0.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-46152May 28, 2026 · wifi: mac80211: drop stray 'static' from fast-RX rx_result35Monitor
- ← EarlierCVE-2026-46155May 28, 2026 · smb/client: fix out-of-bounds read in smb2_compound_op()36Monitor
- Later →CVE-2026-46159May 28, 2026 · btrfs: fix btrfs_ioctl_space_info() slot_count TOCTOU which can lead to info-leak18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 49f9d048845be874df7997e4b1ce662de450c4b6 | Vendor (CNA) |
| Linux Linux | 6b01c1bc9a4748ab37548a700a8aaff910e298e6 | Vendor (CNA) |
| Linux Linux | 901ac0ff15edf9503162e2cf6579bd11a30f1ed4 | Vendor (CNA) |
| Linux Linux | ac3e9b55b7da6f0be51720bd330a0edc1a8b61f1 | Vendor (CNA) |
| Linux Linux | c937a494901df8fbfaa5037a5883a7cd44282ea8 | Vendor (CNA) |
| Linux Linux | e718cecb73214f53fe8f48083eb7afe9b0921103 | Vendor (CNA) |
| debian:linux | 6.12.88-1 · Debian:13 | Package 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.
No history yet (it accumulates with the daily EPSS job).
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 researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/6b01c1bc9a4748ab37548a700a8aaff910e298e6
- git.kernel.org/stable/c/901ac0ff15edf9503162e2cf6579bd11a30f1ed4
- git.kernel.org/stable/c/ac3e9b55b7da6f0be51720bd330a0edc1a8b61f1
- git.kernel.org/stable/c/c937a494901df8fbfaa5037a5883a7cd44282ea8
- git.kernel.org/stable/c/e718cecb73214f53fe8f48083eb7afe9b0921103
Vendor advisories and official records. Exploit/PoC links are deliberately left out.