CVE-2026-46157

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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().

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ac3e9b55b7da6f0be51720bd330a0edc1a8b61f1
generic

ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/901ac0ff15edf9503162e2cf6579bd11a30f1ed4
generic

ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b01c1bc9a4748ab37548a700a8aaff910e298e6
generic

ALSA: pcm: oss: Fix data race at accessing runtime.oss.trigger - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49f9d048845be874df7997e4b1ce662de450c4b6

Vendor Advisories for CVE-2026-46157(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(24)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-09-14ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-09-14ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-14ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-14ubuntu
linuxKernel @ 6.12.88—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.88-1~bpo12+1 (21 versions)6.12.88-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (136 versions)7.0.7-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(23)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 258 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-14 07:14 UTCEG score recompute
  6. 2026-09-14 07:14 UTCVendor advisory
  7. 2026-09-14 07:14 UTCGHSA enrichment
  8. 2026-09-13 02:39 UTCOSV refresh
  9. 2026-09-12 15:01 UTCEPSS rescore
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 09:37 UTCEPSS rescore
  12. 2026-09-10 09:34 UTCEPSS rescore
  13. 2026-09-08 22:00 UTCEPSS rescore
  14. 2026-09-07 16:01 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 13:54 UTCEPSS rescore
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 04:54 UTCEG score recompute
  24. 2026-08-25 04:54 UTCVendor advisory
  25. 2026-08-25 04:53 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 14:42 UTCEG score recompute
  2. 2026-08-23 14:42 UTCVendor advisory
  3. 2026-08-23 14:42 UTCGHSA enrichment
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 15:36 UTCEG score recompute
  7. 2026-08-21 15:36 UTCVendor advisory
  8. 2026-08-21 15:35 UTCGHSA enrichment
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 22:31 UTCVendor advisory
  11. 2026-08-20 22:31 UTCGHSA enrichment
  12. 2026-08-20 10:58 UTCEG score recompute
  13. 2026-08-20 10:58 UTCVendor advisory
  14. 2026-08-20 10:58 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 08:58 UTCVendor advisory
  19. 2026-08-17 08:58 UTCGHSA enrichment
  20. 2026-08-16 15:11 UTCVendor advisory
  21. 2026-08-16 15:11 UTCGHSA enrichment
  22. 2026-08-16 02:39 UTCEG score recompute
  23. 2026-08-16 02:39 UTCVendor advisory
  24. 2026-08-16 02:38 UTCGHSA enrichment
  25. 2026-08-16 02:14 UTCEPSS rescore
  26. 2026-08-15 01:30 UTCEPSS rescore
  27. 2026-08-14 23:37 UTCVendor advisory
  28. 2026-08-14 23:37 UTCGHSA enrichment
  29. 2026-08-14 12:27 UTCVendor advisory
  30. 2026-08-14 12:27 UTCGHSA enrichment
  31. 2026-08-14 01:16 UTCEG score recompute
  32. 2026-08-14 01:16 UTCVendor advisory
  33. 2026-08-14 01:16 UTCGHSA enrichment
  34. 2026-08-13 22:00 UTCEPSS rescore
  35. 2026-08-13 08:02 UTCVendor advisory
  36. 2026-08-13 08:02 UTCGHSA enrichment
  37. 2026-08-12 20:51 UTCEG score recompute
  38. 2026-08-12 20:51 UTCVendor advisory
  39. 2026-08-12 20:51 UTCGHSA enrichment
  40. 2026-08-12 13:51 UTCEPSS rescore
  41. 2026-08-12 09:41 UTCVendor advisory
  42. 2026-08-12 09:41 UTCGHSA enrichment
  43. 2026-08-11 22:30 UTCVendor advisory
  44. 2026-08-11 22:30 UTCGHSA enrichment
  45. 2026-08-11 11:19 UTCVendor advisory
  46. 2026-08-11 11:19 UTCGHSA enrichment
  47. 2026-08-11 00:07 UTCEG score recompute
  48. 2026-08-11 00:07 UTCVendor advisory
  49. 2026-08-11 00:07 UTCGHSA enrichment
  50. 2026-08-11 00:00 UTCEPSS rescore
  51. 2026-08-10 06:28 UTCVendor advisory
  52. 2026-08-10 06:28 UTCGHSA enrichment
  53. 2026-08-09 19:18 UTCEG score recompute
  54. 2026-08-09 19:18 UTCVendor advisory
  55. 2026-08-09 19:17 UTCGHSA enrichment
  56. 2026-08-09 13:46 UTCEPSS rescore
  57. 2026-08-09 08:07 UTCVendor advisory
  58. 2026-08-09 08:07 UTCGHSA enrichment
  59. 2026-08-08 20:56 UTCEG score recompute
  60. 2026-08-08 20:56 UTCVendor advisory
  61. 2026-08-08 20:56 UTCGHSA enrichment
  62. 2026-08-08 16:37 UTCEPSS rescore
  63. 2026-08-08 09:38 UTCVendor advisory
  64. 2026-08-08 09:38 UTCGHSA enrichment
  65. 2026-08-07 22:28 UTCEG score recompute
  66. 2026-08-07 22:28 UTCVendor advisory
  67. 2026-08-07 22:28 UTCGHSA enrichment
  68. 2026-08-07 11:17 UTCVendor advisory
  69. 2026-08-07 11:17 UTCGHSA enrichment
  70. 2026-08-07 00:07 UTCEG score recompute
  71. 2026-08-07 00:07 UTCVendor advisory
  72. 2026-08-07 00:07 UTCGHSA enrichment
  73. 2026-08-06 13:47 UTCEPSS rescore
  74. 2026-08-06 12:04 UTCVendor advisory
  75. 2026-08-06 12:04 UTCGHSA enrichment

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-46157?
CVE-2026-46157 is a high vulnerability published on May 28, 2026. 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…
When was CVE-2026-46157 disclosed?
CVE-2026-46157 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46157 actively exploited?
CVE-2026-46157 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.1% of all scored CVEs.
What is the CVSS score of CVE-2026-46157?
CVE-2026-46157 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46157?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46157, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46157

Explore →

Is Your Infrastructure Affected by CVE-2026-46157?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs