CVE-2026-72486
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().
How to fix
- Linux Linuxb6337a08a63eef8efcffe3c01d479badda6bbbdb, e519c1d8c5efb5cd8d4c5bb3fe39b1bbb812bdb9, fc6c3deb1d4c0adebf7dee0b8af4082af3f17690, 7d881615fb6373f71fc628b3f00186aeca87a3d5, 25d6ea6c76e1b1b7c57337b2f8f1b6fc8d5c52bc, b57d1a40bc43258372fa1f4d39305e093947a262 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| Linux Linux | af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 ≤ v < b6337a08a63eef8efcffe3c01d479badda6bbbdb, af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 ≤ v < e519c1d8c5efb5cd8d4c5bb3fe39b1bbb812bdb9, af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 ≤ v < fc6c3deb1d4c0adebf7dee0b8af4082af3f17690, af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 ≤ v < 7d881615fb6373f71fc628b3f00186aeca87a3d5, af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 ≤ v < 25d6ea6c76e1b1b7c57337b2f8f1b6fc8d5c52bc, af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 ≤ v < b57d1a40bc43258372fa1f4d39305e093947a262, 5.18 | b6337a08a63eef8efcffe3c01d479badda6bbbdb, e519c1d8c5efb5cd8d4c5bb3fe39b1bbb812bdb9, fc6c3deb1d4c0adebf7dee0b8af4082af3f17690, 7d881615fb6373f71fc628b3f00186aeca87a3d5, 25d6ea6c76e1b1b7c57337b2f8f1b6fc8d5c52bc, b57d1a40bc43258372fa1f4d39305e093947a262 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.