IT

Tracker / CVE-2024-36244

CVE-2024-36244

Medium 5.5

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.

Affected products and versions

linux linux_kernel
linux linux_kernel · 5.4.68 → 5.5
linux linux_kernel · 5.8.12 → 5.9
linux linux_kernel · 5.9.1 → 6.1.119
linux linux_kernel · 6.2 → 6.6.33
linux linux_kernel · 6.7 → 6.9.4

Analysis

This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.

References