A Leader in the 2026 Gartner® Magic Quadrant™ for Endpoint Protection. Six years running.Six years. Gartner® Magic Quadrant™ Leader.Find Out Why
Experiencing a Breach?Blog
Get StartedContact Us
SentinelOne
  • Platform
    Platform Overview
    • Singularity Platform
      Welcome to Integrated Enterprise Security
    • AI for Security
      Leading the Way in AI-Powered Security Solutions
    • Securing AI
      Accelerate AI Adoption with Secure AI Tools, Apps, and Agents.
    • How It Works
      The Singularity XDR Difference
    • Singularity Marketplace
      One-Click Integrations to Unlock the Power of XDR
    • Pricing & Packaging
      Comparisons and Guidance at a Glance
    Data & AI
    • Purple AI
      Accelerate SecOps with Generative AI
    • Singularity Hyperautomation
      Easily Automate Security Processes
    • AI-SIEM
      The AI SIEM for the Autonomous SOC
    • AI Data Pipelines
      Security Data Pipeline for AI SIEM and Data Optimization
    • Singularity Data Lake
      AI-Powered, Unified Data Lake
    • Singularity Data Lake for Log Analytics
      Seamlessly Ingest Data from On-Prem, Cloud or Hybrid Environments
    Endpoint Security
    • Singularity Endpoint
      Autonomous Prevention, Detection, and Response
    • Singularity XDR
      Native & Open Protection, Detection, and Response
    • Singularity RemoteOps Forensics
      Orchestrate Forensics at Scale
    • Singularity Threat Intelligence
      Comprehensive Adversary Intelligence
    • Singularity Vulnerability Management
      Application & OS Vulnerability Management
    • Singularity Identity
      Identity Threat Detection and Response
    Cloud Security
    • Singularity Cloud Security
      Block Attacks with an AI-Powered CNAPP
    • Singularity Cloud Native Security
      Secure Cloud and Development Resources
    • Singularity Cloud Workload Security
      Real-Time Cloud Workload Protection Platform
    • Singularity Cloud Data Security
      AI-Powered Threat Detection for Cloud Storage
    • Singularity Cloud Security Posture Management
      Detect and Remediate Cloud Misconfigurations
    Securing AI
    • Prompt Security
      Secure AI Tools Across Your Enterprise
  • Why SentinelOne?
    Why SentinelOne?
    • Why SentinelOne?
      Cybersecurity Built for What’s Next
    • Our Customers
      Trusted by the World’s Leading Enterprises
    • Industry Recognition
      Tested and Proven by the Experts
    • About Us
      The Industry Leader in Autonomous Cybersecurity
    Compare SentinelOne
    • Arctic Wolf
    • Broadcom
    • CrowdStrike
    • Cybereason
    • Microsoft
    • Palo Alto Networks
    • Sophos
    • Splunk
    • Trellix
    • Trend Micro
    • Wiz
    Verticals
    • Energy
    • Federal Government
    • Finance
    • Healthcare
    • Higher Education
    • K-12 Education
    • Manufacturing
    • Retail
    • State and Local Government
  • Services
    Managed Services
    • Managed Services Overview
      Wayfinder Threat Detection & Response
    • Threat Hunting
      World-Class Expertise and Threat Intelligence
    • Managed Detection & Response
      24/7/365 Expert MDR Across Your Entire Environment
    • Incident Readiness & Response
      DFIR, Breach Readiness, & Compromise Assessments
    Support, Deployment, & Health
    • Technical Account Management
      Customer Success with Personalized Service
    • SentinelOne GO
      Guided Onboarding & Deployment Advisory
    • SentinelOne University
      Live and On-Demand Training
    • Services Overview
      Comprehensive Solutions for Seamless Security Operations
    • SentinelOne Community
      Community Login
  • Partners
    Our Network
    • MSSP Partners
      Succeed Faster with SentinelOne
    • Singularity Marketplace
      Extend the Power of S1 Technology
    • Cyber Risk Partners
      Enlist Pro Response and Advisory Teams
    • Technology Alliances
      Integrated, Enterprise-Scale Solutions
    • SentinelOne for AWS
      Hosted in AWS Regions Around the World
    • Channel Partners
      Deliver the Right Solutions, Together
    • SentinelOne for Google Cloud
      Unified, Autonomous Security Giving Defenders the Advantage at Global Scale
    • Partner Locator
      Your Go-to Source for Our Top Partners in Your Region
    Partner Portal→
  • Resources
    Resource Center
    • Case Studies
    • Data Sheets
    • eBooks
    • Reports
    • Videos
    • Webinars
    • Whitepapers
    • Events
    View All Resources→
    Blog
    • Feature Spotlight
    • For CISO/CIO
    • From the Front Lines
    • Identity
    • Cloud
    • macOS
    • SentinelOne Blog
    Blog→
    Tech Resources
    • SentinelLABS
    • Ransomware Anthology
    • Cybersecurity 101
  • About
    About SentinelOne
    • About SentinelOne
      The Industry Leader in Cybersecurity
    • Investor Relations
      Financial Information & Events
    • SentinelLABS
      Threat Research for the Modern Threat Hunter
    • Careers
      The Latest Job Opportunities
    • Press & News
      Company Announcements
    • Cybersecurity Blog
      The Latest Cybersecurity Threats, News, & More
    • FAQ
      Get Answers to Our Most Frequently Asked Questions
    • DataSet
      The Live Data Platform
    • S Foundation
      Securing a Safer Future for All
    • S Ventures
      Investing in the Next Generation of Security, Data and AI
  • Pricing
Get StartedContact Us
CVE Vulnerability Database
Vulnerability Database/CVE-2026-31500

CVE-2026-31500: Linux Kernel Race Condition Vulnerability

CVE-2026-31500 is a race condition vulnerability in Linux Kernel's Bluetooth btintel driver that can lead to use-after-free memory corruption. This article covers technical details, affected versions, and mitigation.

Updated: May 14, 2026

CVE-2026-31500 Overview

CVE-2026-31500 is a use-after-free vulnerability [CWE-416] in the Linux kernel's Bluetooth subsystem, specifically in the Intel Bluetooth driver (btintel). The flaw exists in btintel_hw_error(), which issues two __hci_cmd_sync() calls without holding hci_req_sync_lock(). This creates a race condition with hci_dev_do_close() calling btintel_shutdown_combined(), which manipulates hdev->req_status and hdev->req_rsp under the same lock. The close path can free the response skb while the hardware-error recovery path still references it, triggering a slab-use-after-free in kfree_skb().

Critical Impact

A local attacker with low privileges can trigger concurrent execution paths in the Bluetooth stack to cause memory corruption, potentially leading to kernel privilege escalation or denial of service.

Affected Products

  • Linux kernel mainline through 7.0-rc7
  • Linux kernel 4.3 and later stable branches with btintel driver
  • Distributions shipping Intel Bluetooth hardware support via btintel

Discovery Timeline

  • 2026-04-22 - CVE CVE-2026-31500 published to NVD
  • 2026-04-28 - Last updated in NVD database

Technical Details for CVE-2026-31500

Vulnerability Analysis

The vulnerability resides in drivers/bluetooth/btintel.c within the btintel_hw_error() function. This function executes during Bluetooth controller error recovery and issues two synchronous Host Controller Interface (HCI) commands: HCI_OP_RESET and an Intel-specific exception-info retrieval. These calls go through __hci_cmd_sync() at net/bluetooth/hci_sync.c:223, which manipulates hdev->req_status and hdev->req_rsp to track command completion.

The error-recovery path runs without holding hci_req_sync_lock. Concurrently, hci_dev_do_close() invokes btintel_shutdown_combined() at drivers/bluetooth/btintel.c:3648, which also calls __hci_cmd_sync() but under the proper lock. When both paths run simultaneously, the close path frees the response socket buffer first. The still-executing btintel_hw_error() then dereferences the freed skb in kfree_skb(), producing the slab-use-after-free reported by KASAN at net/core/skbuff.c:1202.

Root Cause

The root cause is missing synchronization. The btintel_hw_error() recovery sequence shares state (hdev->req_status, hdev->req_rsp) with every other synchronous HCI command issuer but does not acquire hci_req_sync_lock to serialize access. This violates the locking contract required by __hci_cmd_sync_sk().

Attack Vector

Exploitation requires local access with low privileges on a system using Intel Bluetooth hardware. An attacker triggers controller error conditions while concurrently invoking ioctl operations that drive hci_dev_do_close(). Reliable triggering depends on race-window timing between hci_error_reset() and hci_dev_close_sync(). Successful exploitation produces a use-after-free in kernel slab memory, which can be steered toward arbitrary kernel memory corruption.

No public proof-of-concept exploit is available for CVE-2026-31500. The KASAN report in the upstream commit provides the full call trace from __hci_cmd_sync_sk+0x12f2/0x1c30 through btintel_hw_error+0x186/0x670 and hci_error_reset+0x348/0xa30. See the kernel commit f7d84737 for the fix and full technical context.

Detection Methods for CVE-2026-31500

Indicators of Compromise

  • KASAN reports referencing slab-use-after-free in sk_skb_reason_drop or kfree_skb with call traces through btintel_hw_error and __hci_cmd_sync_sk.
  • Unexpected kernel oops or panics during Bluetooth controller reset or shutdown sequences on systems with Intel Bluetooth adapters.
  • Data-race warnings from KCSAN naming __hci_cmd_sync_sk and btintel_shutdown_combined on hdev->req_rsp.

Detection Strategies

  • Audit installed kernel versions against the patched commits to identify unpatched hosts running vulnerable btintel code.
  • Enable KASAN and KCSAN on test kernels to surface the race and use-after-free during fuzzing of Bluetooth ioctl interfaces.
  • Monitor dmesg and journald for Bluetooth subsystem errors correlated with HCI reset events.

Monitoring Recommendations

  • Track Bluetooth driver crash signatures via centralized log aggregation, focusing on btintel and hci_sync symbols.
  • Alert on repeated hci_error_reset events on the same device, which may indicate attempted race exploitation.
  • Correlate local user ioctl activity against /dev/rfkill and Bluetooth HCI sockets with subsequent kernel error events.

How to Mitigate CVE-2026-31500

Immediate Actions Required

  • Apply the upstream patch that wraps the recovery sequence in hci_req_sync_lock/unlock, as merged in kernel commit f7d84737.
  • Update to a distribution kernel that includes the stable backports listed in the vendor advisories.
  • On systems where Bluetooth is not required, disable the btintel and bluetooth modules to remove the attack surface.

Patch Information

The fix serializes btintel_hw_error() with every other synchronous HCI command issuer by acquiring hci_req_sync_lock for the entire recovery sequence. Stable backports are available across multiple branches:

  • Kernel Commit 5f84e84
  • Kernel Commit 66696648
  • Kernel Commit 94d8e6fe
  • Kernel Commit e10a4cbc
  • Kernel Commit f7d84737

Workarounds

  • Blacklist the btintel kernel module on systems that do not require Intel Bluetooth functionality.
  • Restrict access to Bluetooth HCI sockets and related ioctl interfaces to trusted local users only.
  • Disable Bluetooth at the firmware or BIOS level on servers and fixed-function appliances.
bash
# Configuration example: blacklist btintel until kernel is patched
echo 'blacklist btintel' | sudo tee /etc/modprobe.d/blacklist-btintel.conf
echo 'blacklist btusb'   | sudo tee -a /etc/modprobe.d/blacklist-btintel.conf
sudo rmmod btintel btusb 2>/dev/null
sudo update-initramfs -u

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

  • Vulnerability Details
  • TypeRace Condition

  • Vendor/TechLinux Kernel

  • SeverityHIGH

  • CVSS Score7.8

  • EPSS Probability0.01%

  • Known ExploitedNo
  • CVSS Vector
  • CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
  • Impact Assessment
  • ConfidentialityLow
  • IntegrityNone
  • AvailabilityHigh
  • CWE References
  • CWE-416
  • Vendor Resources
  • Kernel Commit 5f84e84

  • Kernel Commit 66696648

  • Kernel Commit 94d8e6fe

  • Kernel Commit e10a4cbc

  • Kernel Commit f7d84737
  • Related CVEs
  • CVE-2026-46202: Linux Kernel Race Condition Vulnerability

  • CVE-2026-43342: Linux Kernel Race Condition Vulnerability

  • CVE-2026-43340: Linux Kernel Race Condition Vulnerability

  • CVE-2026-43353: Linux Kernel Race Condition Vulnerability
Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.

Try SentinelOne
  • Get Started
  • Get a Demo
  • Product Tour
  • Why SentinelOne
  • Pricing & Packaging
  • FAQ
  • Contact
  • Contact Us
  • Customer Support
  • SentinelOne Status
  • Language
  • Platform
  • Singularity Platform
  • Singularity Endpoint
  • Singularity Cloud
  • Singularity AI-SIEM
  • Singularity Identity
  • Singularity Marketplace
  • Purple AI
  • Services
  • Wayfinder TDR
  • SentinelOne GO
  • Technical Account Management
  • Support Services
  • Verticals
  • Energy
  • Federal Government
  • Finance
  • Healthcare
  • Higher Education
  • K-12 Education
  • Manufacturing
  • Retail
  • State and Local Government
  • Cybersecurity for SMB
  • Resources
  • Blog
  • Labs
  • Case Studies
  • Videos
  • Product Tours
  • Events
  • Cybersecurity 101
  • eBooks
  • Webinars
  • Whitepapers
  • Press
  • News
  • Ransomware Anthology
  • Company
  • About Us
  • Our Customers
  • Careers
  • Partners
  • Legal & Compliance
  • Security & Compliance
  • Investor Relations
  • S Foundation
  • S Ventures

©2026 SentinelOne, All Rights Reserved.

Privacy Notice Terms of Use

English