CVE-2026-64409
Last modified
CVE-2026-64409 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.17, < 6.1.178 |
| Linux | Linux Kernel | >= 6.2, < 6.6.145 |
| Linux | Linux Kernel | >= 6.7, < 6.12.96 |
| Linux | Linux Kernel | >= 6.13, < 6.18.39 |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64409?
How severe is CVE-2026-64409?
How do I fix CVE-2026-64409?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64403In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64404In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64405In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64406In the Linux kernel, the following vulnerability has been re…8
- CVE-2026-64407In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64408In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-6441The Canto plugin for WordPress is vulnerable to Missing Auth…4.3
- CVE-2026-64410In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64411In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64412In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64413In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-64414In the Linux kernel, the following vulnerability has been re…7.5
Are you affected by CVE-2026-64409?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
