Loading vulnerability…
CVE-2024-57988 is a NULL-pointer dereference vulnerability in the Linux kernel Bluetooth BCM (btbcm) driver. The btbcm_get_board_name() function uses the result of devm_kstrdup() without validating whether the allocation failed and returned NULL. An allocation failure can therefore cause a kernel NULL-pointer dereference. The issue was introduced in Linux kernel 6.9 and affects drivers/bluetooth/btbcm.c.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
NULL-pointer dereference in Linux kernel BCM Bluetooth board-name handling.
Linux kernel Bluetooth Broadcom NULL-pointer dereference.
A Linux kernel Bluetooth btbcm driver NULL-pointer dereference caused by failing to validate a potentially NULL value returned by devm_kstrdup() in btbcm_get_board_name().
A moderate-severity Linux kernel Bluetooth (btbcm) NULL-pointer dereference in btbcm_get_board_name(). A local low-privileged attacker could cause an availability impact (kernel crash/denial of service).
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.