CVE-2026-23191

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.0EG
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.0Exploit: None knownExposed: 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.0
EG Score
7.0(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

February 14, 2026

Last Modified

September 14, 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(16)

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

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-09-14ubuntu
redhatkernel-0:5.14.0-570.125.1.el9_62026-07-01redhat
redhatkernel-0:4.18.0-305.194.1.el8_42026-06-17redhat
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-0:5.14.0-427.124.1.el9_42026-05-06redhat
redhatkernel-0:4.18.0-372.191.1.el8_62026-05-06redhat
redhatkernel-rt-0:5.14.0-284.169.1.rt14.454.el9_22026-05-06redhat
redhatkernel-0:5.14.0-70.178.1.el9_02026-05-06redhat
redhatkernel-rt-0:5.14.0-70.178.1.rt21.250.el9_02026-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
linuxKernel @ 6.12.70—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.73-1~bpo12+1 (12 versions)6.12.73-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (99 versions)6.18.10-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(10)

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 / 27× 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 207 total refreshes for this CVE.

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

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 September 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-23191 actively exploited?
CVE-2026-23191 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 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-23191?
CVE-2026-23191 has a CVSS v3 base score of 7.0 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by 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