CVE-2026-64573 — Bluetooth: qca: fix NVM tag length underflow in TLV parser
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: fix NVM tag length underflow in TLV parser In the TLV_TYPE_NVM branch of qca_tlv_check_data() the tag loop bound is "while (idx < length - sizeof(struct tlv_type_nvm))". "length" is a signed int from the firmware TLV header and sizeof(struct tlv_type_nvm) is a size_t (12), so "length" is converted to size_t and any firmware-supplied "length" < 12 makes the subtraction wrap to a huge value. The loop body then reads a 12-byte struct tlv_type_nvm past the end of the short vmalloc'd firmware buffer (and the EDL_TAG_ID_* handlers can write past it). Rewrite the bound as "idx + sizeof(struct tlv_type_nvm) <= length"; both operands are non-negative, so it no longer underflows and a "length" too small for one record correctly skips the loop. BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421) Read of size 2 at addr ffffc900000e5004 by task kworker/u9:0/52 Workqueue: hci0 hci_power_on Call Trace: ... kasan_report (mm/kasan/report.c:595) qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617) qca_uart_setup (drivers/bluetooth/btqca.c:948) qca_setup (drivers/bluetooth/hci_qca.c:2029) hci_uart_setup (drivers/bluetooth/hci_ldisc.c:438) hci_dev_open_sync (net/bluetooth/hci_sync.c:5227) hci_power_on (net/bluetooth/hci_core.c:920) process_one_work (kernel/workqueue.c:3322) worker_thread (kernel/workqueue.c:3486) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245)
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ ed53949cc92e28aaa3463d246942bda1fbb7f307 and < a7ee11441d71ab036a705d110a415421f5a4a898≥ 1caceadfb50432dbf6d808796cb6c34ebb6d662c and < 5d34e537755d2f9eba2d4e54d70126f987ef20b4≥ 427281f9498ed614f9aabc80e46ec077c487da6d and < 70354dbb5f72d9a76da7b031de3cbaf6c7d8fc24≥ 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d and < 59fd2f075bca94f030c7c78e94878ea0803d7690≥ 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d and < a087ed960fce54e9302796229e9d545bbc9bcd4a≥ 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d and < 4fcfb5b2c736785464ff9745f94c6726c5ee2d85≥ 2e4edfa1e2bd821a317e7d006517dcf2f3fac68d and < c90164ca0f7036942ba088eb7ea8d3f6c2352020version 02f05ed44b71152d5e11d29be28aed91c0489b4e and 5 more≥ 5.15.159 and < 5.15.216≥ 6.1.91 and < 6.1.183≥ 6.6.31 and < 6.6.148≥ 6.8.10 and < 6.9version 6.9 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.16%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
7 on the record
- git.kernel.org/stable/c/59fd2f075bca94f030c7c78e94878ea0803d7690
- git.kernel.org/stable/c/70354dbb5f72d9a76da7b031de3cbaf6c7d8fc24
- git.kernel.org/stable/c/a087ed960fce54e9302796229e9d545bbc9bcd4a
- git.kernel.org/stable/c/4fcfb5b2c736785464ff9745f94c6726c5ee2d85
- git.kernel.org/stable/c/5d34e537755d2f9eba2d4e54d70126f987ef20b4
- git.kernel.org/stable/c/c90164ca0f7036942ba088eb7ea8d3f6c2352020
- git.kernel.org/stable/c/a7ee11441d71ab036a705d110a415421f5a4a898
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 3d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 3d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 3d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 3d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 3d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-64573 is "Bluetooth: qca: fix NVM tag length underflow in TLV parser", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.16% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.