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 — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
1.0%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 14, 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 65× 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 164 total refreshes for this CVE.

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

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 June 14, 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 1.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.