In the Linux kernel, the following vulnerability has been resolved: mmc: hsq: Fix use-after-free in retry work mmc_hsq_pump_requests() queues retry_work when request_atomic() returns -EBUSY; today sdhci-sprd is the only consumer that implements request_atomic(). The work is embedded in a devm-allocated mmc_hsq, but is never cancelled during driver removal. Work still pending at unbind can therefore run after the devm allocation has been released and dereference hsq->mmc and hsq->mrq. Use devm_work_autocancel() to cancel and drain retry_work before the devm allocation is released. By the time devres cleanup begins, mmc_remove_host() has already stopped the host, so no new requests can arm the work. This issue was found by an in-house static analysis tool.
Fix
Microsoft's update · Critical
- Release Notes — azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 · build 6.6.158.1-1
From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-28.
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 2
- StatusReceived → PublishedNVD modified 2026-10-19 09:15
- First seenunscoredNVD modified 2026-10-19 10:18
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://git.kernel.org/stable/c/45341b341642c377192c95e4d48e0a859cf85f42
- https://git.kernel.org/stable/c/5d132990475f02cfa1debe03d50b479432864ebd
- https://git.kernel.org/stable/c/8439bf262ce3267bcfee29d3c61605f1731a2271
- https://git.kernel.org/stable/c/c50d6515bffb148c2c12be6d587ec201dfab4c34
- https://git.kernel.org/stable/c/df2eb59fd9eb33663dc1053f5a4ed851e0aa1f67