CVE-2023-52522 Affecting kernel-rt-debug-debuginfo package, versions <0:4.18.0-553.22.1.rt7.363.el8_10


Severity

Recommended
high

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.04% (13th 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-ROCKY8-KERNELRTDEBUGDEBUGINFO-8134386
  • published1 Oct 2024
  • disclosed2 Mar 2024

Introduced: 2 Mar 2024

CVE-2023-52522  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:8 kernel-rt-debug-debuginfo to version 0:4.18.0-553.22.1.rt7.363.el8_10 or higher.
This issue was patched in RLSA-2024:7001.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-rt-debug-debuginfo package and not the kernel-rt-debug-debuginfo package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:8 relevant fixed versions and status.

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

net: fix possible store tearing in neigh_periodic_work()

While looking at a related syzbot report involving neigh_periodic_work(), I found that I forgot to add an annotation when deleting an RCU protected item from a list.

Readers use rcu_deference(*np), we need to use either rcu_assign_pointer() or WRITE_ONCE() on writer side to prevent store tearing.

I use rcu_assign_pointer() to have lockdep support, this was the choice made in neigh_flush_dev().

CVSS Scores

version 3.1