Количество 64
Количество 64
CVE-2025-38001
In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: "We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent insertions in the HFSC eltree and cause a UAF." To fix both the U...
CVE-2025-38001
In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: "We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent insertions in the HFSC eltree and cause a UAF." To fix both the U...
CVE-2025-38001
In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: "We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent ins
CVE-2025-38001
net_sched: hfsc: Address reentrant enqueue adding class to eltree twice
CVE-2025-38001
In the Linux kernel, the following vulnerability has been resolved: n ...
GHSA-rh23-w5x7-xjm4
In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: "We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent ...
BDU:2025-12349
Уязвимость компонента net/sched/sch_hfsc.c ядра операционной системы Linux, позволяющая нарушителю получить доступ к конфиденциальным данным, нарушить их целостность, а также вызвать отказ в обслуживании
SUSE-SU-2025:03222-1
Security update for the Linux Kernel (Live Patch 1 for SLE 15 SP7)
SUSE-SU-2025:03213-1
Security update for the Linux Kernel (Live Patch 12 for SLE 15 SP6)
SUSE-SU-2025:03182-1
Security update for the Linux Kernel (Live Patch 41 for SLE 15 SP4)
SUSE-SU-2025:03154-1
Security update for the Linux Kernel (Live Patch 58 for SLE 15 SP3)
SUSE-SU-2025:03104-1
Security update for the Linux Kernel RT (Live Patch 1 for SLE 15 SP7)
SUSE-SU-2025:03195-1
Security update for the Linux Kernel (Live Patch 27 for SLE 15 SP5)
SUSE-SU-2025:03184-1
Security update for the Linux Kernel (Live Patch 40 for SLE 15 SP4)
SUSE-SU-2025:03179-1
Security update for the Linux Kernel (Live Patch 39 for SLE 15 SP4)
SUSE-SU-2025:03153-1
Security update for the Linux Kernel (Live Patch 56 for SLE 15 SP3)
SUSE-SU-2025:03148-1
Security update for the Linux Kernel (Live Patch 57 for SLE 15 SP3)
SUSE-SU-2025:03106-1
Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP7)
SUSE-SU-2025:03212-1
Security update for the Linux Kernel (Live Patch 10 for SLE 15 SP6)
SUSE-SU-2025:03207-1
Security update for the Linux Kernel (Live Patch 25 for SLE 15 SP5)
Уязвимостей на страницу
Уязвимость  | CVSS  | EPSS  | Опубликовано  | |
|---|---|---|---|---|
CVE-2025-38001 In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: "We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent insertions in the HFSC eltree and cause a UAF." To fix both the U...  | 0% Низкий | 5 месяцев назад | ||
CVE-2025-38001 In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: "We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent insertions in the HFSC eltree and cause a UAF." To fix both the U...  | CVSS3: 7  | 0% Низкий | 5 месяцев назад | |
CVE-2025-38001 In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: "We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent ins  | 0% Низкий | 5 месяцев назад | ||
CVE-2025-38001 net_sched: hfsc: Address reentrant enqueue adding class to eltree twice  | CVSS3: 7.8  | 0% Низкий | 3 месяца назад | |
CVE-2025-38001 In the Linux kernel, the following vulnerability has been resolved: n ...  | 0% Низкий | 5 месяцев назад | ||
GHSA-rh23-w5x7-xjm4 In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice Savino says: "We are writing to report that this recent patch (141d34391abbb315d68556b7c67ad97885407547) [1] can be bypassed, and a UAF can still occur when HFSC is utilized with NETEM. The patch only checks the cl->cl_nactive field to determine whether it is the first insertion or not [2], but this field is only incremented by init_vf [3]. By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the check and insert the class twice in the eltree. Under normal conditions, this would lead to an infinite loop in hfsc_dequeue for the reasons we already explained in this report [5]. However, if TBF is added as root qdisc and it is configured with a very low rate, it can be utilized to prevent packets from being dequeued. This behavior can be exploited to perform subsequent ...  | 0% Низкий | 5 месяцев назад | ||
BDU:2025-12349 Уязвимость компонента net/sched/sch_hfsc.c ядра операционной системы Linux, позволяющая нарушителю получить доступ к конфиденциальным данным, нарушить их целостность, а также вызвать отказ в обслуживании  | CVSS3: 5.6  | 0% Низкий | 6 месяцев назад | |
SUSE-SU-2025:03222-1 Security update for the Linux Kernel (Live Patch 1 for SLE 15 SP7)  | около 2 месяцев назад | |||
SUSE-SU-2025:03213-1 Security update for the Linux Kernel (Live Patch 12 for SLE 15 SP6)  | около 2 месяцев назад | |||
SUSE-SU-2025:03182-1 Security update for the Linux Kernel (Live Patch 41 for SLE 15 SP4)  | около 2 месяцев назад | |||
SUSE-SU-2025:03154-1 Security update for the Linux Kernel (Live Patch 58 for SLE 15 SP3)  | около 2 месяцев назад | |||
SUSE-SU-2025:03104-1 Security update for the Linux Kernel RT (Live Patch 1 for SLE 15 SP7)  | около 2 месяцев назад | |||
SUSE-SU-2025:03195-1 Security update for the Linux Kernel (Live Patch 27 for SLE 15 SP5)  | около 2 месяцев назад | |||
SUSE-SU-2025:03184-1 Security update for the Linux Kernel (Live Patch 40 for SLE 15 SP4)  | около 2 месяцев назад | |||
SUSE-SU-2025:03179-1 Security update for the Linux Kernel (Live Patch 39 for SLE 15 SP4)  | около 2 месяцев назад | |||
SUSE-SU-2025:03153-1 Security update for the Linux Kernel (Live Patch 56 for SLE 15 SP3)  | около 2 месяцев назад | |||
SUSE-SU-2025:03148-1 Security update for the Linux Kernel (Live Patch 57 for SLE 15 SP3)  | около 2 месяцев назад | |||
SUSE-SU-2025:03106-1 Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP7)  | около 2 месяцев назад | |||
SUSE-SU-2025:03212-1 Security update for the Linux Kernel (Live Patch 10 for SLE 15 SP6)  | около 2 месяцев назад | |||
SUSE-SU-2025:03207-1 Security update for the Linux Kernel (Live Patch 25 for SLE 15 SP5)  | около 2 месяцев назад | 
Уязвимостей на страницу