CVE-2026-31500

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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: btintel: serialize btintel_hw_error() with hci_req_sync_lock

btintel_hw_error() issues two __hci_cmd_sync() calls (HCI_OP_RESET and Intel exception-info retrieval) without holding hci_req_sync_lock(). This lets it race against hci_dev_do_close() -> btintel_shutdown_combined(), which also runs __hci_cmd_sync() under the same lock. When both paths manipulate hdev->req_status/req_rsp concurrently, the close path may free the response skb first, and the still-running hw_error path hits a slab-use-after-free in kfree_skb().

Wrap the whole recovery sequence in hci_req_sync_lock/unlock so it is serialized with every other synchronous HCI command issuer.

Below is the data race report and the kasan report:

BUG: data-race in __hci_cmd_sync_sk / btintel_shutdown_combined

read of hdev->req_rsp at net/bluetooth/hci_sync.c:199 by task kworker/u17:1/83: __hci_cmd_sync_sk+0x12f2/0x1c30 net/bluetooth/hci_sync.c:200 __hci_cmd_sync+0x55/0x80 net/bluetooth/hci_sync.c:223 btintel_hw_error+0x114/0x670 drivers/bluetooth/btintel.c:254 hci_error_reset+0x348/0xa30 net/bluetooth/hci_core.c:1030

write/free by task ioctl/22580: btintel_shutdown_combined+0xd0/0x360 drivers/bluetooth/btintel.c:3648 hci_dev_close_sync+0x9ae/0x2c10 net/bluetooth/hci_sync.c:5246 hci_dev_do_close+0x232/0x460 net/bluetooth/hci_core.c:526

BUG: KASAN: slab-use-after-free in sk_skb_reason_drop+0x43/0x380 net/core/skbuff.c:1202 Read of size 4 at addr ffff888144a738dc by task kworker/u17:1/83: __hci_cmd_sync_sk+0x12f2/0x1c30 net/bluetooth/hci_sync.c:200 __hci_cmd_sync+0x55/0x80 net/bluetooth/hci_sync.c:223 btintel_hw_error+0x186/0x670 drivers/bluetooth/btintel.c:260

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

Published

April 22, 2026

Last Modified

June 1, 2026

Advisory Details (6)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94d8e6fe5d0818e9300e514e095a200bd5ff93ae
generic

Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e041d0aad1d4d43d921ace052e04f4e2cacaed3
generic

Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66696648af477dc87859e5e4b607112f5f29d010
generic

Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f84e845648dfa86e42de5487f1a774b42f0444d

Vendor Advisories for CVE-2026-31500(2)

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.1.175—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 ... 7.2~rc5-1~exp1 (496 versions)——
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-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 (121 versions)6.19.11-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 66× 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 241 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31500?
CVE-2026-31500 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btintel: serialize btintelhwerror() with hcireqsync_lock btintelhwerror() issues two hcicmdsync() calls (HCIOPRESET and Intel exception-info retrieval) without holding hcireqsync_lock(). This lets it race against…
When was CVE-2026-31500 disclosed?
CVE-2026-31500 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31500 actively exploited?
CVE-2026-31500 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-31500?
CVE-2026-31500 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31500?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31500, 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-31500

Explore →

Is Your Infrastructure Affected by CVE-2026-31500?

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

Start Free Scan →Browse All CVEs