CVE-2024-41062 Affecting python3-perf package, versions <0:5.14.0-570.12.1.0.1.el9_6


Severity

Recommended
medium

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.13% (35th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ORACLE9-PYTHON3PERF-10239397
  • published24 May 2025
  • disclosed29 Jul 2024

Introduced: 29 Jul 2024

CVE-2024-41062  (opens in a new tab)

How to fix?

Upgrade Oracle:9 python3-perf to version 0:5.14.0-570.12.1.0.1.el9_6 or higher.
This issue was patched in ELSA-2025-6966.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3-perf package and not the python3-perf package as distributed by Oracle. See How to fix? for Oracle:9 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1