CVE-2026-64409

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

References (6)

Vendor Advisories for CVE-2026-64409(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

(refreshed 10× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 02:29 UTCVendor advisory
  2. 2026-08-30 02:29 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-26 21:14 UTCVendor advisory
  6. 2026-08-26 21:14 UTCGHSA enrichment
  7. 2026-08-26 14:47 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-23 15:46 UTCVendor advisory
  10. 2026-08-23 15:46 UTCGHSA enrichment
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-20 22:55 UTCEPSS rescore
  13. 2026-08-20 10:32 UTCVendor advisory
  14. 2026-08-20 10:32 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 05:25 UTCNVD update
  18. 2026-08-17 05:18 UTCVendor advisory
  19. 2026-08-17 05:18 UTCGHSA enrichment
  20. 2026-08-17 05:05 UTCMITRE cvelistV5
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 20:20 UTCVendor advisory
  24. 2026-08-14 20:20 UTCGHSA enrichment
  25. 2026-08-12 13:51 UTCEPSS rescore
Show 34 more
  1. 2026-08-11 15:06 UTCVendor advisory
  2. 2026-08-11 15:06 UTCGHSA enrichment
  3. 2026-08-11 04:59 UTCVendor advisory
  4. 2026-08-11 04:59 UTCGHSA enrichment
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-09 13:47 UTCEPSS rescore
  7. 2026-08-07 23:45 UTCVendor advisory
  8. 2026-08-07 23:45 UTCGHSA enrichment
  9. 2026-08-06 13:47 UTCEPSS rescore
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-04 18:31 UTCGHSA enrichment
  13. 2026-08-04 15:10 UTCEPSS rescore
  14. 2026-08-04 10:39 UTCEPSS rescore
  15. 2026-08-03 10:36 UTCEPSS rescore
  16. 2026-08-02 02:27 UTCEPSS rescore
  17. 2026-08-01 13:17 UTCEG score recompute
  18. 2026-08-01 13:17 UTCGHSA enrichment
  19. 2026-08-01 04:16 UTCEPSS rescore
  20. 2026-07-30 01:30 UTCEPSS rescore
  21. 2026-07-30 01:30 UTCEPSS rescore
  22. 2026-07-29 08:02 UTCEG score recompute
  23. 2026-07-29 08:02 UTCGHSA enrichment
  24. 2026-07-28 15:37 UTCEPSS rescore
  25. 2026-07-27 14:14 UTCEPSS rescore
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-26 14:54 UTCEPSS rescore
  28. 2026-07-26 02:48 UTCEG score recompute
  29. 2026-07-26 02:48 UTCGHSA enrichment
  30. 2026-07-25 14:18 UTCEPSS rescore
  31. 2026-07-25 14:18 UTCEPSS rescore
  32. 2026-07-25 10:39 UTCNVD update
  33. 2026-07-25 09:30 UTCEG score recompute
  34. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64409?
CVE-2026-64409 is a publicly disclosed vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtksdio: fix infinite loop in btmtksdiotxrxwork() Every once in a while we see a hung btmtksdio_flush() task: INFO: task kworker/u17:0:189 blocked for more than 122 seconds. cancelworktimer+0x3f4/0x460…
When was CVE-2026-64409 disclosed?
CVE-2026-64409 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64409 actively exploited?
CVE-2026-64409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.2% of all scored CVEs.
How do I remediate CVE-2026-64409?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64409, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64409

Explore →

Is Your Infrastructure Affected by CVE-2026-64409?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs