CVE-2026-99482
ASoC: amd: ps: fix snd_acp63_remove() teardown ordering
What happened?
In the Linux kernel, the following vulnerability has been resolved:
ASoC: amd: ps: fix snd_acp63_remove() teardown ordering
The ACP IRQ handlers dereference the SoundWire, SoundWire DMA, and PDM child platform devices, but snd_acp63_remove() unregisters them while the interrupt is still held by devres, which frees it only after remove returns. An interrupt in this window is a use-after-free.
Mask the ACP interrupt sources and call devm_free_irq() before the first child device is unregistered. The masking goes through the new acp_hw_ops->disable_interrupts callback, keeping the remove path platform-agnostic. The interrupt line is shared, and acp_hw_deinit() clears the sources only after the children are gone, which would leave the line raised with no handler left to ack it. The window predates the tagged refactor, which only reshaped the dereferences.
devm_free_irq() waits for in-flight handlers, but not for work the hardirq has already queued: acp63_irq_handler() schedules amd_sdw_irq_thread on the SoundWire manager. Draining that work in the manager's remove path is a soundwire-side change and follows separately.
This issue was found by an in-house static analysis tool.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: eaf825037d6df89811d43391be920bf6ad731463 to < be66694b2f818d7b14eb5022382b15df837459d8; affected: eaf825037d6df89811d43391be920bf6ad731463 to < 2ff55599528d7712c46956c038665a4d5a5160e5; affected: eaf825037d6df89811d43391be920bf6ad731463 to < 01ab732291bb05cc60952cbb365f4523b747ccfb; affected: eaf825037d6df89811d43391be920bf6ad731463 to < c53791d673ed4da6759d276078627ec4d0c6536b | See vendor advisory |
| LinuxLinux | affected: 6.9; unaffected: 0 to < 6.9; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99482
- https://git.kernel.org/stable/c/be66694b2f818d7b14eb5022382b15df837459d8
- https://git.kernel.org/stable/c/2ff55599528d7712c46956c038665a4d5a5160e5
- https://git.kernel.org/stable/c/01ab732291bb05cc60952cbb365f4523b747ccfb
- https://git.kernel.org/stable/c/c53791d673ed4da6759d276078627ec4d0c6536b