Improper Input Validation Affecting python3-perf package, versions <0:4.18.0-477.74.1.el8_8


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (12th 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 Learn

Learn about Improper Input Validation vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL8-PYTHON3PERF-8085653
  • published24 Sept 2024
  • disclosed2 Mar 2024

Introduced: 2 Mar 2024

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

How to fix?

Upgrade RHEL:8 python3-perf to version 0:4.18.0-477.74.1.el8_8 or higher.
This issue was patched in RHSA-2024:6993.

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 RHEL. See How to fix? for RHEL: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