Linux Kernel up to 6.1.100/6.6.41/6.9.10 l2cap hci_rx_work null pointer dereference

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.1.100/6.6.41/6.9.10. It has been declared as critical. Impacted is the function hci_rx_work of the component l2cap. Such manipulation leads to null pointer dereference. This vulnerability is traded as CVE-2024-41062. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.1.100/6.6.41/6.9.10. Affected by this issue is the function hci_rx_work of the component l2cap. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: bluetooth/l2cap: sync sock recv cb and release The problem occurs between the system call to close the sock and hci_rx_work, where the former releases the sock and the latter accesses it without lock protection. CPU0 CPU1 ---- ---- sock_close hci_rx_work l2cap_sock_release hci_acldata_packet l2cap_sock_kill l2cap_recv_frame sk_free l2cap_conless_channel l2cap_sock_recv_cb If hci_rx_work processes the data that needs to be received before the sock is closed, then everything is normal; Otherwise, the work thread may access the released sock when receiving data. Add a chan mutex in the rx callback of the sock to achieve synchronization between the sock release and recv cb. Sock is dead, so set chan data to NULL, avoid others use invalid sock pointer.

The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2024-41062 since 07/12/2024. The exploitation is known to be difficult. There are known technical details, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 207884 (openSUSE 15 Security Update : kernel (SUSE-SU-2024:3483-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.1.101, 6.6.42 or 6.9.11 eliminates this vulnerability. Applying the patch 605572e64cd9/b803f30ea23e/3b732449b781/89e856e124f9 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (207884) and CERT Bund (WID-SEC-2024-1722). Once again VulDB remains the best source for vulnerability data.

Affected

• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• IBM InfoSphere Guardium
• Oracle Linux
• NetApp FAS
• NetApp ActiveIQ Unified Manager
• Siemens SIMATIC S7
• Oracle VM
• IBM Security Guardium
• RESF Rocky Linux
• Broadcom Brocade SANnav
• Dell PowerScale
• Open Source Linux Kernel
• IBM QRadar SIEM
• Dell integrated Dell Remote Access Controller
• Dell Avamar
• IBM Storage Scale
• IBM Spectrum Protect Plus
• Juniper Junos Space
• IBM Storage Scale System
• SolarWinds Security Event Manager
• Dell PowerProtect Data Domain
• Dell PowerProtect Data Domain Management Center
• Dell PowerProtect Data Domain OS

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.0
• 6.1.100
• 6.6.0
• 6.6.1
• 6.6.2
• 6.6.3
• 6.6.4
• 6.6.5
• 6.6.6
• 6.6.7
• 6.6.8
• 6.6.9
• 6.6.10
• 6.6.11
• 6.6.12
• 6.6.13
• 6.6.14
• 6.6.15
• 6.6.16
• 6.6.17
• 6.6.18
• 6.6.19
• 6.6.20
• 6.6.21
• 6.6.22
• 6.6.23
• 6.6.24
• 6.6.25
• 6.6.26
• 6.6.27
• 6.6.28
• 6.6.29
• 6.6.30
• 6.6.31
• 6.6.32
• 6.6.33
• 6.6.34
• 6.6.35
• 6.6.36
• 6.6.37
• 6.6.38
• 6.6.39
• 6.6.40
• 6.6.41
• 6.9.0
• 6.9.1
• 6.9.2
• 6.9.3
• 6.9.4
• 6.9.5
• 6.9.6
• 6.9.7
• 6.9.8
• 6.9.9
• 6.9.10

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion