Release Date: | 2024-06-21 |
In the Linux kernel, the following vulnerability has been resolved:\nnet/sched: taprio: extend minimum interval restriction to entire cycle too\nIt is possible for syzbot to side-step the restriction imposed by the\nblamed commit in the Fixes: tag, because the taprio UAPI permits a\ncycle-time different from (and potentially shorter than) the sum of\nentry intervals.\nWe need one more restriction, which is that the cycle time itself must\nbe larger than N * ETH_ZLEN bit times, where N is the number of schedule\nentries. This restriction needs to apply regardless of whether the cycle\ntime came from the user or was the implicit, auto-calculated value, so\nwe move the existing 'cycle == 0' check outside the 'if '(!new->cycle_time)'\nbranch. This way covers both conditions and scenarios.\nAdd a selftest which illustrates the issue triggered by syzbot.
See more information about CVE-2024-36244 from MITRE CVE dictionary and NIST NVD
NOTE: The following CVSS v3.1 metrics and score provided are preliminary and subject to review.
Base Score: | 5.5 | CVSS Vector: | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Attack Vector: | Local network | Attack Complexity: | Low |
Privileges Required: | Low | User Interaction: | None |
Scope: | Unchanged | Confidentiality Impact: | None |
Integrity Impact: | None | Availability Impact: | High |
Platform | Errata | Release Date |
Oracle Linux version 9 (kernel) | ELSA-2024-8617 | 2024-10-30 |
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections: