mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-05-30 02:00:53 +00:00
28 lines
1.6 KiB
JSON
28 lines
1.6 KiB
JSON
![]() |
{
|
||
|
"id": "CVE-2024-36244",
|
||
|
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||
|
"published": "2024-06-21T11:15:09.957",
|
||
|
"lastModified": "2024-06-21T11:22:01.687",
|
||
|
"vulnStatus": "Awaiting Analysis",
|
||
|
"descriptions": [
|
||
|
{
|
||
|
"lang": "en",
|
||
|
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: taprio: extend minimum interval restriction to entire cycle too\n\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.\n\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.\n\nAdd a selftest which illustrates the issue triggered by syzbot."
|
||
|
}
|
||
|
],
|
||
|
"metrics": {},
|
||
|
"references": [
|
||
|
{
|
||
|
"url": "https://git.kernel.org/stable/c/91f249b01fe490fce11fbb4307952ca8cce78724",
|
||
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||
|
},
|
||
|
{
|
||
|
"url": "https://git.kernel.org/stable/c/b939d1e04a90248b4cdf417b0969c270ceb992b2",
|
||
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||
|
},
|
||
|
{
|
||
|
"url": "https://git.kernel.org/stable/c/fb66df20a7201e60f2b13d7f95d031b31a8831d3",
|
||
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||
|
}
|
||
|
]
|
||
|
}
|