Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98213mmc: core: Cancel SDIO IRQ work before freeing host

Description

In the Linux kernel, the following vulnerability has been resolved: mmc: core: Cancel SDIO IRQ work before freeing host A host controller that uses sdio_signal_irq() schedules host->sdio_irq_work from its interrupt handler. That work is only cancelled on the suspend path (mmc_sdio_suspend()), not on the remove/free path, so a worker armed just before the controller freed its IRQ can run after mmc_host_classdev_release() has freed the host and dereference it through container_of(). Cancel host->sdio_irq_work in mmc_free_host(), like the existing host->detect drain added by commit 1036f69e2513 ("mmc: core: Cancel delayed work before releasing host"). This issue was found by an in-house static analysis tool.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 682696605c7093d2800c498c04166831e5aedf87 – < bae1cf4f9902b2065bd78b759c7fe6312855f05e
    • affected 682696605c7093d2800c498c04166831e5aedf87 – < 0bf3d168a2cc20b120d6b50f0a8ac5b40ff4d589
    • affected 682696605c7093d2800c498c04166831e5aedf87 – < 1d6e7315ee1c992b4ca42c9b11c5ed0e925a00e0
    • affected 682696605c7093d2800c498c04166831e5aedf87 – < 4553b5004eca9c9eae29a421f1a9c4d5db2c9114
    • affected 682696605c7093d2800c498c04166831e5aedf87 – < 2a863458828ade0671c2bc2e469bbd7f2340eb03
    • affected 682696605c7093d2800c498c04166831e5aedf87 – < 6feadbecdae60a6324c967f3b1493741083793a3
  • Linux · Linux

    • affected 4.13
    • unaffected < 4.13
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98213 badge
[![CVE-2026-98213](https://cveledger.app/badge/CVE-2026-98213.svg)](https://cveledger.app/cve/CVE-2026-98213)

Record last updated .