Loading story…
CVE-2024-57988 is a moderate-severity flaw in the Linux kernel Bluetooth btbcm driver. Introduced in Linux 6.9, btbcm_get_board_name() did not validate a NULL value returned by devm_kstrdup() after an allocation failure, allowing a local low-privileged attacker to trigger a kernel NULL-pointer dereference and cause denial of service. Red Hat assigned a CVSS v3.1 score of 5.5, with high availability impact.
The upstream issue is fixed in Linux 6.12.13, 6.13.2, and 6.14-rc1; maintainers recommend updating to a current stable kernel rather than cherry-picking the patch. Red Hat shipped fixes for RHEL 10 in RHSA-2025:20095 and RHEL 9 in RHSA-2025:20518. RHEL 9 kernel-rt remained affected at publication, while listed RHEL 6 and RHEL 8 kernel variants were not affected and RHEL 7 variants were outside support scope.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Red Hat released fixes for RHEL 10 via RHSA-2025:20095 and for RHEL 9 via RHSA-2025:20518. RHEL 9 kernel-rt remained listed as affected without a listed erratum.
Red Hat published its record for CVE-2024-57988, describing a local denial-of-service risk from a NULL-pointer dereference in the Linux Bluetooth btbcm component. Upstream remediation adds a NULL check; Linux 6.12.13, 6.13.2, and 6.14-rc1 include fixes.
The defect was introduced in Linux kernel 6.9, where btbcm_get_board_name() used the result of devm_kstrdup() without validating whether allocation failure returned NULL.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
bugzilla.redhat.com
Open sourceredhat.com
Open sourcelore.kernel.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
**CVE-2023-51779** is a use-after-free flaw in the Linux kernel Bluetooth subsystem caused by a race between `bt_sock_recvmsg()` and `bt_sock_ioctl()` over a socket buffer. A local low-privileged user could trigger a denial of service and may potentially execute code; Red Hat rates the issue Moderate, with CVSS 7.0, while noting exploitation is difficult and local privilege escalation has not been confirmed. The upstream fix is available in commit `2e07e8348ea454615e268222ae3fc240421be768`, and Fedora addressed the issue in its 6.6.9 stable kernel updates. Red Hat released fixes for affected RHEL 8 and 9 streams, including RHSA-2024:3859 for supported RHEL 8.6 extended-support variants, which provides kernel `4.18.0-372.107.1.el8_6`; affected systems require a reboot after installation. RHEL 6 is outside support scope and should be considered affected.
Aug 26, 2026
A use-after-free flaw in the Linux kernel Bluetooth HCI SCO subsystem, tracked as **CVE-2021-3640**, can allow a local privileged attacker to crash a host or escalate privileges. The vulnerability stems from a race involving `sco_sock_sendmsg()` and `sco_conn_del()`; it can be triggered through `UFFDIO_REGISTER` or a comparable mechanism by an attacker holding `CAP_NET_ADMIN` in the initial user namespace. Red Hat assigned the issue a **Moderate** severity rating with a CVSS v3.1 score of **6.7** and classified it as CWE-825, expired pointer dereference. Fixed `kernel` and `kernel-rt` packages were released for Red Hat Enterprise Linux 8 and 9, with further fixes for RHEL 8.6 EUS and Red Hat Virtualization; RHEL 6 is unaffected, while out-of-support RHEL 7 kernel variants should be treated as potentially affected.
Aug 26, 2026
A use-after-free flaw in the Linux kernel's Bluetooth SCO implementation, tracked as **CVE-2026-31408**, was fixed after maintainers found that `sco_recv_frame()` could access a socket after it had been freed during a concurrent `close()`. The bug stems from reading `conn->sk` while holding `sco_conn_lock()` and then releasing the lock before safely retaining a socket reference, creating a race that can lead to memory corruption or a denial of service. Upstream records say the vulnerable code path existed since Linux `2.6.12`, and the fix adds `sco_sock_hold()` before unlocking along with `sock_put()` on all exit paths. The Linux kernel CVE team published fixes across multiple stable branches, including `6.6.131`, `6.12.80`, `6.18.21`, `6.19.11`, and `7.0-rc6`, and advised users to move to the latest stable kernel rather than cherry-picking patches. Red Hat rated the issue **Moderate** for its products, assigned a CVSS v3 score of `7.0`, and said updated kernel packages were released for multiple Red Hat Enterprise Linux lines, including **RHEL 8, 9, and 10** and related support variants; upstream CVE scoring lists the flaw at `8.8` under adjacent-network Bluetooth attack conditions.
Aug 25, 2026