Stale SDHCI children via incomplete controller teardown
Published Oct 6, 2026 · Updated Oct 6, 2026
Improper teardown in Linux's ASPEED SD controller driver leaves SDHCI child devices registered after parent resources are released. The probe-failure and removal paths disable the parent clock without destroying manually created children, which remain bound to released resources. Exposure requires an ASPEED SD controller and a probe failure or driver removal; the upstream patch reports no runtime reproduction or demonstrated attacker-controlled trigger.
Summary
What happened
Improper teardown in Linux's ASPEED SD controller driver leaves SDHCI child devices registered after parent resources are released. The probe-failure and removal paths disable the parent clock without destroying manually created children, which remain bound to released resources. Exposure requires an ASPEED SD controller and a probe failure or driver removal; the upstream patch reports no runtime reproduction or demonstrated attacker-controlled trigger.
The record
- CVE
- CVE-2026-98209
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.4
- Affected versionversion=bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c <15b5ffd8af2dd46856da57467eb6e0f90d8ada51
- Affected versionversion=bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c <356b4b3b28a8ecd2a6c66d3b9666686315337df1
- Affected versionversion=bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c <4396d70bb7fec531bcf934fed016b2f3300c670b
- Affected versionversion=bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c <67e8117df8547433989a6ac1545a68848d0a289f
- Affected versionversion=bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c <6b22b4d29e4fc1d2de2e4d7174925d68220165fb
- Affected versionversion=bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c <7eb896617a6db846b18596c10ca9f8900a73013e
- Affected versionversion=bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c <b84d29f2541c8adb768e468388dbaa4bc25ef157
- Affected versionversion=bb7b8ec62dfb9b255027c3a54d01f12fc3bd1d2c <bc5e79a5a5651588f3a93bef7815e4e86f78962c
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started