dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-24858

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-05
Fix available
A fix is available. Upgrade to after 6.7.12 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A race condition in the Linux kernel's Bluetooth subsystem (net/bluetooth) in the {conn,adv}_{min,max}_interval_set() functions that handle connection and advertisement interval configuration. This timing vulnerability can corrupt I2cap connection state or broadcast parameters, potentially causing denial of service via malformed Bluetooth operations.

MitigationApply the upstream Linux kernel security patch; update to a kernel version containing the fix. If immediate patching is not feasible, consider network segmentation to limit Bluetooth exposure and monitor for anomalous Bluetooth activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 10.0
Linux KernelOperating system
Affected:<= 3.19.8>= 6.0, <= 6.6.25>= 6.7, <= 6.7.12= 6.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the running Linux kernel version
    Run `uname -r` or check `/proc/version` to get the installed kernel version
    Affected if The kernel version falls within any of these ranges: <= 3.19.8, 6.0.x through 6.6.25, 6.7.x through 6.7.12, or exactly 6.8
  2. Confirm the Bluetooth subsystem is active
    Run `systemctl status bluetooth` or check if `bluetooth` module is loaded via `lsmod | grep bluetooth`
    Affected if The Bluetooth kernel module is loaded and the bluetooth service is running, making the vulnerable code path accessible
  3. Check for active Bluetooth connections or adapters
    Run `hcitool con` to list active connections, or `hciconfig -a` to show all Bluetooth adapters and their current state
    Affected if There are active Bluetooth connections or configured adapters; the race condition triggers when conn/adv interval configuration functions are invoked
  4. Identify Bluetooth-specific kernel configuration
    Check kernel config for `CONFIG_BT` and related options in `/boot/config-$(uname -r)` or via `zcat /proc/config.gz` if available
    Affected if Bluetooth support is compiled into the kernel (CONFIG_BT is set), enabling the vulnerable net/bluetooth code path

You are affected if your kernel version matches the affected ranges AND the Bluetooth subsystem is loaded and actively managing connections or advertisements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 6.7.12
Interim mitigation

Apply the upstream Linux kernel security patch; update to a kernel version containing the fix. If immediate patching is not feasible, consider network segmentation to limit Bluetooth exposure and monitor for anomalous Bluetooth activity.

Recommended fix Moderate confidence

Linux Kernel 6.6.26+ / 6.7.13+ / 6.8.1+ (or Debian 10 kernel updates)

  1. Identify the current running kernel version using 'uname -r'
  2. For Debian 10 (Buster), update the system using 'apt update && apt upgrade' to receive kernel security updates
  3. If using a upstream kernel, upgrade to kernel version 6.6.26 or later, or 6.7.13 or later, or 6.8.1 or later
  4. Reboot the system to load the updated kernel
  5. Verify the fix is applied by checking 'uname -r' shows a patched version and reviewing /proc/version or dmesg for confirmation
Caveat Kernel upgrades may require rebuilding out-of-tree kernel modules; ensure compatibility with existing system configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24858 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24858 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data