Skip to content
CVE PROGRAM SOURCE RECORD8.8 High

CVE-2024-41062

bluetooth/l2cap: sync sock recv cb and release

Description

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.

Affected products

Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.

Linux Linux

Default version status: unaffected

  • 5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa to < 59a3ccd749b2550392ee531b4d727022eae4c89faffected
  • 5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa to < 9c0b7d61cf3c00f87f2529b5b8b785f0f65089aaaffected
  • 5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa to < 605572e64cd9cebb05ed609d96cff05b50d18cdfaffected
  • 5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa to < b803f30ea23e0968b6c8285c42adf0d862ab2bf6affected
  • 5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa to < 3b732449b78183d17178db40be3a4401cf3cd629affected
  • 5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa to < 89e856e124f9ae548572c56b1b70c2255705f8feaffected

Linux Linux

Default version status: affected

  • 3.4affected
  • 0 to < 3.4unaffected
  • 5.10.271 to ≤ 5.10.*unaffected
  • 5.15.222 to ≤ 5.15.*unaffected
  • 6.1.101 to ≤ 6.1.*unaffected
  • 6.6.42 to ≤ 6.6.*unaffected
  • 6.9.11 to ≤ 6.9.*unaffected
  • 6.10 to ≤ *unaffected

References