CVE-2026-72336

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: 6lowpan: hold L2CAP conn across debugfs control

get_l2cap_conn() looks up an LE hci_conn under hdev protection, but then drops that protection before reading hcon->l2cap_data and before lowpan_control_write() later dereferences conn->hcon. A disconnect or device close can tear down the same L2CAP connection in that window.

The buggy scenario involves two paths, with each column showing the order within that path:

6LoWPAN control write: HCI disconnect/device close:

  • get_l2cap_conn() finds hcon 1. hci_disconn_cfm() dispatches
and hcon->l2cap_data. the L2CAP disconnect callback.
  • get_l2cap_conn() drops hdev 2. l2cap_conn_del() clears
protection and returns conn. hcon->l2cap_data and drops the L2CAP connection reference.
  • lowpan_control_write() reads 3. hci_conn_del() removes and drops
conn->hcon. the HCI connection.

Take a reference to the L2CAP connection with l2cap_conn_hold_unless_zero() while hdev is still locked, and drop that reference after the debugfs command's last use of conn. This mirrors the existing L2CAP ACL receive-side handoff and keeps the connection dereferenceable after leaving hdev protection. Export the existing helper so the bluetooth_6lowpan module can use the same lifetime primitive.

Validation reproduced this kernel report: BUG: KASAN: slab-use-after-free in lowpan_control_write+0x374/0x520 The buggy address belongs to the object at ffff888111b9d000 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 0 bytes inside of freed 1024-byte region [ffff888111b9d000, ffff888111b9d400) Read of size 8 Call trace: dump_stack_lvl+0x66/0xa0 print_report+0xce/0x5f0 lowpan_control_write+0x374/0x520 (net/bluetooth/6lowpan.c:1131) srso_alias_return_thunk+0x5/0xfbef5 __virt_addr_valid+0x19f/0x330 kasan_report+0xe0/0x110 __debugfs_file_get+0xf7/0x400 full_proxy_write+0x9e/0xd0 vfs_write+0x1b0/0x810 ksys_write+0xd2/0x170 dnotify_flush+0x32/0x220 do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f Allocated by task stack: kasan_save_stack+0x33/0x60 kasan_save_track+0x17/0x60 __kasan_kmalloc+0xaa/0xb0 l2cap_conn_add+0x45/0x520 l2cap_chan_connect+0xac6/0xd90 l2cap_sock_connect+0x216/0x350 __sys_connect+0x101/0x130 __x64_sys_connect+0x40/0x50 do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task stack: kasan_save_stack+0x33/0x60 kasan_save_track+0x17/0x60 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x5f/0x80 kfree+0x313/0x590 hci_conn_hash_flush+0xc0/0x140 hci_dev_close_sync+0x41a/0xb00 hci_dev_close+0x12f/0x160 hci_sock_ioctl+0x157/0x570 sock_do_ioctl+0xf7/0x210 sock_ioctl+0x32f/0x490 __x64_sys_ioctl+0xc7/0x110 do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f kasan_record_aux_stack+0xa7/0xc0 insert_work+0x32/0x100 __queue_work+0x262/0xa60 queue_work_on+0xad/0xb0 l2cap_connect_cfm+0x4ef/0x670 hci_le_remote_feat_complete_evt+0x247/0x430 hci_event_packet+0x360/0x6f0 hci_rx_work+0x2ae/0x7a0 process_one_work+0x4fd/0xbc0 worker_thread+0x2d8/0x570 kthread+0x1ad/0x1f0 ret_from_fork+0x3c9/0x540 ret_from_fork_asm+0x1a/0x30

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.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 15, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-72336(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Data Freshness Timeline

(refreshed 8× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 84 are merged into the row they repeat.

  1. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-18 03:16 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-12 15:42 UTCEG score recompute
  11. 2026-10-11 19:27 UTCEG score recompute
  12. 2026-10-11 16:43 UTCEG score recompute
  13. 2026-10-11 14:03 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-04 14:42 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-01 10:18 UTCEG score recompute
  25. 2026-10-01 10:18 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
Show 55 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-09-28 06:31 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-09-25 02:43 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  7. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-09-21 20:40 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  10. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-09-18 16:52 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  13. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-09-15 12:03 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  16. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-09-12 08:09 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  19. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-09-09 04:20 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  22. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-05 06:11 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  25. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  26. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  27. 2026-09-02 02:15 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  28. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  29. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  30. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  31. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  32. 2026-08-29 22:19 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  33. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  34. 2026-08-26 18:31 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  35. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  36. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  37. 2026-08-23 14:06 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  38. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  39. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  40. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  41. 2026-08-20 10:17 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  42. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  43. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  44. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  45. 2026-08-17 06:29 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  46. 2026-08-17 06:22 UTCNVD update
  47. 2026-08-17 05:30 UTCEG score recompute
  48. 2026-08-17 05:30 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  49. 2026-08-17 05:24 UTCMITRE cvelistV5
  50. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  51. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  52. 2026-08-15 06:36 UTCGHSA enrichmentGHSA-53r8-c46r-w2fg
  53. 2026-08-15 06:23 UTCNVD update
  54. 2026-08-15 06:06 UTCEG score recompute
  55. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-72336?
CVE-2026-72336 is a vulnerability whose severity is not yet rated; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: 6lowpan: hold L2CAP conn across debugfs control getl2capconn() looks up an LE hci_conn under hdev protection, but then drops that protection before reading hcon->l2cap_data and before lowpancontrolwrite() later…
When was the CVE record for CVE-2026-72336 published?
The CVE record for CVE-2026-72336 was published on August 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-72336 actively exploited?
CVE-2026-72336 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-72336?
A fix for CVE-2026-72336 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72336 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-72336?

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