CVE-2026-64409

CVE CVE-2026-64409EUVD EUVD-2026-48953Published 2026-07-25T08:50:50.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() Every once in a while we see a hung btmtksdio_flush() task: INFO: task kworker/u17:0:189 blocked for more than 122 seconds. __cancel_work_timer+0x3f4/0x460 cancel_work_sync+0x1c/0x2c btmtksdio_flush+0x2c/0x40 hci_dev_open_sync+0x10c4/0x2190 [..] It all boils down to incorrect time_is_before_jiffies() usage in btmtksdio_txrx_work(). The btmtksdio_txrx_work() loop is expected to be terminated if running for longer than 5*HZ. However the timeout check is twisted: time_is_before_jiffies(old_jiffies + 5*HZ) evaluates to true when old_jiffies + 5*HZ is in the past i.e. when a timeout has occurred. Using OR with time_is_before_jiffies(txrx_timeout) means that: - before the 5-second timeout: the condition is `int_status || false`, so it loops as long as there are pending interrupts. - after the 5-second timeout: the condition becomes `int_status || true`, which is always true. When the loop becomes infinite btmtksdio_txrx_work() loop never terminates and never releases the SDIO host. Fix loop termination condition to actually enforce a 5*HZ timeout.

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 patch: 7.2-rc1; patch: 6.12.96; 5.17; 26270bc189ea4b5a8356ec99561357fc87f00b32 <a257407e2bbbb099ed427719a50563f67fa366d8; patch: 6.18.39; 26270bc189ea4b5a8356ec99561357fc87f00b32 <7b429d611060e87752e848851815537963726493; 26270bc189ea4b5a8356ec99561357fc87f00b32 <466540e045d01fcacf383a5beb8a2dad2fc53a26; patch: 0; 26270bc189ea4b5a8356ec99561357fc87f00b32 <0f0a83e26a9c7fd4b243c315ce07161d2496d83d; patch: 6.6.145; 26270bc189ea4b5a8356ec99561357fc87f00b32 <f6682c23b6fac4780d297ae4662053d17e58fd52; patch: 6.1.178; patch: 7.1.4; 26270bc189ea4b5a8356ec99561357fc87f00b32 <0039bdde36b23ccf1196635f1d52c5490481544d

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.