CVE-2026-99035 — mmc: mtk-sd: Cancel request timeout work on remove
In the Linux kernel, the following vulnerability has been resolved: mmc: mtk-sd: Cancel request timeout work on remove The driver queues req_timeout while a request is active. msdc_request_done() uses cancel_delayed_work(), which does not wait for a timeout callback that has already started. The timeout callback calls mmc_request_done(), which wakes the request waiter, and then continues to use host->dev_comp and check the SDIO IRQ. During unbind, msdc_drv_remove() can return and the managed mmc_host can be freed before the callback finishes. KASAN reported use-after-free accesses in msdc_request_done() and msdc_recheck_sdio_irq() in each of three unbind tests. The same tests completed without a kernel diagnostic after this change. Call cancel_delayed_work_sync() after mmc_remove_host() has stopped new requests and before the driver releases the host resources.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 208489032bdd8d4a7de50f3057c175058f271956 and < 9e799f25c420e759641eb25102967ea091fc758f≥ 208489032bdd8d4a7de50f3057c175058f271956 and < f37e0367ad6f2147a0b37564b442b7a25bec0d23≥ 208489032bdd8d4a7de50f3057c175058f271956 and < 46e75703ca3f00fb8c935b3ce35b90836e34e8af≥ 208489032bdd8d4a7de50f3057c175058f271956 and < edef1355224c0799a502a46b71d3649fa0dd218e≥ 208489032bdd8d4a7de50f3057c175058f271956 and < b38af5386a74416e898955443f2e26547b358cb2version 4.2≥ 208489032bdd8d4a7de50f3057c175058f271956 and < d8ce81006ee4e42ce2d0bd3a2ab87adc1e24ef11≥ 208489032bdd8d4a7de50f3057c175058f271956 and < 2cff6a2a912a3464ae1fefb7e0a82393682ccea6 and 1 more≥ 208489032bdd8d4a7de50f3057c175058f271956 and < e5d82695f2cabca3222b8f6a89ea0e18bafc4c0a |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 23, 2026 – Oct 30, 2026
- 1× Official description updated · Oct 23, 2026 – Oct 23, 2026
References
10 on the record
- github.com/advisories/GHSA-pwxj-3q2q-r972
- git.kernel.org/stable/c/f37e0367ad6f2147a0b37564b442b7a25bec0d23
- git.kernel.org/stable/c/9e799f25c420e759641eb25102967ea091fc758f
- git.kernel.org/stable/c/2cff6a2a912a3464ae1fefb7e0a82393682ccea6
- git.kernel.org/stable/c/d8ce81006ee4e42ce2d0bd3a2ab87adc1e24ef11
- git.kernel.org/stable/c/edef1355224c0799a502a46b71d3649fa0dd218e
- nvd.nist.gov/vuln/detail/CVE-2026-99035
- git.kernel.org/stable/c/b38af5386a74416e898955443f2e26547b358cb2
- git.kernel.org/stable/c/e5d82695f2cabca3222b8f6a89ea0e18bafc4c0a
- git.kernel.org/stable/c/46e75703ca3f00fb8c935b3ce35b90836e34e8af
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-99035 is "mmc: mtk-sd: Cancel request timeout work on remove", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.