CVE-2026-98212

Unknown

Last modified

CVE-2026-98212 is a vulnerability of currently unknown severity. 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.

Description

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 6db96e5810e0a6a345b7d78549de7676ae5b2662, < c50d6515bffb148c2c12be6d587ec201dfab4c34; >= 6db96e5810e0a6a345b7d78549de7676ae5b2662, < df2eb59fd9eb33663dc1053f5a4ed851e0aa1f67; >= 6db96e5810e0a6a345b7d78549de7676ae5b2662, < 8439bf262ce3267bcfee29d3c61605f1731a2271; >= 6db96e5810e0a6a345b7d78549de7676ae5b2662, < 45341b341642c377192c95e4d48e0a859cf85f42; >= 6db96e5810e0a6a345b7d78549de7676ae5b2662, < 5d132990475f02cfa1debe03d50b479432864ebd
LinuxLinux5.8

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98212?
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.
How severe is CVE-2026-98212?
Severity scoring for CVE-2026-98212 is pending analysis.
How do I fix CVE-2026-98212?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98212?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST