NULL Pointer Dereference Affecting kernel-rt-debug-modules-extra package, versions <0:4.18.0-553.27.1.rt7.368.el8_10


Severity

Recommended
0.0
medium
0
10

Based on AlmaLinux security rating.

Threat Intelligence

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 Learn

Learn about NULL Pointer Dereference vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-ALMALINUX8-KERNELRTDEBUGMODULESEXTRA-8348281
  • published6 Nov 2024
  • disclosed5 Nov 2024

Introduced: 5 Nov 2024

CVE-2024-42079  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:8 kernel-rt-debug-modules-extra to version 0:4.18.0-553.27.1.rt7.368.el8_10 or higher.
This issue was patched in ALSA-2024:8870.

NVD Description

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

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

gfs2: Fix NULL pointer dereference in gfs2_log_flush

In gfs2_jindex_free(), set sdp->sd_jdesc to NULL under the log flush lock to provide exclusion against gfs2_log_flush().

In gfs2_log_flush(), check if sdp->sd_jdesc is non-NULL before dereferencing it. Otherwise, we could run into a NULL pointer dereference when outstanding glock work races with an unmount (glock_work_func -> run_queue -> do_xmote -> inode_go_sync -> gfs2_log_flush).

CVSS Scores

version 3.1