Join the Cyber Forum: Threat Intel on May 12, 2026 to learn how AI is reshaping threat defense.Join the Virtual Cyber Forum: Threat IntelRegister Now
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-31408

CVE-2026-31408: Linux Kernel Bluetooth Use-After-Free

CVE-2026-31408 is a use-after-free vulnerability in the Linux kernel Bluetooth SCO component caused by improper socket reference handling. This article covers the technical details, affected versions, and mitigation.

Published: April 10, 2026

CVE-2026-31408 Overview

CVE-2026-31408 is a use-after-free vulnerability in the Linux kernel's Bluetooth SCO (Synchronous Connection-Oriented) subsystem. The vulnerability exists in the sco_recv_frame() function, which reads conn->sk under sco_conn_lock() but immediately releases the lock without holding a reference to the socket. This race condition allows a concurrent close() operation to free the socket between the lock release and the subsequent sk->sk_state access, resulting in a use-after-free condition.

Critical Impact

A local attacker can exploit this race condition to cause kernel memory corruption, potentially leading to denial of service or arbitrary code execution with kernel privileges.

Affected Products

  • Linux kernel (Bluetooth SCO subsystem)
  • Linux systems with Bluetooth functionality enabled
  • Kernel versions prior to the security patches

Discovery Timeline

  • 2026-04-06 - CVE-2026-31408 published to NVD
  • 2026-04-07 - Last updated in NVD database

Technical Details for CVE-2026-31408

Vulnerability Analysis

The use-after-free vulnerability stems from improper socket reference handling in the Bluetooth SCO subsystem. When sco_recv_frame() processes incoming SCO data, it accesses the socket pointer (conn->sk) while holding the sco_conn_lock(). However, the function releases this lock before performing operations that depend on the socket's validity, specifically before accessing sk->sk_state.

This creates a critical Time-of-Check Time-of-Use (TOCTOU) race window. During this window, another thread executing close() on the same socket can deallocate the socket structure. When the original thread subsequently attempts to access the freed socket memory, it triggers a use-after-free condition.

The kernel developers noted that other functions in the same file, such as sco_sock_timeout() and sco_conn_del(), correctly use sco_sock_hold() to safely maintain a reference under the lock, demonstrating the established pattern for safe socket reference handling in this codebase.

Root Cause

The root cause is a missing call to sco_sock_hold() before releasing the sco_conn_lock() in the sco_recv_frame() function. Without this reference increment, the socket can be freed by a concurrent operation while still being accessed. The fix involves using sco_sock_hold() to take a reference before releasing the lock and adding corresponding sock_put() calls on all exit paths to properly decrement the reference count.

Attack Vector

An attacker with local access to a Linux system with Bluetooth enabled could exploit this vulnerability by:

  1. Establishing a Bluetooth SCO connection to the target system
  2. Triggering concurrent socket receive and close operations
  3. Timing the operations to hit the race condition window
  4. Exploiting the resulting use-after-free for memory corruption or privilege escalation

The vulnerability requires local access and the ability to interact with Bluetooth subsystem APIs, but successful exploitation could result in kernel-level code execution or system denial of service.

Detection Methods for CVE-2026-31408

Indicators of Compromise

  • Kernel oops or panic messages referencing sco_recv_frame() or related Bluetooth SCO functions
  • Unexpected system crashes when Bluetooth SCO connections are active
  • Memory corruption artifacts in kernel logs related to the Bluetooth subsystem
  • KASAN (Kernel Address Sanitizer) reports indicating use-after-free in net/bluetooth/sco.c

Detection Strategies

  • Deploy kernel memory debugging tools such as KASAN to detect use-after-free conditions in production or testing environments
  • Monitor kernel logs for warnings or crashes associated with Bluetooth SCO subsystem functions
  • Implement runtime integrity monitoring to detect unexpected kernel behavior patterns
  • Use SentinelOne's kernel-level behavioral analysis to identify exploitation attempts targeting race conditions

Monitoring Recommendations

  • Enable kernel debugging options such as CONFIG_DEBUG_KMEMLEAK and CONFIG_KASAN in test environments
  • Configure syslog alerting for kernel warnings and panics related to Bluetooth modules
  • Monitor Bluetooth connection activity for unusual patterns that may indicate exploitation attempts
  • Deploy endpoint detection and response (EDR) solutions capable of identifying kernel-level anomalies

How to Mitigate CVE-2026-31408

Immediate Actions Required

  • Update the Linux kernel to a patched version that includes the fix for CVE-2026-31408
  • If immediate patching is not possible, consider disabling Bluetooth functionality on affected systems
  • Review and restrict local access to systems where Bluetooth is required
  • Monitor affected systems for signs of exploitation while patches are being deployed

Patch Information

The Linux kernel team has released patches addressing this vulnerability across multiple stable kernel branches. The fix involves adding proper socket reference counting using sco_sock_hold() before releasing the connection lock and ensuring sock_put() is called on all exit paths.

Patches are available in the following kernel commits:

  • Kernel Git Commit 108b815
  • Kernel Git Commit 45aaca9
  • Kernel Git Commit 598dbba
  • Kernel Git Commit 7197462
  • Kernel Git Commit e76e8f0

Workarounds

  • Disable Bluetooth functionality at the kernel level by blacklisting the bluetooth and btusb modules
  • Restrict access to Bluetooth-related system calls using seccomp profiles or SELinux/AppArmor policies
  • Implement network segmentation to limit Bluetooth exposure on critical systems
  • Use physical Bluetooth disable switches where available on affected hardware
bash
# Temporarily disable Bluetooth kernel modules
echo "blacklist bluetooth" >> /etc/modprobe.d/blacklist-bluetooth.conf
echo "blacklist btusb" >> /etc/modprobe.d/blacklist-bluetooth.conf
modprobe -r btusb bluetooth

# Verify Bluetooth modules are not loaded
lsmod | grep bluetooth

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

  • Vulnerability Details
  • TypeUse After Free

  • Vendor/TechLinux Kernel

  • SeverityNONE

  • CVSS ScoreN/A

  • EPSS Probability0.01%

  • Known ExploitedNo
  • Impact Assessment
  • ConfidentialityNone
  • IntegrityNone
  • AvailabilityNone
  • Technical References
  • Kernel Git Commit Update

  • Kernel Git Commit Update

  • Kernel Git Commit Update

  • Kernel Git Commit Update

  • Kernel Git Commit Update
  • Related CVEs
  • CVE-2026-31475: Linux Kernel Use-After-Free Vulnerability

  • CVE-2026-31469: Linux Kernel Use-After-Free Vulnerability

  • CVE-2026-31457: Linux Kernel Use-After-Free Vulnerability

  • CVE-2026-31444: Linux Kernel Use-After-Free Vulnerability
Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the World’s Most Advanced Cybersecurity Platform

See how our intelligent, autonomous cybersecurity platform can protect your organization now 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