CVE-2026-64127

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. 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: L2CAP: ecred_reconfigure: send packed pdu, not stack pointer

Commit 1c08108f3014 ("Bluetooth: L2CAP: Avoid -Wflex-array-member-not-at-end warnings") converted the on-stack request PDU in l2cap_ecred_reconfigure() from an explicit packed struct to DEFINE_RAW_FLEX(), but did not adjust the size and source-pointer arguments to l2cap_send_cmd():

  • struct {
  • struct l2cap_ecred_reconf_req req;
  • __le16 scid;
  • } pdu;
+ DEFINE_RAW_FLEX(struct l2cap_ecred_reconf_req, pdu, scid, 1); ... l2cap_send_cmd(conn, chan->ident, L2CAP_ECRED_RECONF_REQ, sizeof(pdu), &pdu);

After the conversion, DEFINE_RAW_FLEX() expands to declare an anonymous union pdu_u plus a local pointer "pdu" pointing at it. Therefore:

  • sizeof(pdu) is now sizeof(struct l2cap_ecred_reconf_req *) = 8 on
64-bit (4 on 32-bit), not the 6 bytes of (mtu, mps, scid[1]).
  • &pdu is the address of the local pointer's stack storage, not the
address of the request payload.

l2cap_send_cmd() forwards (data, count) to l2cap_build_cmd(), which calls skb_put_data(skb, data, count). The L2CAP_ECRED_RECONFIGURE_REQ packet body therefore contains 8 bytes copied from the kernel stack starting at &pdu -- the 8 bytes overlap the pdu pointer's value, leaking a kernel stack address to the paired Bluetooth peer. The intended (mtu, mps, scid) fields are not transmitted at all, so the peer rejects the request as malformed and the L2CAP_ECRED_RECONFIGURE feature itself has been broken for the local-side initiator since the introducing commit landed.

The sibling site l2cap_ecred_conn_req() in the same commit was converted correctly (sizeof(*pdu) + len, pdu); only this site was missed.

Restore the original semantics: pass the full flex-struct size via struct_size(pdu, scid, 1) and the pdu pointer (the struct address) as the source.

Validated on a stock 7.0-based host kernel via the real call path: setsockopt(SOL_BLUETOOTH, BT_RCVMTU, ...) on a BT_CONNECTED L2CAP_MODE_EXT_FLOWCTL socket emits an L2CAP_ECRED_RECONFIGURE_REQ whose body is 8 bytes (the on-stack pdu local's value) rather than the expected 6. Three captures from fresh socket / fresh hciemu peer on the same host -- low bytes vary per call, high 0xffff confirms a kernel virtual address (KASLR-randomised stack slot, not a fixed string):

RECONF_REQ body (ident=0x02 len=8): 42 fb 54 af 0e ca ff ff RECONF_REQ body (ident=0x02 len=8): 52 3d 2e af 0e ca ff ff RECONF_REQ body (ident=0x02 len=8): b2 fc 5b af 0e ca ff ff

After this patch the body is 6 bytes carrying the expected little-endian (mtu, mps, scid).

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
3%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (4)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

Bluetooth: L2CAP: ecred_reconfigure: send packed pdu, not stack pointer - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: ecred_reconfigure: send packed pdu, not stack pointer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/356c9d1a1cbacd2a1640fff3c050e1c3472e924f
generic

Bluetooth: L2CAP: ecred_reconfigure: send packed pdu, not stack pointer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3374ef8cf99368a40f7efd51a2a375a4c5dc6f0d
generic

Bluetooth: L2CAP: ecred_reconfigure: send packed pdu, not stack pointer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/051922ab709c0a6917eae765c22481dfc68379e5

Vendor Advisories for CVE-2026-64127(1)

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

Patch Availability(5)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 22× in last 7d / 78× 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 108 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64127?
CVE-2026-64127 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: ecred_reconfigure: send packed pdu, not stack pointer Commit 1c08108f3014 ("Bluetooth: L2CAP: Avoid -Wflex-array-member-not-at-end warnings") converted the on-stack request PDU in l2capecredreconfigure() from an…
When was CVE-2026-64127 disclosed?
CVE-2026-64127 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64127 actively exploited?
CVE-2026-64127 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.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64127?
CVE-2026-64127 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64127?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64127, 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-64127

Explore →

Is Your Infrastructure Affected by CVE-2026-64127?

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