CVE-2024-57987 is a NULL-pointer dereference in the Linux kernel Bluetooth Realtek (btrtl) driver. In btrtl_setup_realtek(), processing a USB Bluetooth dongle whose chip identifier is not represented in the driver’s supported identifier table can yield a NULL lookup result that is subsequently dereferenced. The upstream correction validates the lookup result before use, preventing the kernel Oops.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel Bluetooth Realtek setup NULL-pointer flaw.
A Linux kernel Bluetooth Realtek (btrtl) driver NULL-pointer dereference in btrtl_setup_realtek(). Connecting a USB Bluetooth dongle whose chipset is absent from ic_id_table can trigger a kernel Oops; the fix adds a NULL check.
A moderate-severity Linux kernel Bluetooth Realtek (btrtl) NULL-pointer dereference vulnerability. A local authenticated attacker can trigger a denial of service through a crash or restart; Red Hat assigns CVSS 5.5.
A Linux kernel Bluetooth Realtek (btrtl) driver NULL-pointer dereference. Connecting a USB Bluetooth dongle whose chip is absent from ic_id_table can trigger a kernel Oops. The issue was introduced in Linux kernel 6.10 and is fixed in 6.12.13, 6.13.2, and 6.14-rc1.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.