Linux Kernel up to 7.1.3 Btmtksdio btmtksdio_txrx_work infinite loop

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.2$0-$5k1.55-

Summaryinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.1.177/6.6.144/6.12.95/6.18.38/7.1.3. This impacts the function btmtksdio_txrx_work of the component Btmtksdio. Executing a manipulation can lead to infinite loop. The identification of this vulnerability is CVE-2026-64409. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.1.177/6.6.144/6.12.95/6.18.38/7.1.3. This vulnerability affects the function btmtksdio_txrx_work of the component Btmtksdio. The manipulation with an unknown input leads to a infinite loop vulnerability. The CWE definition for the vulnerability is CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. As an impact it is known to affect availability. CVE summarizes:

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.

The advisory is available at git.kernel.org. This vulnerability was named CVE-2026-64409 since 07/19/2026. The exploitation appears to be easy. The attack can be initiated remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 07/25/2026). This vulnerability is assigned to T1499 by the MITRE ATT&CK project.

Upgrading to version 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.4 or 7.2-rc1 eliminates this vulnerability. Applying the patch f6682c23b6fac4780d297ae4662053d17e58fd52/466540e045d01fcacf383a5beb8a2dad2fc53a26/7b429d611060e87752e848851815537963726493/0039bdde36b23ccf1196635f1d52c5490481544d/0f0a83e26a9c7fd4b243c315ce07161d2496d83d/a257407e2bbbb099ed427719a50563f67fa366d8 is able to eliminate this problem.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Infinite loop
CWE: CWE-835 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.178/6.6.145/6.12.96/6.18.39/7.1.4/7.2-rc1
Patch: f6682c23b6fac4780d297ae4662053d17e58fd52/466540e045d01fcacf383a5beb8a2dad2fc53a26/7b429d611060e87752e848851815537963726493/0039bdde36b23ccf1196635f1d52c5490481544d/0f0a83e26a9c7fd4b243c315ce07161d2496d83d/a257407e2bbbb099ed427719a50563f67fa366d8

Timelineinfo

07/19/2026 CVE reserved
07/25/2026 +6 days Advisory disclosed
07/25/2026 +0 days VulDB entry created
07/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64409 (🔒)
GCVE (CVE): GCVE-0-2026-64409
GCVE (VulDB): GCVE-100-383194

Entryinfo

Created: 07/25/2026 18:23
Changes: 07/25/2026 18:23 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!