alsa-lib through 1.2.16.1 contains a denial of service vulnerability in the multi PCM plugin that fails to validate sparse binding indices before array access. Attackers can supply a malicious ALSA configuration file with sparse bindings to trigger an out-of-bounds array read and assertion failure, causing the application to abort.
CVE-2026-96675
This low-severity CVE scores 3.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.3
- EG Score
- 3.3(low)
- EG Risk
- 15(Track)EG Risk 15/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 computedSeverity33% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
References (4)
- disclosure@vulncheckhttps://github.com/alsa-project/alsa-lib
- disclosure@vulncheckhttps://github.com/alsa-project/alsa-lib/blob/v1.2.16.1/src/pcm/pcm_multi.c#L1122-L1131
- disclosure@vulncheckhttps://github.com/alsa-project/alsa-lib/pull/527
- disclosure@vulncheckhttps://www.vulncheck.com/advisories/alsa-lib-through-1.2.16.1-denial-of-service-via-pcm-multi
Vendor Advisories for CVE-2026-96675(1)
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 5× in last 7d / 5× 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.
- 2026-09-23 18:18 UTCEG score recompute
- 2026-09-23 17:49 UTCEG score recompute
- 2026-09-23 16:17 UTCEG score recompute
- 2026-09-23 15:44 UTCEG score recompute
- 2026-09-23 15:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-129
Frequently asked(4)
What is CVE-2026-96675?
When was CVE-2026-96675 disclosed?
What is the CVSS score of CVE-2026-96675?
How do I remediate CVE-2026-96675?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-96675
Is Your Infrastructure Affected by CVE-2026-96675?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.