Loading story…
Red Hat released kernel and real-time kernel updates for CVE-2023-40283, a CVSS 7.8 use-after-free flaw in the Linux Bluetooth L2CAP socket-release routine, l2cap_sock_release. Improper handling of child sockets can allow a local low-privileged user to trigger the vulnerability, potentially compromising confidentiality, integrity, and availability. The upstream fix is commit 1728137b33c00d5a2b5110ed7aafb42e7c32e4a1, included in Linux kernel 6.4.10; Red Hat reported no qualifying mitigation beyond updating affected systems.
Affected Red Hat Enterprise Linux 8.4 support channels received kernel 4.18.0-305.130.1.el8_4 under RHSA-2024:2582, while relevant RHEL 8.4 real-time deployments received kernel-rt 4.18.0-305.130.1.rt7.206.el8_4 through RHSA-2024:2585. RHSA-2024:10772 also includes the remediation in kernel 5.14.0-284.95.1.el9_2 for RHEL 9.2 update channels. Administrators should install the applicable updated kernel packages and reboot to activate the fixes.
See real exploitation activity before you spend the cycle.
5 events from the most recent confirmed update back to the earliest known activity.
Red Hat released RHSA-2024:0881 for RHEL 8 kernel-rt and RHSA-2024:0897 for the RHEL 8 kernel, remediating CVE-2023-40283.
Rohit Keshri disclosed CVE-2023-40283, a use-after-free in the Linux kernel's Bluetooth L2CAP l2cap_sock_release routine caused by mishandling socket children.
Red Hat issued RHSA-2024:2582 and RHSA-2024:2585 for supported RHEL 8.4 channels, fixing CVE-2023-40283 in kernel version 4.18.0-305.130.1.el8_4 and kernel-rt version 4.18.0-305.130.1.rt7.206.el8_4.
Red Hat issued RHSA-2024:1268 and RHSA-2024:1269 to fix CVE-2023-40283 for RHEL 8.2 Advanced Update Support, Telecommunications Update Service, and SAP update-service kernel channels.
The upstream Linux kernel project fixed the Bluetooth L2CAP use-after-free in commit 1728137b33c00d5a2b5110ed7aafb42e7c32e4a1; the fix is included in Linux kernel 6.4.10.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
5 references tracked. Mallory keeps watching after this page renders.
access.redhat.com
Open sourceaccess.redhat.com
Open sourceaccess.redhat.com
Open sourceredhat.com
Open sourcebugzilla.redhat.com
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.
Red Hat released updated Linux kernel packages for Red Hat Enterprise Linux 8.6 extended-support channels and RHEL 8.8 supported update channels, remediating **CVE-2022-3640**, a Bluetooth L2CAP use-after-free flaw in `l2cap_conn_del`. The vulnerability can allow compromise of confidentiality, integrity, and availability from an adjacent network under specific conditions; Red Hat rates it Moderate (CVSS 7.1), while NVD rates it 8.8. RHEL 7, 8, 9, and Red Hat Virtualization 4 product streams received fixes, while RHEL 6 is not affected. RHSA-2024:1877 covers RHEL 8.6 EUS and associated ELL, AUS, TUS, SAP, virtualization-host, and CodeReady Linux Builder channels, while RHSA-2024:2621 supplies kernel `4.18.0-477.55.1.el8_8` for RHEL 8.8 on x86_64, s390x, ppc64le, and aarch64. The advisories also address other kernel defects, including AMD CPU, ext4, x86 emulation, veth/GRO, GSM multiplexing, virtual-machine-monitor, and information-disclosure issues. Red Hat reports no generally deployable mitigation for the affected Bluetooth flaw; organizations should install the applicable errata and reboot systems to load the updated kernel.
Aug 26, 2026
Red Hat released kernel and real-time kernel updates for supported **Red Hat Enterprise Linux (RHEL) 8 and 9** systems to remediate **CVE-2022-3619**, a Bluetooth L2CAP memory-leak flaw in `l2cap_recv_acldata` within `net/bluetooth/l2cap_core.c`. An adjacent attacker could send malicious Bluetooth packets without privileges or user interaction and potentially exhaust memory or crash an affected host. Red Hat rated the issue moderate severity with a CVSS v3.1 score of 4.3 and classified it as CWE-401. The fixes were included in RHEL 8 kernel version `4.18.0-477.10.1.el8_8` under RHSA-2023:2951 and the real-time kernel version `4.18.0-477.10.1.rt7.274.el8_8` under RHSA-2023:2736, alongside numerous other kernel security corrections affecting virtualization, networking, wireless, USB, and memory safety. Organizations should install the applicable kernel packages and reboot systems; where patching cannot occur promptly, disabling Bluetooth through module blocklisting, hardware controls, or BIOS settings reduces exposure.
Aug 26, 2026
Red Hat released **Important** kernel security updates for **RHEL 8.4** and **RHEL 8.2** support channels, including Advanced Mission Critical Update Support, Extended Update Support Long-Life Add-On, and Advanced Update Support. The advisories **RHSA-2026:3360** and **RHSA-2026:3388** update Linux kernel packages to remediate multiple vulnerabilities affecting supported x86_64 systems, with impact ranging from memory corruption and out-of-bounds read/write to denial of service, information disclosure, integer overflow, incomplete input validation, and potential privilege escalation. Among the patched issues is **`CVE-2023-53827`**, a Bluetooth **L2CAP** use-after-free flaw in `l2cap_disconnect_req` and `l2cap_disconnect_rsp` that could occur when a channel was referenced as it was being destroyed. Red Hat said the bug was fixed by using `l2cap_chan_hold_unless_zero`, and confirmed the remediation is included in both advisories. Affected organizations are advised to install the updated kernel packages and **reboot** systems for the fixes to take effect.
Aug 26, 2026