CVE-2026-72446

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 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

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: usb-audio: qcom: reject stream disable with no active interface

handle_uaudio_stream_req() resolves an interface index with info_idx_from_ifnum(), which returns -EINVAL when no interface matches. The enable branch and the response: cleanup label both guard against a negative index, but the disable branch does not: it forms info = &uadev[pcm_card_num].info[info_idx] and dereferences it.

uadev[].info is a pointer allocated only when a stream is first enabled, so a negative info_idx on the disable path is unsafe in two ways:

  • If the card was never enabled, .info is NULL and &info[-EINVAL] is a
wild pointer; reading info->data_ep_pipe faults (kernel oops).
  • If the card was enabled at least once (.info allocated) and the
disable names an interface that does not match, &info[-EINVAL] points before the allocation; info->data_ep_pipe / info->sync_ep_pipe are an out-of-bounds slab read and, when non-zero, an out-of-bounds 4-byte write (both pipe fields are cleared to 0). That is memory corruption, not just a NULL dereference.

The request is reachable from unprivileged local userspace over AF_QIPCRTR. Reject a disable request with no resolved interface, matching the guard the enable path already has.

CVSS v3
7.8
EG Score
7.8(high)
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
5%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

ALSA: usb-audio: qcom: reject stream disable with no active interface - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: usb-audio: qcom: reject stream disable with no active interface - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: usb-audio: qcom: reject stream disable with no active interface - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25a867aa5e67a84333fa6e5c21292c5bcff86b90

Vendor Advisories for CVE-2026-72446(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 28× 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.

  1. 2026-08-20 13:05 UTCGHSA enrichment
  2. 2026-08-19 23:52 UTCEG score recompute
  3. 2026-08-19 23:52 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 10:47 UTCGHSA enrichment
  6. 2026-08-18 21:42 UTCEG score recompute
  7. 2026-08-18 21:42 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 08:37 UTCGHSA enrichment
  11. 2026-08-17 19:32 UTCEG score recompute
  12. 2026-08-17 19:32 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 06:28 UTCEG score recompute
  15. 2026-08-17 06:28 UTCGHSA enrichment
  16. 2026-08-17 05:57 UTCEG score recompute 7.80
  17. 2026-08-17 05:57 UTCGHSA enrichment
  18. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  19. 2026-08-17 05:28 UTCEG score recompute
  20. 2026-08-17 05:28 UTCGHSA enrichment
  21. 2026-08-17 05:24 UTCMITRE cvelistV5
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:15 UTCEPSS rescore
  25. 2026-08-15 06:33 UTCGHSA enrichment
Show 3 more
  1. 2026-08-15 06:23 UTCNVD update
  2. 2026-08-15 06:04 UTCEG score recompute
  3. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72446?
CVE-2026-72446 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: qcom: reject stream disable with no active interface handleuaudiostream_req() resolves an interface index with infoidxfrom_ifnum(), which returns -EINVAL when no interface matches. The enable branch and the…
When was CVE-2026-72446 disclosed?
CVE-2026-72446 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72446 actively exploited?
CVE-2026-72446 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 95.0% of all scored CVEs.
What is the CVSS score of CVE-2026-72446?
CVE-2026-72446 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72446?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72446, 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-72446

Explore →

Is Your Infrastructure Affected by CVE-2026-72446?

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