CVE-2026-98212: Linux kernel · mmc: hsq: Fix use-after-free in retry work
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in df2eb59fd9eb33663dc1053f5a4ed851e0aa1f67 : patch Linux kernel soon.
Data as of 26 Oct 2026, 13:47 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in df2eb59fd9eb33663dc1053f5a4ed851e0aa1f67, c50d6515bffb148c2c12be6d587ec201dfab4c34, 45341b341642c377192c95e4d48e0a859cf85f42 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in specific commits and versions of the Linux kernel. Users should update to a fixed kernel version that includes the patch. No additional mitigation is required once the system is updated, as the patch cancels and drains the retry work properly during driver removal.
Description
A use-after-free vulnerability was identified and fixed in the Linux kernel's MMC subsystem, specifically in the hsq retry work mechanism. The issue arises because retry work is queued but not cancelled during driver removal, allowing work to run after the associated memory has been freed. This could lead to dereferencing freed memory, causing potential instability or crashes. The fix involves using devm_work_autocancel() to properly cancel and drain the retry work before releasing the memory allocation.
References
- git.kernel.org/stable/c/c50d6515bffb148c2c12be6d587ec201dfab4c34 (opens in a new tab)
- git.kernel.org/stable/c/df2eb59fd9eb33663dc1053f5a4ed851e0aa1f67 (opens in a new tab)
- git.kernel.org/stable/c/8439bf262ce3267bcfee29d3c61605f1731a2271 (opens in a new tab)
- git.kernel.org/stable/c/45341b341642c377192c95e4d48e0a859cf85f42 (opens in a new tab)
- git.kernel.org/stable/c/5d132990475f02cfa1debe03d50b479432864ebd (opens in a new tab)