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

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

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~rc5-1~exp1 (335 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 (133 versions)7.0.7-1—

Weakness Classification(1)

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

All Vendor Advisories

(22)

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 4× in last 7d / 85× 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 243 total refreshes for this CVE.

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

Related CVEs(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