- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: mmc: via-sdmmc: cancel card-detect work on remove Disabling the device interrupt and freeing the IRQ prevents new card-detect work from being queued, but carddet_work already queued by the handler can still run after via_sd_remove() returns. via_sdc_card_detect() recovers the host through container_of() and dereferences its MMIO base; once remove() returns the host can be freed, so that work would touch freed memory. Cancel carddet_work after freeing the IRQ and before cancelling finish_bh_work, which the card-detect handler can also queue. carddet_work can re-enable the interrupt through via_reset_pcictrl(); mask it again afterwards. This issue was found by an in-house static analysis tool and confirmed by manual code review.
Timeline
ID reserved
By Linux
Published
- 49 days later
· 49 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected f0bf7f61b8405224bc52fc9a3ccd167a68126e00 – < 28e8e9e1f3bdb75b611ea14c39775455528c4012
- affected f0bf7f61b8405224bc52fc9a3ccd167a68126e00 – < a32603f9b4dd0a1c3ea5845eec7c95f5f8741b3d
- affected f0bf7f61b8405224bc52fc9a3ccd167a68126e00 – < 3ee1b5c8618a26811840bf9f45cb3120dac1e273
- affected f0bf7f61b8405224bc52fc9a3ccd167a68126e00 – < 55d71c70f11d9f92c7d2653774001e98cb509deb
- affected f0bf7f61b8405224bc52fc9a3ccd167a68126e00 – < 0a3c70191868fb007c03ff79693ad4e4b3fdcbb8
- affected f0bf7f61b8405224bc52fc9a3ccd167a68126e00 – < f7ff3027ef004a331ef911a4886f12bc2e996037
- affected f0bf7f61b8405224bc52fc9a3ccd167a68126e00 – < eaca730c6f5e3609df62a0469fb789235a93d276
- affected f0bf7f61b8405224bc52fc9a3ccd167a68126e00 – < 57e5d877f898d5e5c9d672a77bb6bdd24f0d9bf5
- affected 2.6.31
- unaffected < 2.6.31
- unaffected 5.10.273 – ≤ 5.10.*
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.50 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/28e8e9e1f3bdb75b611ea14c39775455528c4012 (opens in a new tab)
- https://git.kernel.org/stable/c/a32603f9b4dd0a1c3ea5845eec7c95f5f8741b3d (opens in a new tab)
- https://git.kernel.org/stable/c/3ee1b5c8618a26811840bf9f45cb3120dac1e273 (opens in a new tab)
- https://git.kernel.org/stable/c/55d71c70f11d9f92c7d2653774001e98cb509deb (opens in a new tab)
- https://git.kernel.org/stable/c/0a3c70191868fb007c03ff79693ad4e4b3fdcbb8 (opens in a new tab)
- https://git.kernel.org/stable/c/f7ff3027ef004a331ef911a4886f12bc2e996037 (opens in a new tab)
- https://git.kernel.org/stable/c/eaca730c6f5e3609df62a0469fb789235a93d276 (opens in a new tab)
- https://git.kernel.org/stable/c/57e5d877f898d5e5c9d672a77bb6bdd24f0d9bf5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-76347 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89441)Record last updated .