CVE-2024-36244 Affecting kernel-debug-core package, versions <0:5.14.0-427.42.1.el9_4
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-ALMALINUX9-KERNELDEBUGCORE-8335707
- published 4 Nov 2024
- disclosed 30 Oct 2024
How to fix?
Upgrade AlmaLinux:9 kernel-debug-core to version 0:5.14.0-427.42.1.el9_4 or higher.
This issue was patched in ALSA-2024:8617.
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 AlmaLinux.
See How to fix? for AlmaLinux: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.
References
- https://errata.almalinux.org/9/ALSA-2024-8617.html
- https://access.redhat.com/security/cve/CVE-2024-36244
- https://access.redhat.com/errata/RHSA-2024:8617
- https://git.kernel.org/stable/c/91f249b01fe490fce11fbb4307952ca8cce78724
- https://git.kernel.org/stable/c/b939d1e04a90248b4cdf417b0969c270ceb992b2
- https://git.kernel.org/stable/c/fb66df20a7201e60f2b13d7f95d031b31a8831d3