CVE-2024-36244
Linux Net Scheduler Taprio Cycle Time Validation Bypass
Description
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.
INFO
Published Date :
June 21, 2024, 11:15 a.m.
Last Modified :
Dec. 2, 2024, 8:15 a.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
Exploitability Score :
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-36244.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-36244 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-36244 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Dec. 02, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/34d83c3e6e97867ae061d14eb52123404aab1cbc -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/91f249b01fe490fce11fbb4307952ca8cce78724 Added Reference https://git.kernel.org/stable/c/b939d1e04a90248b4cdf417b0969c270ceb992b2 Added Reference https://git.kernel.org/stable/c/fb66df20a7201e60f2b13d7f95d031b31a8831d3 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 21, 2024
Action Type Old Value New Value Added Description 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. Added Reference kernel.org https://git.kernel.org/stable/c/b939d1e04a90248b4cdf417b0969c270ceb992b2 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/91f249b01fe490fce11fbb4307952ca8cce78724 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/fb66df20a7201e60f2b13d7f95d031b31a8831d3 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-36244 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-36244
weaknesses.