CVE-2026-98210: mmc: mxcmmc: cancel data work and watchdog on remove
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 23383e0578b58ba2dc0730cf9f7806bd66bf859a, 314966b490323bdcfd3162a1398b00e587e0ced4, 740f595f8ad678cb4d79f13edd12851df2492bdd; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 23383e0578b58ba2dc0730cf9f7806bd66bf859a, 314966b490323bdcfd3162a1398b00e587e0ced4, 740f595f8ad678cb4d79f13edd12851df2492bdd; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: mmc: mxcmmc: cancel data work and watchdog on remove mxcmci_remove() frees the host through the devm tail, but neither it nor mmc_remove_host() drains the driver's own asynchronous state. host->watchdog, a 10 s timer armed on the DMA path in mxcmci_setup_data(), is deleted only by the DMA- and IRQ-complete paths, which the remove path does not explicitly drain; it can therefore fire after the host is freed and dereference it in mxcmci_watchdog(). host->datawork, armed from the IRQ handler on the PIO path, is not cancelled by the remove path either. Free the devm-registered IRQ, then cancel datawork and delete the watchdog in mxcmci_remove(), before dma_release_channel(). Freeing the IRQ first keeps a trailing handler from re-arming datawork between the cancel and the host free. Both callbacks are non-self-rearming. This issue was found by an in-house static analysis tool.
- Published
- Oct 6, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.7affected
- f6ad0a481342223b2e7ae9f55b154e14f1391ada and later · before 740f595f8ad678cb4d79f13edd12851df2492bddaffected · git
- f6ad0a481342223b2e7ae9f55b154e14f1391ada and later · before d3641afe6ee76d852834a34ef0669eefced32752affected · git
- f6ad0a481342223b2e7ae9f55b154e14f1391ada and later · before 314966b490323bdcfd3162a1398b00e587e0ced4affected · git
- f6ad0a481342223b2e7ae9f55b154e14f1391ada and later · before ae10838a7cdf0e54caa9d0a4f488704fd04e7f01affected · git
- f6ad0a481342223b2e7ae9f55b154e14f1391ada and later · before a1ff367e0dc961d73707add508a95df5c3509bd1affected · git
- f6ad0a481342223b2e7ae9f55b154e14f1391ada and later · before 23383e0578b58ba2dc0730cf9f7806bd66bf859aaffected · git
- f6ad0a481342223b2e7ae9f55b154e14f1391ada and later · before e2948c4232209e87c861a680f20f1e3cf8a57fecaffected · git
- f6ad0a481342223b2e7ae9f55b154e14f1391ada and later · before d3a421c82412344022982d5b91ba23194a0a6f29affected · git
- before 3.7not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.8-1 | 7.2.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98208Oct 6, 2026 · mmc: sdio_uart: fix xmit_fifo leak when the port table is full0Monitor
- ← EarlierCVE-2026-98209Oct 6, 2026 · mmc: sdhci-of-aspeed: Remove children before releasing SDC resources0Monitor
- Later →CVE-2026-98211Oct 6, 2026 · mmc: mmci: Fix use-after-free in busy-timeout work0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 23383e0578b58ba2dc0730cf9f7806bd66bf859a | Vendor (CNA) |
| Linux Linux | 314966b490323bdcfd3162a1398b00e587e0ced4 | Vendor (CNA) |
| Linux Linux | 740f595f8ad678cb4d79f13edd12851df2492bdd | Vendor (CNA) |
| Linux Linux | a1ff367e0dc961d73707add508a95df5c3509bd1 | Vendor (CNA) |
| Linux Linux | ae10838a7cdf0e54caa9d0a4f488704fd04e7f01 | Vendor (CNA) |
| Linux Linux | d3641afe6ee76d852834a34ef0669eefced32752 | Vendor (CNA) |
| Linux Linux | d3a421c82412344022982d5b91ba23194a0a6f29 | Vendor (CNA) |
| Linux Linux | e2948c4232209e87c861a680f20f1e3cf8a57fec | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayOct 30, 2026+24 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/314966b490323bdcfd3162a1398b00e587e0ced4
- git.kernel.org/stable/c/740f595f8ad678cb4d79f13edd12851df2492bdd
- git.kernel.org/stable/c/a1ff367e0dc961d73707add508a95df5c3509bd1
- git.kernel.org/stable/c/ae10838a7cdf0e54caa9d0a4f488704fd04e7f01
- git.kernel.org/stable/c/d3641afe6ee76d852834a34ef0669eefced32752
- git.kernel.org/stable/c/d3a421c82412344022982d5b91ba23194a0a6f29
- git.kernel.org/stable/c/e2948c4232209e87c861a680f20f1e3cf8a57fec
Vendor advisories and official records. Exploit/PoC links are deliberately left out.