CVE-2026-12232 Out-of-bounds read via unvalidated stream_id in Intel ALH DAI get_properties
A local attacker with device access can leak kernel memory or cause a crash via an out-of-bounds read in the Intel ALH DAI driver.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-12232?
CVE-2026-12232 is a medium-severity vulnerability in zephyrproject zephyr, published on 12 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
The Intel ALH digital-audio-interface driver function dai_alh_get_properties() in drivers/dai/intel/alh/alh.c used a caller-supplied int stream_id with no range validation. The value indexes the fixed-size static const uint8_t alh_handshake_map[64] array and scales a FIFO register address, so an out-of-range stream_id produces an out-of-bounds read of one byte at an attacker-chosen signed offset from the array. That byte is written into prop->dma_hs_id and the resulting struct dai_properties is copied back to the caller, leaking it.
dai_get_properties_copy() is a Zephyr __syscall, and its verifier z_vrfy_dai_get_properties_copy() (drivers/dai/dai_handlers.c) validates only the device-object permission and the destination buffer, not stream_id. A user-mode thread that has been granted access to the ALH DAI device object can therefore call the syscall with an arbitrary stream_id, crossing the userspace/kernel sandbox boundary.
The impact is a one-byte-per-call arbitrary-offset kernel information disclosure (and leakage of a computed kernel address via fifo_address); a stream_id that resolves to an unmapped page faults in kernel context, giving a local denial of service. Exploitation requires CONFIG_USERSPACE and device access, making this a local, moderate-severity issue. The fix rejects negative and too-large stream_id values up front and returns NULL, which the copy wrapper maps to -ENOENT.
Weakness: CWE-125
Which versions are affected by CVE-2026-12232?
How do I fix CVE-2026-12232?
No fix has been published for CVE-2026-12232 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-12232 being exploited?
There is no known exploitation of CVE-2026-12232 in the wild and no public exploit code.
Sources
Also known as GHSA-3557-j848-pv24.