CVE-2024-56654 Affecting kernel-livepatch-6_4_0-150600_10_26-rt package, versions <1-150600.1.3.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

Exploit Maturity
Not Defined
EPSS
0.04% (6th 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-SLES156-KERNELLIVEPATCH6401506001026RT-8728883
  • published15 Feb 2025
  • disclosed14 Feb 2025

Introduced: 14 Feb 2025

NewCVE-2024-56654  (opens in a new tab)

How to fix?

Upgrade SLES:15.6 kernel-livepatch-6_4_0-150600_10_26-rt to version 1-150600.1.3.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-6_4_0-150600_10_26-rt package and not the kernel-livepatch-6_4_0-150600_10_26-rt package as distributed by SLES. See How to fix? for SLES:15.6 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: hci_event: Fix using rcu_read_(un)lock while iterating

The usage of rcu_read_(un)lock while inside list_for_each_entry_rcu is not safe since for the most part entries fetched this way shall be treated as rcu_dereference:

Note that the value returned by rcu_dereference() is valid
only within the enclosing RCU read-side critical section [1]_.
For example, the following is **not** legal::

rcu_read_lock();
p = rcu_dereference(head.next);
rcu_read_unlock();
x = p-&amp;gt;address;	/* BUG!!! */
rcu_read_lock();
y = p-&amp;gt;data;	/* BUG!!! */
rcu_read_unlock();

CVSS Scores

version 3.1