CVE-2026-89440

CVE CVE-2026-89440EUVD EUVD-2026-76346Published 2026-09-11T19:43:09.000ZLast changed 2026-09-14T11:59:51.000ZCVSS 7.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 5.15.86 <5.15.221; 5.4.229 <5.5; 0ec94795114edc7e24ec71849dce42bfa61dafa3; 63400da6cd37a9793c19bb6aed7131b58b975a04 <5bb5327b92aae17e91c7228953c350a6ee3c94e8; patch: 6.1.188; 4.19.270 <4.20; 5.10.163 <5.10.270; e4e46fb61e3bb4628170810d3f2b996b709b90d9 <2550f89589caad7402d618d7dffc038582c94b6b; patch: 0; patch: 5.10.270; 076bcd2c93e16b05c10564e299d6e5d26a766d00; 6.1.2 <6.1.188; e4e46fb61e3bb4628170810d3f2b996b709b90d9 <efe7f25dd27e35063477b4b0e7eed3675669fd99; 6.2; patch: 6.6.157; 0959cc1685eb19774300d43ef25e318b457b156b <d045596706d1b25d38af4a79980b017639fea9d1; ba91b413983a9235792523c6b9f7ba2586c4d75d <806409f12fdb14c9e4c56a64494c9b75f356cd49; 95025a8dd0ec015872f6c16473fe04d6264e68ca; patch: 6.18.50; e4e46fb61e3bb4628170810d3f2b996b709b90d9 <088eaa92fcebaa6b957ccf9635afdf39643a577d; patch: 7.2.4; 6.0.16 <6.1; 12b8e81b77c05c658efd9cde3585bbd65ae39b59; f59ef2a47a228e51322ad76752a55a8917c56e38; e4e46fb61e3bb4628170810d3f2b996b709b90d9 <dde5b9c91e9fc64e54a2f186d3ae95868b4dbb02; patch: 5.15.221; e4e46fb61e3bb4628170810d3f2b996b709b90d9 <c2b8a624911999399cc14822fec3e35032b3cee4; patch: 7.3-rc1; 4.9.337 <4.10; patch: 6.12.109; 4.14.303 <4.15

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.