CVE-2026-31393

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-04-03. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access

l2cap_information_rsp() checks that cmd_len covers the fixed l2cap_info_rsp header (type + result, 4 bytes) but then reads rsp->data without verifying that the payload is present:

  • L2CAP_IT_FEAT_MASK calls get_unaligned_le32(rsp->data), which reads
4 bytes past the header (needs cmd_len >= 8).
  • L2CAP_IT_FIXED_CHAN reads rsp->data[0], 1 byte past the header
(needs cmd_len >= 5).

A truncated L2CAP_INFO_RSP with result == L2CAP_IR_SUCCESS triggers an out-of-bounds read of adjacent skb data.

Guard each data access with the required payload length check. If the payload is too short, skip the read and let the state machine complete with safe defaults (feat_mask and remote_fixed_chan remain zero from kzalloc), so the info timer cleanup and l2cap_conn_start() still run and the connection is not stalled.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

April 3, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated May 6, 2026
No patch confirmed yet.
generic

Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9aeacde4da0f02d42fd968fd32f245828b230171
generic

Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/807bd1258453c4c83f6ae9dbc1e7b44860ff40d0
generic

Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5229e7d15771eac2b5886bfb1f976aea0c1eec14
generic

Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/187e6fe939295be36063a1d91f8bebee04399a8c

Vendor Advisories for CVE-2026-31393(1)

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

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-05ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-05ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-05ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-05ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-05ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-05ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-05ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-05ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-05ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-05ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-05ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-05ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-05ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-05ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-05ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-05ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-05ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-05ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-05ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-05ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-05ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-05ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-05ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-05ubuntu
linuxKernel @ 5.10.253—osv

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:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 32× 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 222 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31393?
CVE-2026-31393 is a high vulnerability published on April 3, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Validate L2CAPINFORSP payload length before access l2capinformationrsp() checks that cmd_len covers the fixed l2capinforsp header (type + result, 4 bytes) but then reads rsp->data without verifying that the…
When was CVE-2026-31393 disclosed?
CVE-2026-31393 was first published in the National Vulnerability Database on April 3, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31393 actively exploited?
CVE-2026-31393 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 82.8% of all scored CVEs.
What is the CVSS score of CVE-2026-31393?
CVE-2026-31393 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-31393?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31393, 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-31393

Explore →

Is Your Infrastructure Affected by CVE-2026-31393?

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

Start Free Scan →Browse All CVEs