CVE-2026-64409

published 25 Jul 2026 · updated 14 Nov 2026

Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work()

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f6682c23b6fac4780d297ae4662053d17e58fd52, Kernel 0039bdde36b23ccf1196635f1d52c5490481544d, Kernel 0f0a83e26a9c7fd4b243c315ce07161d2496d83d and 8 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=26270bc189ea4b5a8356ec99561357fc87f00b32 <f6682c23b6fac4780d297ae4662053d17e58fd52, >=26270bc189ea4b5a8356ec99561357fc87f00b32 <0039bdde36b23ccf1196635f1d52c5490481544d, >=26270bc189ea4b5a8356ec99561357fc87f00b32 <0f0a83e26a9c7fd4b243c315ce07161d2496d83d, >=26270bc189ea4b5a8356ec99561357fc87f00b32 <466540e045d01fcacf383a5beb8a2dad2fc53a26, >=26270bc189ea4b5a8356ec99561357fc87f00b32 <7b429d611060e87752e848851815537963726493, >=26270bc189ea4b5a8356ec99561357fc87f00b32 <a257407e2bbbb099ed427719a50563f67fa366d8, =5.17f6682c23b6fac4780d297ae4662053d17e58fd52, 0039bdde36b23ccf1196635f1d52c5490481544d, 0f0a83e26a9c7fd4b243c315ce07161d2496d83d, 466540e045d01fcacf383a5beb8a2dad2fc53a26, 7b429d611060e87752e848851815537963726493, a257407e2bbbb099ed427719a50563f67fa366d8
linux-kernel: Kernel>=6.13.0 <6.18.39, >=6.19.0 <7.1.4, >=6.2.0 <6.6.145, >=6.7.0 <6.12.96, >=5.17.0 <6.1.1786.18.39, 7.1.4, 6.6.145, 6.12.96, 6.1.178

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64409 severity on Zeptric[![CVE-2026-64409](https://zeptric.io/badge/cve/CVE-2026-64409.svg)](https://zeptric.io/cve/CVE-2026-64409)