NULL Pointer Dereference Affecting kernel-debug-core package, versions <0:4.18.0-553.27.1.el8_10
Threat Intelligence
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 ID SNYK-RHEL8-KERNELDEBUGCORE-7598677
- published 5 Aug 2024
- disclosed 29 Jul 2024
Introduced: 29 Jul 2024
CVE-2024-42079 Open this link in a new tabHow to fix?
Upgrade RHEL:8 kernel-debug-core to version 0:4.18.0-553.27.1.el8_10 or higher.
This issue was patched in RHSA-2024:8856.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-debug-core package and not the kernel-debug-core 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:
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).