dbcve.org
ZephyrOperating system · Zephyrproject

CVE-2024-6442

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-04
Fix available
A fix is available. Upgrade to after 3.6.0 or later.
See remediation →
70/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
In ascs_cp_rsp_add in /subsys/bluetooth/audio/ascs.c, an unchecked tailroom could lead to a global buffer overflow.

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 buffer overflow vulnerability exists in the ascs_cp_rsp_add function within Zephyr RTOS Bluetooth Audio ASCS (Audio Stream Control Service). The function fails to validate available tailroom before writing data, allowing a write beyond buffer boundaries into adjacent global memory. This could enable memory corruption or potentially remote code execution depending on overflow reach.

MitigationAdd bounds checking to verify sufficient tailroom exists before writing data in ascs_cp_rsp_add. The fix requires validating buffer capacity against data length prior to any write operation.

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
ZephyrOperating system
Affected:<= 3.6.0

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/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 if the system uses Zephyr RTOS
    Check the build system or firmware for Zephyr RTOS markers, such as checking for zephyr_version.h, checking the kernel configuration, or reviewing build artifacts for Zephyr-specific modules
    Affected if The system does not use Zephyr RTOS - not affected; if Zephyr is confirmed, proceed to next step
  2. Determine the Zephyr version
    Locate the Zephyr version file (such as VERSION or zephyr_version.h in the Zephyr source tree), check the build configuration for the version, or inspect the SDK version used in the build
    Affected if Version is 3.6.0 or lower - potentially affected; versions above 3.6.0 are not affected by this CVE
  3. Verify Bluetooth Audio ASCS is enabled
    Check the Kconfig settings or defconfig file for CONFIG_BT_ASCS=y or similar Bluetooth Audio configurations. Also check if the bluetooth audio subsystem is compiled into the firmware image
    Affected if ASCS module is not enabled - not affected; if enabled, the vulnerable code path exists in the build
  4. Confirm the ascs_cp_rsp_add function exists
    Inspect the compiled binary or source code for the ascs_cp_rsp_add function. In the source tree, this is located in subsys/bluetooth/audio/ascs.c. Check if this function is linked into the final firmware image
    Affected if The function exists in the firmware - vulnerable code path is present and the buffer overflow condition can be triggered

The environment is affected only if it uses Zephyr RTOS version 3.6.0 or lower with the Bluetooth Audio ASCS module enabled, resulting in the ascs_cp_rsp_add function being present in the firmware.

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 3.6.0
Interim mitigation

Add bounds checking to verify sufficient tailroom exists before writing data in ascs_cp_rsp_add. The fix requires validating buffer capacity against data length prior to any write operation.

Recommended fix Moderate confidence

Zephyr v3.7.0 or later (check GitHub security advisories for exact tag)

  1. 1. Identify the current Zephyr version in use by checking the `VERSION` file or manifest file (usually `west.yml` or `requirements.txt`)
  2. 2. Check Zephyr's official release notes and security advisories at https://github.com/zephyrproject-rtos/zephyr/security/advisories to confirm the exact fixed version for CVE-2024-6442
  3. 3. If using west for dependency management, update the manifest to point to the fixed version tag (e.g., zephyr-v3.7.0 or later)
  4. 4. Run `west update` to fetch the updated Zephyr repository
  5. 5. Rebuild the application with the updated Zephyr codebase: clean the build directory and recompile
  6. 6. Verify the fix is applied by checking that the `ascs.c` file contains the tailroom check before buffer operations
Caveat Review release notes for v3.7.0 for any Bluetooth Audio API changes that may require code updates

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

Fix this in Zephyr Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,780
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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