CVE-2026-72486

mailbox: mtk-adsp: fix UAF during device teardown

N/A
Published: August 15, 2026 at 05:57 AM UTC
Updated: August 17, 2026 at 06:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: mailbox: mtk-adsp: fix UAF during device teardown When the SOF audio driver fails to initialize (e.g. firmware boot timeout), its devres unwind frees the snd_sof_dev object that the mailbox client (mtk-adsp-ipc) reaches via chan->cl->rx_callback. The mtk-adsp-mailbox shutdown clears the mailbox command registers but leaves the IRQ line unmasked, so a late interrupt can still queue a threaded handler after mbox_free_channel() had cleared chan->cl, and mbox_chan_received_data() would then trigger UAF: BUG: KASAN: slab-use-after-free in sof_ipc3_validate_fw_version sof_ipc3_validate_fw_version sof_ipc3_do_rx_work sof_ipc3_rx_msg mt8196_dsp_handle_request mtk_adsp_ipc_recv mbox_chan_received_data mtk_adsp_mbox_isr irq_thread_fn Freed by task ...: kfree devres_release_all really_probe ... (sof-audio-of-mt8196 probe failure) The crash was observed roughly three seconds after the failed probe. disable_irq() in shutdown and enable_irq() in startup. disable_irq() also waits for any in-flight interrupts, so by the time mbox_free_channel() proceeds to clear chan->cl no rx_callback can run. In addition, request the IRQ with IRQF_NO_AUTOEN so it stays masked between probe and the first client bind — otherwise an early interrupt can crash on chan->cl == NULL in mbox_chan_received_data().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.18 ≤ v < 6.1.1785.18 ≤ v < 6.12.975.18 ≤ v < 6.18.405.18 ≤ v < 6.6.1455.18 ≤ v < 7.1.55.18 ≤ v < 7.25.18af2dfa96c52d042df5deb29fb6e32d3ff4d76a61
Vendor states this is fixed in 25d6ea6c76e1b1b7c57337b2f8f1b6fc8d5c52bc (fixed)
Vendor states this is fixed in 7d881615fb6373f71fc628b3f00186aeca87a3d5 (fixed)
Vendor states this is fixed in b57d1a40bc43258372fa1f4d39305e093947a262 (fixed)
Vendor states this is fixed in b6337a08a63eef8efcffe3c01d479badda6bbbdb (fixed)
Vendor states this is fixed in e519c1d8c5efb5cd8d4c5bb3fe39b1bbb812bdb9 (fixed)
Vendor states this is fixed in fc6c3deb1d4c0adebf7dee0b8af4082af3f17690 (fixed)
Vendor states this is fixed in 5.18 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card