CVE-2026-99347
Severity unknownNo known exploitationFix availableALSA: x86: hdmi: fix chmap array missing terminator entry
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 9% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
In the Linux kernel, the following vulnerability has been resolved: ALSA: x86: hdmi: fix chmap array missing terminator entry had_build_channel_allocation_map() allocates a single struct snd_pcm_chmap_elem via kzalloc() and stores it as intelhaddata->chmap->chmap. struct snd_pcm_chmap.chmap is expected to be a zero-terminated array (see snd_pcm_std_chmaps[]), but had_register_chmap_ctls() never overrides the TLV callback installed by snd_pcm_add_chmap_ctls(), so the generic pcm_chmap_ctl_tlv() from ALSA core is left in place. pcm_chmap_ctl_tlv() is reachable by any local user via SNDRV_CTL_IOCTL_TLV_READ on the "Playback Channel Map" control and walks the array with "for (map = info->chmap; map->channels; map++)". Since the driver's single element is never terminated, this walks past the allocation. The same pointer is also freed on hot-unplug and rebuilt on hot-plug under intelhaddata->mutex, while the TLV callback runs under card->controls_rwsem without that mutex, so the walk can also race a concurrent free of the array. Fix this by allocating a second, zeroed element so the array is properly terminated, and by dropping the inherited TLV callback entirely at registration time, since the driver never implements one of its own.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 5dab11d89777230b3ff38f19ee1b6fbba9688b23 before 29fdc91fb672da4532cc9da6d53aa9b3c396ec63 | 29fdc91fb672da4532cc9da6d53aa9b3c396ec63 | CVE Program |
| Linux | Linux | from 5dab11d89777230b3ff38f19ee1b6fbba9688b23 before 92f77936554b01ed5bff3175e511111b5aa57976 | 92f77936554b01ed5bff3175e511111b5aa57976 | CVE Program |
| Linux | Linux | from 5dab11d89777230b3ff38f19ee1b6fbba9688b23 before f5e1a9a3fddab8421416b68bb132ae9626d07156 | f5e1a9a3fddab8421416b68bb132ae9626d07156 | CVE Program |
| Linux | Linux | from 5dab11d89777230b3ff38f19ee1b6fbba9688b23 before a0b1f32f912faaad0ed3ee98a04367d9a6e3a737 | a0b1f32f912faaad0ed3ee98a04367d9a6e3a737 | CVE Program |
| Linux | Linux | 4.11 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.118 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.64 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 4.11 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/29fdc91fb672da4532cc9da6d53aa9b3c396ec63 (opens in a new tab)
- https://git.kernel.org/stable/c/92f77936554b01ed5bff3175e511111b5aa57976 (opens in a new tab)
- https://git.kernel.org/stable/c/a0b1f32f912faaad0ed3ee98a04367d9a6e3a737 (opens in a new tab)
- https://git.kernel.org/stable/c/f5e1a9a3fddab8421416b68bb132ae9626d07156 (opens in a new tab)