CVE-2024-36244 Affecting kernel-debug-modules-core package, versions <0:5.14.0-427.42.1.el9_4


Severity

Recommended
medium

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.05% (18th 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-ROCKY9-KERNELDEBUGMODULESCORE-8362713
  • published9 Nov 2024
  • disclosed21 Jun 2024

Introduced: 21 Jun 2024

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

How to fix?

Upgrade Rocky-Linux:9 kernel-debug-modules-core 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-modules-core package and not the kernel-debug-modules-core 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:

net/sched: taprio: extend minimum interval restriction to entire cycle too

It is possible for syzbot to side-step the restriction imposed by the blamed commit in the Fixes: tag, because the taprio UAPI permits a cycle-time different from (and potentially shorter than) the sum of entry intervals.

We need one more restriction, which is that the cycle time itself must be larger than N * ETH_ZLEN bit times, where N is the number of schedule entries. This restriction needs to apply regardless of whether the cycle time came from the user or was the implicit, auto-calculated value, so we move the existing "cycle == 0" check outside the "if "(!new->cycle_time)" branch. This way covers both conditions and scenarios.

Add a selftest which illustrates the issue triggered by syzbot.

CVSS Scores

version 3.1