CVE-2026-31499

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

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: L2CAP: Fix deadlock in l2cap_conn_del()

l2cap_conn_del() calls cancel_delayed_work_sync() for both info_timer and id_addr_timer while holding conn->lock. However, the work functions l2cap_info_timeout() and l2cap_conn_update_id_addr() both acquire conn->lock, creating a potential AB-BA deadlock if the work is already executing when l2cap_conn_del() takes the lock.

Move the work cancellations before acquiring conn->lock and use disable_delayed_work_sync() to additionally prevent the works from being rearmed after cancellation, consistent with the pattern used in hci_conn_del().

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

Published

April 22, 2026

Last Modified

May 14, 2026

Advisory Details (4)

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

Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f26ecbd9cde621dd94be7ef252c7210b965a5c7
generic

Bluetooth: L2CAP: Fix deadlock in l2cap_conn_del() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00fdebbbc557a2fc21321ff2eaa22fd70c078608

Vendor Advisories for CVE-2026-31499(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.88osv

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.88-1~bpo12+1 (21 versions)6.12.88-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1

Weakness Classification(1)

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

All Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 6× in last 7d / 28× 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 180 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31499?
CVE-2026-31499 is a medium vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix deadlock in l2capconndel() l2capconndel() calls canceldelayedworksync() for both infotimer and idaddrtimer while holding conn->lock. However, the work functions l2capinfotimeout() and l2capconnupdateidaddr()…
When was CVE-2026-31499 disclosed?
CVE-2026-31499 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on May 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31499 actively exploited?
CVE-2026-31499 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 99.3% of all scored CVEs.
What is the CVSS score of CVE-2026-31499?
CVE-2026-31499 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31499?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31499, 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-31499

Explore →

Is Your Infrastructure Affected by CVE-2026-31499?

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