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-31408

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

CVE-2026-31408 is a use-after-free flaw in the Linux kernel Bluetooth SCO component caused by improper socket reference handling. This vulnerability allows potential exploitation during concurrent operations. Learn the technical details, affected versions, impact, and mitigation strategies.

Updated: May 16, 2026

CVE-2026-31408 Overview

CVE-2026-31408 is a use-after-free vulnerability in the Linux kernel's Bluetooth Synchronous Connection-Oriented (SCO) subsystem. The flaw resides in sco_recv_frame(), which reads conn->sk under sco_conn_lock() but releases the lock without holding a reference to the socket. A concurrent close() operation can free the socket between the lock release and the subsequent sk->sk_state access. An attacker within Bluetooth range can exploit this race condition to corrupt kernel memory, potentially achieving code execution or causing a denial of service.

Critical Impact

Adjacent-network attackers can trigger kernel memory corruption through concurrent Bluetooth SCO socket operations, leading to potential code execution with kernel privileges.

Affected Products

  • Linux kernel Bluetooth SCO subsystem
  • Multiple stable kernel branches receiving backported fixes
  • Systems with Bluetooth hardware and SCO functionality enabled

Discovery Timeline

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

Technical Details for CVE-2026-31408

Vulnerability Analysis

The vulnerability is a classic use-after-free race condition in the Linux kernel Bluetooth stack. The sco_recv_frame() function processes incoming SCO frames and retrieves the associated socket from the connection structure. The function acquires sco_conn_lock() to read conn->sk, then releases the lock before accessing the socket's state via sk->sk_state. This window between lock release and socket access creates an exploitable race condition.

A concurrent socket close() operation on another CPU can free the socket structure during this window. When sco_recv_frame() subsequently dereferences sk, it operates on freed memory. The vulnerability requires Bluetooth proximity, making it exploitable across the adjacent network attack surface.

Root Cause

The root cause is missing reference counting on the socket object. While companion functions in the same file, including sco_sock_timeout() and sco_conn_del(), correctly call sco_sock_hold() to acquire a reference before releasing the lock, sco_recv_frame() omitted this safety pattern. This inconsistency between functions handling the same shared object created the race window.

Attack Vector

Exploitation requires an attacker within Bluetooth radio range of the target device. The attacker must trigger SCO frame reception concurrently with socket close operations to win the race. Successful exploitation can corrupt kernel heap memory, enabling privilege escalation, kernel code execution, or system crashes.

The upstream fix takes a socket reference using sco_sock_hold() before releasing the lock and adds sock_put() on all exit paths to balance the reference count. Patch details are available in the Linux Kernel Commit b0a7da0e3f74 and related backport commits.

Detection Methods for CVE-2026-31408

Indicators of Compromise

  • Unexpected kernel oops or panic messages referencing sco_recv_frame, sk_state, or the Bluetooth SCO subsystem in dmesg output
  • KASAN reports identifying use-after-free conditions in net/bluetooth/sco.c
  • Abnormal Bluetooth subsystem crashes correlated with active SCO connections
  • Unexplained kernel privilege escalation events on systems with active Bluetooth interfaces

Detection Strategies

  • Enable Kernel Address Sanitizer (KASAN) on test systems to surface use-after-free conditions in the SCO code path
  • Monitor kernel logs for Bluetooth subsystem warnings and panics referencing socket state access
  • Audit installed kernel versions against the patched commits listed in the upstream references
  • Deploy endpoint telemetry that captures kernel crash signatures and correlates them with Bluetooth activity

Monitoring Recommendations

  • Track Bluetooth device pairings and SCO connection establishment on managed endpoints
  • Alert on repeated kernel crashes on Bluetooth-enabled hosts, particularly servers and workstations with wireless headsets
  • Centralize kernel ring buffer logs for retrospective analysis of memory corruption indicators
  • Inventory Linux kernel versions across the fleet to identify hosts running unpatched builds

How to Mitigate CVE-2026-31408

Immediate Actions Required

  • Apply the upstream Linux kernel patches referenced in the NVD entry as soon as distribution updates become available
  • Identify Linux endpoints with Bluetooth hardware and prioritize them for patching
  • Disable the Bluetooth stack on systems that do not require it using systemctl disable --now bluetooth
  • Unload the SCO kernel module on systems where Bluetooth audio is not needed with modprobe -r bnep sco

Patch Information

The fix is committed across multiple stable kernel branches. Reference patches include Linux Kernel Commit 108b81514d8f, Linux Kernel Commit 45aaca995e4a, Linux Kernel Commit 598dbba9919c, Linux Kernel Commit 7197462e90b8, Linux Kernel Commit b0a7da0e3f74, Linux Kernel Commit d57384e27d1e, and Linux Kernel Commit e76e8f0581ef. Consult your Linux distribution vendor for backported kernel updates.

Workarounds

  • Disable the Bluetooth controller via firmware or operating system settings on devices that do not use it
  • Blacklist the bluetooth, bnep, and related modules through /etc/modprobe.d/ to prevent kernel loading
  • Restrict physical proximity access to high-value Linux hosts to reduce the adjacent network attack surface
  • Enforce least-privilege policies and kernel hardening features such as SMEP, SMAP, and KASLR
bash
# Configuration example: disable Bluetooth and SCO modules
sudo systemctl disable --now bluetooth.service
echo "blacklist bluetooth" | sudo tee /etc/modprobe.d/blacklist-bluetooth.conf
echo "blacklist bnep"      | sudo tee -a /etc/modprobe.d/blacklist-bluetooth.conf
echo "install sco /bin/true" | sudo tee -a /etc/modprobe.d/blacklist-bluetooth.conf
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
  • TypeUse After Free

  • Vendor/TechLinux Kernel

  • SeverityHIGH

  • CVSS Score8.8

  • EPSS Probability0.03%

  • Known ExploitedNo
  • CVSS Vector
  • CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Impact Assessment
  • ConfidentialityLow
  • IntegrityNone
  • AvailabilityHigh
  • Technical References
  • Linux Kernel Commit Change 1

  • Linux Kernel Commit Change 2

  • Linux Kernel Commit Change 3

  • Linux Kernel Commit Change 4

  • Linux Kernel Commit Change 5

  • Linux Kernel Commit Change 6

  • Linux Kernel Commit Change 7
  • Related CVEs
  • CVE-2026-46241: Linux Kernel Use-After-Free Vulnerability

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

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

  • CVE-2026-46222: Linux Kernel Use-After-Free 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