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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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)
EPSS
2.6%
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.

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.