CVE-2024-50125: Bluetooth: SCO: Fix UAF on sco_sock_timeout
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: SCO: Fix UAF on sco_sock_timeout
conn->sk maybe have been unlinked/freed while waiting for sco_conn_lock
so this checks if the conn->sk is still valid by checking if it part of
sco_sk_list.
Security readout for executives and security teams
Plain-English summary
A Linux Bluetooth audio flaw can access a socket after its memory has been released during a connection timeout. The supplied CVSS score is 8.0, reflecting potentially serious confidentiality, integrity, and availability impact. Exposure appears limited to affected kernels where Bluetooth SCO functionality is reachable.
Executive priority
Treat this as a high-priority kernel update for Bluetooth-capable Linux fleets, particularly laptops, mobile or embedded devices, and shared environments. It is less urgent for systems without usable Bluetooth SCO exposure. Require package-level validation because the supplied version mapping is not sufficiently clear for decisions based solely on kernel version.
Technical view
CVE-2024-50125 is a CWE-416 use-after-free race in sco_sock_timeout. While code waits for sco_conn_lock, conn->sk may be unlinked and freed. The upstream correction verifies that the socket remains in sco_sk_list before using it. The supplied vector requires adjacent access, low privileges, and no user interaction.
Likely exposure
Prioritize Linux systems using affected kernels with Bluetooth enabled, especially devices supporting SCO audio connections. Internet-only exposure is not indicated by the adjacent-attack vector. The supplied affected-version data contains ambiguous entries, including "0" and duplicate hashes, so confirm distribution-specific package and backport status rather than relying only on version strings.
Exploitation context
The bundle does not identify CVE-2024-50125 as CISA KEV and provides no evidence of active exploitation. Successful exploitation is characterized as adjacent, low-complexity, low-privilege, and requiring no user interaction. The sources do not establish exploit reliability or observed attacks.
Researcher notes
The central condition is socket lifetime changing while sco_sock_timeout waits for sco_conn_lock. The correction uses sco_sk_list membership as a validity check. The bundle supports high theoretical impact through CVSS, but it does not document demonstrated code execution, exploitation in the wild, or a complete distribution-by-distribution affected-version matrix.
Mitigation direction
Apply the distribution kernel update incorporating the referenced Linux stable correction.
Reboot affected systems so the corrected kernel is actually running.
Consult the Linux distribution vendor when package or backport status is unclear.
Prioritize remediation on Bluetooth-enabled endpoints and embedded devices supporting SCO audio.
Validation and detection
Inventory running kernels on systems with Bluetooth hardware or SCO functionality.
Compare installed packages with distribution advisories and referenced upstream stable corrections.
Confirm the corrected kernel is running after maintenance and reboot.
Review kernel logs for Bluetooth or SCO failures, recognizing that clean logs do not prove safety.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
2ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.