CVE-2026-64409

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 25, 2026

Last Modified

September 4, 2026

Advisory Details (6)

Auto-updated Sep 4, 2026
No patch confirmed yet.
generic

Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f6682c23b6fac4780d297ae4662053d17e58fd52
generic

Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a257407e2bbbb099ed427719a50563f67fa366d8
generic

Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7b429d611060e87752e848851815537963726493
generic

Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/466540e045d01fcacf383a5beb8a2dad2fc53a26
generic

Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f0a83e26a9c7fd4b243c315ce07161d2496d83d
generic

Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0039bdde36b23ccf1196635f1d52c5490481544d

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.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-20ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-20ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-20ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-09-20ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-20ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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 (158 versions)7.1.4-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 18× in last 7d / 63× 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.

Showing the most recent 100 of 111 total refreshes for this CVE.

  1. 2026-09-20 01:24 UTCEG score recompute
  2. 2026-09-20 01:24 UTCVendor advisory
  3. 2026-09-20 01:24 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 02:44 UTCEG score recompute
  6. 2026-09-18 02:44 UTCVendor advisory
  7. 2026-09-18 02:44 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 11:56 UTCEG score recompute
  10. 2026-09-16 11:56 UTCVendor advisory
  11. 2026-09-16 11:55 UTCGHSA enrichment
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 09:22 UTCEG score recompute
  14. 2026-09-15 09:22 UTCVendor advisory
  15. 2026-09-15 09:22 UTCGHSA enrichment
  16. 2026-09-13 21:25 UTCEG score recompute
  17. 2026-09-13 21:25 UTCVendor advisory
  18. 2026-09-13 21:25 UTCGHSA enrichment
  19. 2026-09-12 17:40 UTCEG score recompute
  20. 2026-09-12 17:40 UTCVendor advisory
  21. 2026-09-12 17:40 UTCGHSA enrichment
  22. 2026-09-11 16:21 UTCEG score recompute
  23. 2026-09-11 16:21 UTCVendor advisory
  24. 2026-09-11 16:21 UTCGHSA enrichment
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 09:37 UTCEPSS rescore
  2. 2026-09-10 13:17 UTCEG score recompute
  3. 2026-09-10 13:17 UTCVendor advisory
  4. 2026-09-10 13:17 UTCGHSA enrichment
  5. 2026-09-09 08:35 UTCEG score recompute
  6. 2026-09-09 08:35 UTCVendor advisory
  7. 2026-09-09 08:34 UTCGHSA enrichment
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-07 21:14 UTCEG score recompute
  10. 2026-09-07 21:14 UTCVendor advisory
  11. 2026-09-07 21:14 UTCGHSA enrichment
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-05 19:20 UTCEG score recompute
  14. 2026-09-05 19:20 UTCVendor advisory
  15. 2026-09-05 19:20 UTCGHSA enrichment
  16. 2026-09-05 15:31 UTCEPSS rescore
  17. 2026-09-04 15:30 UTCEG score recompute▲ 5.50
  18. 2026-09-04 15:30 UTCVendor advisory
  19. 2026-09-04 15:30 UTCGHSA enrichment
  20. 2026-09-04 15:29 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  21. 2026-09-04 12:40 UTCVendor advisory
  22. 2026-09-04 12:39 UTCGHSA enrichment
  23. 2026-09-04 05:07 UTCEPSS rescore
  24. 2026-09-02 14:12 UTCEPSS rescore
  25. 2026-09-01 13:54 UTCEPSS rescore
  26. 2026-09-01 04:40 UTCEPSS rescore
  27. 2026-08-30 19:17 UTCEPSS rescore
  28. 2026-08-30 02:29 UTCVendor advisory
  29. 2026-08-30 02:29 UTCGHSA enrichment
  30. 2026-08-30 01:22 UTCEPSS rescore
  31. 2026-08-28 21:42 UTCEPSS rescore
  32. 2026-08-26 21:14 UTCVendor advisory
  33. 2026-08-26 21:14 UTCGHSA enrichment
  34. 2026-08-26 14:47 UTCEPSS rescore
  35. 2026-08-25 13:49 UTCEPSS rescore
  36. 2026-08-23 15:46 UTCVendor advisory
  37. 2026-08-23 15:46 UTCGHSA enrichment
  38. 2026-08-21 23:49 UTCEPSS rescore
  39. 2026-08-20 22:55 UTCEPSS rescore
  40. 2026-08-20 10:32 UTCVendor advisory
  41. 2026-08-20 10:32 UTCGHSA enrichment
  42. 2026-08-19 17:04 UTCEPSS rescore
  43. 2026-08-17 13:47 UTCEPSS rescore
  44. 2026-08-17 05:25 UTCNVD update
  45. 2026-08-17 05:18 UTCVendor advisory
  46. 2026-08-17 05:18 UTCGHSA enrichment
  47. 2026-08-17 05:05 UTCMITRE cvelistV5
  48. 2026-08-16 14:56 UTCEPSS rescore
  49. 2026-08-15 01:30 UTCEPSS rescore
  50. 2026-08-14 20:20 UTCVendor advisory
  51. 2026-08-14 20:20 UTCGHSA enrichment
  52. 2026-08-12 13:51 UTCEPSS rescore
  53. 2026-08-11 15:06 UTCVendor advisory
  54. 2026-08-11 15:06 UTCGHSA enrichment
  55. 2026-08-11 04:59 UTCVendor advisory
  56. 2026-08-11 04:59 UTCGHSA enrichment
  57. 2026-08-11 00:00 UTCEPSS rescore
  58. 2026-08-09 13:47 UTCEPSS rescore
  59. 2026-08-07 23:45 UTCVendor advisory
  60. 2026-08-07 23:45 UTCGHSA enrichment
  61. 2026-08-06 13:47 UTCEPSS rescore
  62. 2026-08-05 19:17 UTCEPSS rescore
  63. 2026-08-05 19:17 UTCEPSS rescore
  64. 2026-08-04 18:31 UTCGHSA enrichment
  65. 2026-08-04 15:10 UTCEPSS rescore
  66. 2026-08-04 10:39 UTCEPSS rescore
  67. 2026-08-03 10:36 UTCEPSS rescore
  68. 2026-08-02 02:27 UTCEPSS rescore
  69. 2026-08-01 13:17 UTCEG score recompute
  70. 2026-08-01 13:17 UTCGHSA enrichment
  71. 2026-08-01 04:16 UTCEPSS rescore
  72. 2026-07-30 01:30 UTCEPSS rescore
  73. 2026-07-30 01:30 UTCEPSS rescore
  74. 2026-07-29 08:02 UTCEG score recompute
  75. 2026-07-29 08:02 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64409?
CVE-2026-64409 is a medium 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 September 4, 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 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64409?
CVE-2026-64409 has a CVSS v3 base score of 5.5 (NVD).
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