CVE-2024-24858: Race condition vulnerability in Linux kernel net/bluetooth in {conn,adv}_{min,max}_interval_set()
A race condition was found in the Linux kernel's net/bluetooth in {conn,adv}_{min,max}_interval_set() function. This can result in I2cap connection or broadcast abnormality issue, possibly leading to denial of service.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Bluetooth race condition that can disrupt Bluetooth connections or broadcasts and potentially cause denial of service. The public record rates it medium severity because exploitation appears constrained by adjacent access, high privileges, high complexity, and user interaction.
Executive priority
Treat as a moderate operational availability risk, not an internet-scale emergency. Prioritize normal kernel patching, with higher urgency for Bluetooth-enabled endpoints, embedded devices, and operational technology covered by vendor advisories.
Technical view
CVE-2024-24858 is CWE-362 in Linux kernel net/bluetooth {conn,adv}_{min,max}_interval_set(). The CVSS 3.1 vector is AV:A/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:H, indicating no confidentiality impact, low integrity impact, and high availability impact.
Likely exposure
Systems running affected Linux kernel builds with Bluetooth functionality are the relevant exposure. The provided affected-version data is sparse, listing Linux kernel v4.0-rc1 and default status unaffected, so teams should verify against their distribution and device-vendor advisories.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates exploitation is not broadly remote and would require adjacent access, high attack complexity, high privileges, and user interaction.
Researcher notes
Evidence supports a Bluetooth kernel race condition with denial-of-service potential, but the bundle lacks detailed fixed-version ranges and exploit details. Avoid assuming broader Linux impact beyond vendor-confirmed affected builds.
Mitigation direction
Check Linux distribution and device-vendor advisories for applicable kernel updates.
Prioritize updates for systems where Bluetooth is enabled or operationally required.
Review Debian LTS, OpenAnolis, and Siemens advisories for environment-specific guidance.
Where Bluetooth is unnecessary, evaluate disabling it under approved operational policy.
Validation and detection
Inventory Linux kernel versions on systems with Bluetooth capability.
Confirm whether installed kernels match affected vendor advisory ranges.
Verify Bluetooth is disabled where policy says it should be disabled.
Confirm patched kernel packages are installed after maintenance.
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-362: 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.
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.