Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work()
Summary
| CVE | CVE-2026-64409 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-25 10:17:24 UTC |
| Updated | 2026-07-25 10:17:24 UTC |
| Description | 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. |
Risk And Classification
EPSS: 0.001730000 probability, percentile 0.069650000 (date 2026-07-28)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 26270bc189ea4b5a8356ec99561357fc87f00b32 f6682c23b6fac4780d297ae4662053d17e58fd52 git | Not specified |
| CNA | Linux | Linux | affected 26270bc189ea4b5a8356ec99561357fc87f00b32 466540e045d01fcacf383a5beb8a2dad2fc53a26 git | Not specified |
| CNA | Linux | Linux | affected 26270bc189ea4b5a8356ec99561357fc87f00b32 7b429d611060e87752e848851815537963726493 git | Not specified |
| CNA | Linux | Linux | affected 26270bc189ea4b5a8356ec99561357fc87f00b32 0039bdde36b23ccf1196635f1d52c5490481544d git | Not specified |
| CNA | Linux | Linux | affected 26270bc189ea4b5a8356ec99561357fc87f00b32 0f0a83e26a9c7fd4b243c315ce07161d2496d83d git | Not specified |
| CNA | Linux | Linux | affected 26270bc189ea4b5a8356ec99561357fc87f00b32 a257407e2bbbb099ed427719a50563f67fa366d8 git | Not specified |
| CNA | Linux | Linux | affected 5.17 | Not specified |
| CNA | Linux | Linux | unaffected 5.17 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.178 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.145 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.96 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.39 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.4 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/7b429d611060e87752e848851815537963726493 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/0039bdde36b23ccf1196635f1d52c5490481544d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/466540e045d01fcacf383a5beb8a2dad2fc53a26 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a257407e2bbbb099ed427719a50563f67fa366d8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f6682c23b6fac4780d297ae4662053d17e58fd52 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/0f0a83e26a9c7fd4b243c315ce07161d2496d83d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.