Allocation of Resources Without Limits or Throttling Affecting kernel-debug-devel package, versions <0:5.14.0-427.42.1.el9_4


Severity

Recommended
0.0
medium
0
10

Based on Rocky Linux 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 Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-ROCKY9-KERNELDEBUGDEVEL-8362786
  • published9 Nov 2024
  • disclosed5 Jul 2024

Introduced: 5 Jul 2024

CVE-2024-39472  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:9 kernel-debug-devel to version 0:5.14.0-427.42.1.el9_4 or higher.
This issue was patched in RLSA-2024:8617.

NVD Description

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

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

xfs: fix log recovery buffer allocation for the legacy h_size fixup

Commit a70f9fe52daa ("xfs: detect and handle invalid iclog size set by mkfs") added a fixup for incorrect h_size values used for the initial umount record in old xfsprogs versions. Later commit 0c771b99d6c9 ("xfs: clean up calculation of LR header blocks") cleaned up the log reover buffer calculation, but stoped using the fixed up h_size value to size the log recovery buffer, which can lead to an out of bounds access when the incorrect h_size does not come from the old mkfs tool, but a fuzzer.

Fix this by open coding xlog_logrec_hblks and taking the fixed h_size into account for this calculation.

CVSS Scores

version 3.1