CVE-2026-89440

mmc: via-sdmmc: stop card-detect handling on probe failure

HIGH
7.8
CVSS Score
Published: September 11, 2026 at 07:43 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: mmc: via-sdmmc: stop card-detect handling on probe failure request_irq() registers the SD card-detect interrupt and the probe enables it before mmc_add_host() runs. If mmc_add_host() fails, the error path only unmaps the registers and returns: the interrupt stays registered, so the handler keeps running against the host once it is freed. via_sdc_isr() dereferences sdhost and its MMIO base and schedules carddet_work, which via_sdc_card_detect() also runs against freed memory through its container_of() dereference. Add a probe-error path that disables and frees the interrupt and cancels carddet_work before unmapping. carddet_work can re-enable the device interrupt via via_reset_pcictrl(), which restores PCIINTCTRL, so mask it again after cancelling the work. This issue was found by an in-house static analysis tool and confirmed by manual code review.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

076bcd2c93e16b05c10564e299d6e5d26a766d000959cc1685eb19774300d43ef25e318b457b156b0ec94795114edc7e24ec71849dce42bfa61dafa312b8e81b77c05c658efd9cde3585bbd65ae39b594.14.3034.19.2704.9.3375.10.1635.15.865.4.2296.0.166.1.26.263400da6cd37a9793c19bb6aed7131b58b975a0476bcd2c93e16b5c10564e299d6e5d26a766d095025a8dd0ec015872f6c16473fe04d6264e68ca959cc1685eb19774300d43ef25e318b457b156bba91b413983a9235792523c6b9f7ba2586c4d75de4e46fb61e3bb4628170810d3f2b996b709b90d9f59ef2a47a228e51322ad76752a55a8917c56e38
Vendor states this is fixed in 088eaa92fcebaa6b957ccf9635afdf39643a577d (fixed)
Vendor states this is fixed in 2550f89589caad7402d618d7dffc038582c94b6b (fixed)
Vendor states this is fixed in 5bb5327b92aae17e91c7228953c350a6ee3c94e8 (fixed)
Vendor states this is fixed in 806409f12fdb14c9e4c56a64494c9b75f356cd49 (fixed)
Vendor states this is fixed in c2b8a624911999399cc14822fec3e35032b3cee4 (fixed)
Vendor states this is fixed in d045596706d1b25d38af4a79980b017639fea9d1 (fixed)
Vendor states this is fixed in dde5b9c91e9fc64e54a2f186d3ae95868b4dbb02 (fixed)
Vendor states this is fixed in efe7f25dd27e35063477b4b0e7eed3675669fd99 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card