Use After Free Affecting perf package, versions <0:4.18.0-553.126.1.el8_10


Severity

Recommended
0.0
high
0
10

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.12% (3rd 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-PERF-17115917
  • published1 Jun 2026
  • disclosed23 Apr 2026

Introduced: 23 Apr 2026

CVE-2026-31532  (opens in a new tab)
CWE-416  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:8 perf to version 0:4.18.0-553.126.1.el8_10 or higher.
This issue was patched in RLSA-2026:21706.

NVD Description

Note: Versions mentioned in the description apply only to the upstream perf package and not the perf 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:

can: raw: fix ro->uniq use-after-free in raw_rcv()

raw_release() unregisters raw CAN receive filters via can_rx_unregister(), but receiver deletion is deferred with call_rcu(). This leaves a window where raw_rcv() may still be running in an RCU read-side critical section after raw_release() frees ro->uniq, leading to a use-after-free of the percpu uniq storage.

Move free_percpu(ro->uniq) out of raw_release() and into a raw-specific socket destructor. can_rx_unregister() takes an extra reference to the socket and only drops it from the RCU callback, so freeing uniq from sk_destruct ensures the percpu area is not released until the relevant callbacks have drained.

[mkl: applied manually]

CVSS Base Scores

version 3.1