dbcve.org
Linux KernelOperating system · Linux

CVE-2024-24860

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-05
Fix available
A fix is available. Upgrade to after 6.7.2 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 bluetooth device driver in {min,max}_key_size_set() function. This can result in a null pointer dereference issue, possibly leading to a kernel panic or denial of service issue.

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 · moderate confidence

A race condition in the Linux kernel bluetooth driver's min/max_key_size_set() functions allows concurrent access without proper synchronization, leading to null pointer dereference. This can trigger kernel panic or denial of service.

MitigationApply the upstream kernel patch which adds proper locking around the key size setter functions to prevent the race condition. Update to a kernel version containing the fix.

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
Linux KernelOperating system
Affected:<= 5.5.19>= 6.0, <= 6.7.2

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. Check installed kernel version
    Run 'uname -r' or 'cat /proc/version' to retrieve the running kernel version
    Affected if The version is <= 5.5.19 OR >= 6.0 through <= 6.7.2 (versions 5.6-5.x are not affected)
  2. Verify bluetooth subsystem is active
    Run 'systemctl status bluetooth' or check 'lsmod | grep bluetooth' to see if the bluetooth kernel module is loaded
    Affected if Bluetooth module is loaded and active - the vulnerability only triggers when the bluetooth driver is in use
  3. Identify bluetooth driver in use
    Check '/sys/class/bluetooth/' directory or run 'hciconfig -a' to see which bluetooth hci device is present
    Affected if An hci device (hci0, hci1, etc.) is present and configured - the race condition occurs in the driver functions handling this device
  4. Check for key size configuration access
    Inspect 'sys/kernel/debug/bluetooth/hci0/security' or similar debugfs interface if available, or monitor for any userspace tools setting min_key_size or max_key_size
    Affected if Applications or tools are setting bluetooth encryption key size parameters - the race condition occurs specifically in min_key_size_set() and max_key_size_set() functions

You are affected if your kernel version falls within 6.0-6.7.2 or is <= 5.5.19 AND you have an active bluetooth interface with key size configuration being accessed, which can trigger the race condition leading to null pointer dereference.

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.2
Interim mitigation

Apply the upstream kernel patch which adds proper locking around the key size setter functions to prevent the race condition. Update to a kernel version containing the fix.

Recommended fix Moderate confidence

Linux Kernel 6.8.0 or later stable release

  1. 1. Identify the current running kernel version using 'uname -r'
  2. 2. Check if the current version is within the affected range (<=5.5.19 or >=6.0, <=6.7.2)
  3. 3. Update the system package repository metadata
  4. 4. Install a kernel version newer than 6.7.2 (such as 6.8.x or later stable release)
  5. 5. Reboot the system to load the new kernel
  6. 6. Verify the new kernel is running using 'uname -r' and confirm the version is > 6.7.2
Caveat Kernel upgrades may require rebuilding third-party kernel modules; ensure compatible drivers are available before rebooting

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24860 — 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-24860 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