CVE-2024-27397 Affecting kernel-zfcpdump-core package, versions <0:5.14.0-284.71.1.el9_2


Severity

Recommended
0.0
high
0
10

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 IDSNYK-RHEL9-KERNELZFCPDUMPCORE-7395446
  • published26 Jun 2024
  • disclosed8 May 2024

Introduced: 8 May 2024

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

How to fix?

Upgrade RHEL:9 kernel-zfcpdump-core to version 0:5.14.0-284.71.1.el9_2 or higher.
This issue was patched in RHSA-2024:4108.

NVD Description

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

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

netfilter: nf_tables: use timestamp to check for set element timeout

Add a timestamp field at the beginning of the transaction, store it in the nftables per-netns area.

Update set backend .insert, .deactivate and sync gc path to use the timestamp, this avoids that an element expires while control plane transaction is still unfinished.

.lookup and .update, which are used from packet path, still use the current time to check if the element has expired. And .get path and dump also since this runs lockless under rcu read size lock. Then, there is async gc which also needs to check the current time since it runs asynchronously from a workqueue.

CVSS Scores

version 3.1