CVE-2026-72486mailbox: mtk-adsp: fix UAF during device teardown
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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().
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 before b6337a08a63eef8efcffe3c01d479badda6bbbdb; from af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 before e519c1d8c5efb5cd8d4c5bb3fe39b1bbb812bdb9; from af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 before fc6c3deb1d4c0adebf7dee0b8af4082af3f17690; from af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 before 7d881615fb6373f71fc628b3f00186aeca87a3d5; from af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 before 25d6ea6c76e1b1b7c57337b2f8f1b6fc8d5c52bc; from af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 before b57d1a40bc43258372fa1f4d39305e093947a262 | CNA record |
References
- https://git.kernel.org/stable/c/b6337a08a63eef8efcffe3c01d479badda6bbbdb
- https://git.kernel.org/stable/c/e519c1d8c5efb5cd8d4c5bb3fe39b1bbb812bdb9
- https://git.kernel.org/stable/c/fc6c3deb1d4c0adebf7dee0b8af4082af3f17690
- https://git.kernel.org/stable/c/7d881615fb6373f71fc628b3f00186aeca87a3d5
- https://git.kernel.org/stable/c/25d6ea6c76e1b1b7c57337b2f8f1b6fc8d5c52bc
- https://git.kernel.org/stable/c/b57d1a40bc43258372fa1f4d39305e093947a262
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.