CVE-2026-98209
mmc: sdhci-of-aspeed: Remove children before releasing SDC resources
No known exploitation. EPSS puts it in the 12th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c, < 6b22b4d29e4fc1d2de2e4d7174925d68220165fbUpgrade to: 6b22b4d29e4fc1d2de2e4d7174925d68220165fbAffected: ≥ bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c, < 67e8117df8547433989a6ac1545a68848d0a289fUpgrade to: 67e8117df8547433989a6ac1545a68848d0a289fAffected: ≥ bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c, < bc5e79a5a5651588f3a93bef7815e4e86f78962cUpgrade to: bc5e79a5a5651588f3a93bef7815e4e86f78962cAffected: ≥ bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c, < b84d29f2541c8adb768e468388dbaa4bc25ef157Upgrade to: b84d29f2541c8adb768e468388dbaa4bc25ef157 + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-of-aspeed: Remove children before releasing SDC resources Probe failure and removal leave SDHCI child devices registered after the parent clock and managed resources are released. Unregister the OF children in reverse order before disabling the parent clock on both paths. Use of_platform_device_destroy() because manual child creation does not set the flag required by of_platform_depopulate(). This issue was identified during our ongoing static-analysis research while reviewing kernel code.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 12th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/15b5ffd8af2dd46856da57467eb6e0f90d8ada51
- git.kernel.org/stable/c/356b4b3b28a8ecd2a6c66d3b9666686315337df1
- git.kernel.org/stable/c/4396d70bb7fec531bcf934fed016b2f3300c670b
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI