CVE-2026-74640

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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: FCP: fix OOB write in fcp_meter_ctl_get()

fcp_ioctl_set_meter_map() bounds the user-supplied Level Meter map size by the driver's own limit of 255

if (map.map_size < 1 || map.map_size > 255 || map.meter_slots < 1 || map.meter_slots > 255) return -EINVAL;

and passes it to fcp_add_new_ctl() as the control's channel count, where it is stored as elem->channels.

Every control read writes into struct snd_ctl_elem_value, whose integer array is declared long value[128], so the limit is 128, not 255. fcp_meter_ctl_get() stores one 64-bit word per channel into that array with no bound of its own:

for (i = 0; i < elem->channels; i++) { int idx = private->meter_level_map[i]; int value = idx < 0 ? 0 : le32_to_cpu(resp[idx]);

ucontrol->value.integer.value[i] = value; }

snd_ctl_elem_read_user() serves that object from memdup_user(_control, sizeof(*control)), 1224 bytes on LP64 out of kmalloc-2048. offsetof(struct snd_ctl_elem_value, value) is 72, so element i is written at byte 72 + 8 * i and element 144 already lands past the allocation. At map_size 255 the last store ends at byte 2112, 888 bytes past the object and 64 bytes into the adjacent slab object. The stored words come from the device and meter_level_map[] selects which word lands in which slot, so extent and contents are both controlled.

The core does not catch this. snd_ctl_check_elem_info() is reached only from __snd_ctl_elem_info(), which snd_ctl_elem_read() calls under CONFIG_SND_CTL_DEBUG; without that option snd_ctl_skip_validation() is a compile-time true. __snd_ctl_add_replace() validates kcontrol->count and never inspects elem->channels.

Installing an oversized map needs CAP_SYS_RAWIO, but the control outlives the hwdep descriptor that created it, so the out-of-bounds stores are issued by any process able to read controls on /dev/snd/controlC0.

KASAN on 7.2.0-rc5 (arm64), triggered by an unprivileged control read:

BUG: KASAN: slab-out-of-bounds in fcp_meter_ctl_get Write of size 8 at addr ffff000017af04c8 by task fcp_trigger/185 __asan_store8 fcp_meter_ctl_get snd_ctl_elem_read snd_ctl_ioctl Allocated by task 185: memdup_user snd_ctl_ioctl The buggy address is located 0 bytes to the right of allocated 1224-byte region [ffff000017af0000, ffff000017af04c8)

Bound the map size by the ABI limit rather than by 255, and bound the store loop at the sink so it cannot run past the value array whatever elem->channels holds.

Discovered by XBOW, triaged by Baul Lee

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
3%
KEV
Not listed

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (3)

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

ALSA: FCP: fix OOB write in fcp_meter_ctl_get() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/620f1e52a46f604635efd0fb78138afd6a513b5d
generic

ALSA: FCP: fix OOB write in fcp_meter_ctl_get() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: FCP: fix OOB write in fcp_meter_ctl_get() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bb30e35c36ed00f24fa39aded811f64230a913b0

Vendor Advisories for CVE-2026-74640(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 26× in last 7d / 29× 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-30 05:08 UTCEG score recompute
  2. 2026-08-30 05:08 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 17:36 UTCGHSA enrichment
  5. 2026-08-29 05:12 UTCEG score recompute
  6. 2026-08-29 05:11 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 17:34 UTCGHSA enrichment
  9. 2026-08-28 05:49 UTCGHSA enrichment
  10. 2026-08-27 18:16 UTCEG score recompute
  11. 2026-08-27 18:16 UTCGHSA enrichment
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-27 05:26 UTCGHSA enrichment
  14. 2026-08-26 17:51 UTCEG score recompute
  15. 2026-08-26 17:51 UTCGHSA enrichment
  16. 2026-08-26 14:47 UTCEPSS rescore
  17. 2026-08-26 05:35 UTCGHSA enrichment
  18. 2026-08-25 18:02 UTCEG score recompute
  19. 2026-08-25 18:01 UTCGHSA enrichment
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 06:29 UTCEG score recompute
  22. 2026-08-25 06:29 UTCGHSA enrichment
  23. 2026-08-25 05:56 UTCEG score recompute 7.80
  24. 2026-08-25 05:56 UTCGHSA enrichment
  25. 2026-08-25 05:55 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
Show 4 more
  1. 2026-08-24 14:18 UTCEPSS rescore
  2. 2026-08-22 16:24 UTCNVD update
  3. 2026-08-22 15:41 UTCEG score recompute
  4. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74640?
CVE-2026-74640 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: FCP: fix OOB write in fcpmeterctl_get() fcpioctlsetmetermap() bounds the user-supplied Level Meter map size by the driver's own limit of 255 if (map.mapsize < 1 || map.mapsize > 255 || map.meterslots < 1 || map.meterslots >…
When was CVE-2026-74640 disclosed?
CVE-2026-74640 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74640 actively exploited?
CVE-2026-74640 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 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-74640?
CVE-2026-74640 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74640?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74640, 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-74640

Explore →

Is Your Infrastructure Affected by CVE-2026-74640?

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