dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-24857

MEDIUM · 6.8 CVSS v3.1 Published 2024-02-05
Fix available
A fix is available. Upgrade to 6.7.12 or later.
See remediation →
73/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 device driver in conn_info_{min,max}_age_set() function. This can result in integrity overflow issue, possibly leading to bluetooth connection abnormality or 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 · moderate confidence

A race condition exists in the Linux kernel's Bluetooth driver in the conn_info_{min,max}_age_set() functions. The vulnerability allows concurrent access without proper synchronization, leading to an integrity overflow where data structures can be corrupted during read-modify-write operations. This can cause malformed Bluetooth connection parameters or trigger a denial of service.

MitigationApply the upstream Linux kernel patch which adds proper locking/synchronization to the conn_info_{min,max}_age_set() functions to prevent concurrent access race conditions. For production systems, backport the relevant kernel security update once available.

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
High
Availability
High

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/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 your Linux kernel version
    Run `uname -r` to get the running kernel version
    Affected if The version matches <= 3.19.8; >= 6.0 through 6.6.25; >= 6.7 through 6.7.12; or exactly 6.8
  2. Verify the Bluetooth kernel module is loaded
    Run `lsmod | grep -i bluetooth` or check `modinfo bluetooth` to confirm the btusb or other Bluetooth module is active
    Affected if A Bluetooth module (such as btusb, bluetooth, or hci_usb) is loaded and in use
  3. Check for exposed conn_info age parameters
    Inspect sysfs for Bluetooth connection info age parameters: `ls -la /sys/module/btusb/parameters/conn_info_*` or `ls -la /sys/class/bluetooth/hci*/conn_info_*`
    Affected if The conn_info_min_age and conn_info_max_age sysfs entries exist and are writable (indicating the vulnerable functions are accessible)
  4. Inspect the current conn_info age values
    Read the parameter values if they exist: `cat /sys/module/btusb/parameters/conn_info_min_age` and `cat /sys/module/btusb/parameters/conn_info_max_age`
    Affected if These values can be read, confirming the vulnerable code path is reachable (no explicit values indicate vulnerability, but existence confirms the attack surface)
  5. Verify concurrent access is possible
    Check if multiple Bluetooth adapters or concurrent HCI operations are possible by examining `/sys/class/bluetooth/` for multiple hci devices
    Affected if Multiple HCI devices exist or concurrent Bluetooth operations can be triggered, allowing the race condition to be exercised

You are affected if your kernel version falls within the vulnerable ranges AND the Bluetooth subsystem with conn_info age parameters is active and accessible in your environment.

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 6.7.12 or later
Fixed in 6.7.12
Interim mitigation

Apply the upstream Linux kernel patch which adds proper locking/synchronization to the conn_info_{min,max}_age_set() functions to prevent concurrent access race conditions. For production systems, backport the relevant kernel security update once available.

Recommended fix Moderate confidence

Linux Kernel 6.6.26+, 6.7.12+, or 6.8.1+ (depending on current version)

  1. Identify the current running kernel version using `uname -r`
  2. For Debian 10.0 systems, apply security updates via `apt update && apt upgrade` to get the patched kernel
  3. For Linux Kernel 6.0-6.6.x: upgrade to kernel version 6.6.26 or later
  4. For Linux Kernel 6.7.x: upgrade to kernel version 6.7.12 or later
  5. For Linux Kernel 6.8.x: upgrade to kernel version 6.8.1 or later
  6. Reboot the system to load the new kernel
  7. Verify the new kernel version is running with `uname -r`
Caveat Kernel upgrade requires system reboot and may require rebuilding third-party kernel modules

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
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,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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