CVE-2026-72486mailbox: mtk-adsp: fix UAF during device teardown
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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().
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 days later
· 2 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 – < b6337a08a63eef8efcffe3c01d479badda6bbbdb
- affected af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 – < e519c1d8c5efb5cd8d4c5bb3fe39b1bbb812bdb9
- affected af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 – < fc6c3deb1d4c0adebf7dee0b8af4082af3f17690
- affected af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 – < 7d881615fb6373f71fc628b3f00186aeca87a3d5
- affected af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 – < 25d6ea6c76e1b1b7c57337b2f8f1b6fc8d5c52bc
- affected af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 – < b57d1a40bc43258372fa1f4d39305e093947a262
- affected 5.18
- unaffected < 5.18
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/b6337a08a63eef8efcffe3c01d479badda6bbbdb (opens in a new tab)
- https://git.kernel.org/stable/c/e519c1d8c5efb5cd8d4c5bb3fe39b1bbb812bdb9 (opens in a new tab)
- https://git.kernel.org/stable/c/fc6c3deb1d4c0adebf7dee0b8af4082af3f17690 (opens in a new tab)
- https://git.kernel.org/stable/c/7d881615fb6373f71fc628b3f00186aeca87a3d5 (opens in a new tab)
- https://git.kernel.org/stable/c/25d6ea6c76e1b1b7c57337b2f8f1b6fc8d5c52bc (opens in a new tab)
- https://git.kernel.org/stable/c/b57d1a40bc43258372fa1f4d39305e093947a262 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59385 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72486)Record last updated .