Поиск уязвимостей
Количество 20
Количество 20
CVE-2024-36244
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.
CVE-2024-36244
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.
CVE-2024-36244
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.
CVE-2024-36244
net/sched: taprio: extend minimum interval restriction to entire cycle too
CVE-2024-36244
In the Linux kernel, the following vulnerability has been resolved: n ...
GHSA-35qp-2m3w-q656
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.
BDU:2025-08075
Уязвимость компонентов sch_taprio.c, taprio.json ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260112-7321
Уязвимость kernel-lt
RLSA-2024:8617
Moderate: kernel security update
ELSA-2024-8617
ELSA-2024-8617: kernel security update (MODERATE)
ALT-PU-2020-3058
ALT-PU-2020-3058: package `kernel-image-un-def` update to version 5.9.0-alt1
ALT-PU-2024-16040
ALT-PU-2024-16040: package `kernel-image-un-def` update to version 6.1.119-alt1
SUSE-SU-2024:3983-1
Security update for the Linux Kernel
SUSE-SU-2024:3985-1
Security update for the Linux Kernel
SUSE-SU-2024:3986-1
Security update for the Linux Kernel
SUSE-SU-2024:3984-1
Security update for the Linux Kernel
SUSE-SU-2024:4364-1
Security update for the Linux Kernel
SUSE-SU-2024:4387-1
Security update for the Linux Kernel
SUSE-SU-2024:4318-1
Security update for the Linux Kernel
ALT-PU-2024-14046
ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-36244 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. | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-36244 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. | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-36244 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. | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-36244 net/sched: taprio: extend minimum interval restriction to entire cycle too | 0% Низкий | около 1 года назад | ||
CVE-2024-36244 In the Linux kernel, the following vulnerability has been resolved: n ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-35qp-2m3w-q656 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. | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2025-08075 Уязвимость компонентов sch_taprio.c, taprio.json ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 3.8 | 0% Низкий | больше 2 лет назад | |
ROS-20260112-7321 Уязвимость kernel-lt | CVSS3: 3.8 | 0% Низкий | 10 месяцев назад | |
RLSA-2024:8617 Moderate: kernel security update | около 2 лет назад | |||
ELSA-2024-8617 ELSA-2024-8617: kernel security update (MODERATE) | около 2 лет назад | |||
ALT-PU-2020-3058 ALT-PU-2020-3058: package `kernel-image-un-def` update to version 5.9.0-alt1 | CVSS3: 7.8 | около 6 лет назад | ||
ALT-PU-2024-16040 ALT-PU-2024-16040: package `kernel-image-un-def` update to version 6.1.119-alt1 | CVSS3: 7.8 | почти 2 года назад | ||
SUSE-SU-2024:3983-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:3985-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:3986-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:3984-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:4364-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:4387-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:4318-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2024-14046 ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1 | CVSS3: 9.8 | почти 2 года назад |
Уязвимостей на страницу