CVE-2026-23191

HIGHPre-NVD 7.87.0▼
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-02-14. NVD baseline CVSS 7.8; sources differ by 0.8.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ALSA: aloop: Fix racy access at PCM trigger

The PCM trigger callback of aloop driver tries to check the PCM state and stop the stream of the tied substream in the corresponding cable. Since both check and stop operations are performed outside the cable lock, this may result in UAF when a program attempts to trigger frequently while opening/closing the tied stream, as spotted by fuzzers.

For addressing the UAF, this patch changes two things:

  • It covers the most of code in loopback_check_format() with
cable->lock spinlock, and add the proper NULL checks. This avoids already some racy accesses.
  • In addition, now we try to check the state of the capture PCM stream
that may be stopped in this function, which was the major pain point leading to UAF.

CVSS v3
7.8
EG Score
7.0(medium)
EPSS
1.7%
KEV
Not listed

Published

February 14, 2026

Last Modified

June 16, 2026

Advisory Details (3)

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

ALSA: aloop: Fix racy access at PCM trigger - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: aloop: Fix racy access at PCM trigger - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/826af7fa62e347464b1b4e0ba2fe19a92438084f
generic

ALSA: aloop: Fix racy access at PCM trigger - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5727ccf9d19ca414cb76d9b647883822e2789c2e

Vendor Advisories for CVE-2026-23191(15)

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

Patch Availability(20)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-06-12ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-06-12ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-06-12ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-12ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-06-12ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-06-12ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-06-12ubuntu
redhatkernel-0:4.18.0-477.143.1.el8_82026-05-20redhat
redhatkernel-0:3.10.0-1160.149.1.el72026-05-07redhat
redhatkernel-rt-0:3.10.0-1160.149.1.rt56.1301.el72026-05-07redhat
redhatkernel-rt-0:5.14.0-70.178.1.rt21.250.el9_02026-05-06redhat
redhatkernel-0:4.18.0-372.191.1.el8_62026-05-06redhat
redhatkernel-0:5.14.0-70.178.1.el9_02026-05-06redhat
redhatkernel-0:5.14.0-427.124.1.el9_42026-05-06redhat
redhatkernel-rt-0:5.14.0-284.169.1.rt14.454.el9_22026-05-06redhat
redhatkernel-0:5.14.0-284.169.1.el9_22026-05-05redhat
redhatkernel-0:4.18.0-553.120.1.el8_102026-04-20redhat
redhatkernel-rt-0:4.18.0-553.120.1.rt7.461.el8_102026-04-20redhat
redhatkernel-0:6.12.0-124.49.1.el10_12026-04-06redhat
redhatkernel-0:5.14.0-611.45.1.el9_72026-03-30redhat

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 45× 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 120 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-23191?
CVE-2026-23191 is a high vulnerability published on February 14, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: aloop: Fix racy access at PCM trigger The PCM trigger callback of aloop driver tries to check the PCM state and stop the stream of the tied substream in the corresponding cable. Since both check and stop operations are…
When was CVE-2026-23191 disclosed?
CVE-2026-23191 was first published in the National Vulnerability Database on February 14, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23191 actively exploited?
CVE-2026-23191 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-23191?
CVE-2026-23191 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.0.
How do I remediate CVE-2026-23191?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23191, 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-23191

Explore →

Is Your Infrastructure Affected by CVE-2026-23191?

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

Start Free Scan →Browse All CVEs