- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 23 days later
· 23 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (11 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 26270bc189ea4b5a8356ec99561357fc87f00b32 – < f6682c23b6fac4780d297ae4662053d17e58fd52
- affected 26270bc189ea4b5a8356ec99561357fc87f00b32 – < 466540e045d01fcacf383a5beb8a2dad2fc53a26
- affected 26270bc189ea4b5a8356ec99561357fc87f00b32 – < 7b429d611060e87752e848851815537963726493
- affected 26270bc189ea4b5a8356ec99561357fc87f00b32 – < 0039bdde36b23ccf1196635f1d52c5490481544d
- affected 26270bc189ea4b5a8356ec99561357fc87f00b32 – < 0f0a83e26a9c7fd4b243c315ce07161d2496d83d
- affected 26270bc189ea4b5a8356ec99561357fc87f00b32 – < a257407e2bbbb099ed427719a50563f67fa366d8
- affected 5.17
- unaffected < 5.17
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/f6682c23b6fac4780d297ae4662053d17e58fd52 (opens in a new tab)
- https://git.kernel.org/stable/c/466540e045d01fcacf383a5beb8a2dad2fc53a26 (opens in a new tab)
- https://git.kernel.org/stable/c/7b429d611060e87752e848851815537963726493 (opens in a new tab)
- https://git.kernel.org/stable/c/0039bdde36b23ccf1196635f1d52c5490481544d (opens in a new tab)
- https://git.kernel.org/stable/c/0f0a83e26a9c7fd4b243c315ce07161d2496d83d (opens in a new tab)
- https://git.kernel.org/stable/c/a257407e2bbbb099ed427719a50563f67fa366d8 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-48953 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64409)Record last updated .