Количество 52
Количество 52

CVE-2025-21702
In the Linux kernel, the following vulnerability has been resolved: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 Expected behaviour: In case we reach scheduler's limit, pfifo_tail_enqueue() will drop a packet in scheduler's queue and decrease scheduler's qlen by one. Then, pfifo_tail_enqueue() enqueue new packet and increase scheduler's qlen by one. Finally, pfifo_tail_enqueue() return `NET_XMIT_CN` status code. Weird behaviour: In case we set `sch->limit == 0` and trigger pfifo_tail_enqueue() on a scheduler that has no packet, the 'drop a packet' step will do nothing. This means the scheduler's qlen still has value equal 0. Then, we continue to enqueue new packet and increase scheduler's qlen by one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by one and return `NET_XMIT_CN` status code. The problem is: Let's say we have two qdiscs: Qdisc_A and Qdisc_B. - Qdisc_A's type must have '->graft()' function to create parent/child relationship. Let's say Q...

CVE-2025-21702
In the Linux kernel, the following vulnerability has been resolved: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 Expected behaviour: In case we reach scheduler's limit, pfifo_tail_enqueue() will drop a packet in scheduler's queue and decrease scheduler's qlen by one. Then, pfifo_tail_enqueue() enqueue new packet and increase scheduler's qlen by one. Finally, pfifo_tail_enqueue() return `NET_XMIT_CN` status code. Weird behaviour: In case we set `sch->limit == 0` and trigger pfifo_tail_enqueue() on a scheduler that has no packet, the 'drop a packet' step will do nothing. This means the scheduler's qlen still has value equal 0. Then, we continue to enqueue new packet and increase scheduler's qlen by one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by one and return `NET_XMIT_CN` status code. The problem is: Let's say we have two qdiscs: Qdisc_A and Qdisc_B. - Qdisc_A's type must have '->graft()' function to create parent/child relationship. Let's say Q...

CVE-2025-21702
In the Linux kernel, the following vulnerability has been resolved: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 Expected behaviour: In case we reach scheduler's limit, pfifo_tail_enqueue() will drop a packet in scheduler's queue and decrease scheduler's qlen by one. Then, pfifo_tail_enqueue() enqueue new packet and increase scheduler's qlen by one. Finally, pfifo_tail_enqueue() return `NET_XMIT_CN` status code. Weird behaviour: In case we set `sch->limit == 0` and trigger pfifo_tail_enqueue() on a scheduler that has no packet, the 'drop a packet' step will do nothing. This means the scheduler's qlen still has value equal 0. Then, we continue to enqueue new packet and increase scheduler's qlen by one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by one and return `NET_XMIT_CN` status code. The problem is: Let's say we have two qdiscs: Qdisc_A and Qdisc_B. - Qdisc_A's type must have '->graft()' function to create parent/child relationship. Let's
CVE-2025-21702
In the Linux kernel, the following vulnerability has been resolved: p ...
GHSA-c82f-pmfx-x3vv
In the Linux kernel, the following vulnerability has been resolved: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 Expected behaviour: In case we reach scheduler's limit, pfifo_tail_enqueue() will drop a packet in scheduler's queue and decrease scheduler's qlen by one. Then, pfifo_tail_enqueue() enqueue new packet and increase scheduler's qlen by one. Finally, pfifo_tail_enqueue() return `NET_XMIT_CN` status code. Weird behaviour: In case we set `sch->limit == 0` and trigger pfifo_tail_enqueue() on a scheduler that has no packet, the 'drop a packet' step will do nothing. This means the scheduler's qlen still has value equal 0. Then, we continue to enqueue new packet and increase scheduler's qlen by one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by one and return `NET_XMIT_CN` status code. The problem is: Let's say we have two qdiscs: Qdisc_A and Qdisc_B. - Qdisc_A's type must have '->graft()' function to create parent/child relationship. Let...

BDU:2025-02167
Уязвимость функции pfifo_tail_enqueue() (net/sched/sch_fifo.c) ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации.

SUSE-SU-2025:02710-1
Security update for the Linux Kernel (Live Patch 10 for SLE 15 SP6)

SUSE-SU-2025:02704-1
Security update for the Linux Kernel (Live Patch 58 for SLE 15 SP3)

SUSE-SU-2025:02693-1
Security update for the Linux Kernel (Live Patch 11 for SLE 15 SP6)

SUSE-SU-2025:02689-1
Security update for the Linux Kernel (Live Patch 9 for SLE 15 SP6)

SUSE-SU-2025:02687-1
Security update for the Linux Kernel (Live Patch 54 for SLE 15 SP3)

SUSE-SU-2025:02676-1
Security update for the Linux Kernel (Live Patch 26 for SLE 15 SP5)

SUSE-SU-2025:02637-1
Security update for the Linux Kernel RT (Live Patch 10 for SLE 15 SP6)

SUSE-SU-2025:02619-1
Security update for the Linux Kernel (Live Patch 56 for SLE 15 SP3)

SUSE-SU-2025:02608-1
Security update for the Linux Kernel (Live Patch 57 for SLE 15 SP3)

SUSE-SU-2025:02606-1
Security update for the Linux Kernel (Live Patch 66 for SLE 12 SP5)

SUSE-SU-2025:02602-1
Security update for the Linux Kernel RT (Live Patch 8 for SLE 15 SP6)

SUSE-SU-2025:02708-1
Security update for the Linux Kernel (Live Patch 41 for SLE 15 SP4)

SUSE-SU-2025:02697-1
Security update for the Linux Kernel (Live Patch 50 for SLE 15 SP3)

SUSE-SU-2025:02673-1
Security update for the Linux Kernel (Live Patch 7 for SLE 15 SP6)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
---|---|---|---|---|
![]() | CVE-2025-21702 In the Linux kernel, the following vulnerability has been resolved: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 Expected behaviour: In case we reach scheduler's limit, pfifo_tail_enqueue() will drop a packet in scheduler's queue and decrease scheduler's qlen by one. Then, pfifo_tail_enqueue() enqueue new packet and increase scheduler's qlen by one. Finally, pfifo_tail_enqueue() return `NET_XMIT_CN` status code. Weird behaviour: In case we set `sch->limit == 0` and trigger pfifo_tail_enqueue() on a scheduler that has no packet, the 'drop a packet' step will do nothing. This means the scheduler's qlen still has value equal 0. Then, we continue to enqueue new packet and increase scheduler's qlen by one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by one and return `NET_XMIT_CN` status code. The problem is: Let's say we have two qdiscs: Qdisc_A and Qdisc_B. - Qdisc_A's type must have '->graft()' function to create parent/child relationship. Let's say Q... | 0% Низкий | 7 месяцев назад | |
![]() | CVE-2025-21702 In the Linux kernel, the following vulnerability has been resolved: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 Expected behaviour: In case we reach scheduler's limit, pfifo_tail_enqueue() will drop a packet in scheduler's queue and decrease scheduler's qlen by one. Then, pfifo_tail_enqueue() enqueue new packet and increase scheduler's qlen by one. Finally, pfifo_tail_enqueue() return `NET_XMIT_CN` status code. Weird behaviour: In case we set `sch->limit == 0` and trigger pfifo_tail_enqueue() on a scheduler that has no packet, the 'drop a packet' step will do nothing. This means the scheduler's qlen still has value equal 0. Then, we continue to enqueue new packet and increase scheduler's qlen by one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by one and return `NET_XMIT_CN` status code. The problem is: Let's say we have two qdiscs: Qdisc_A and Qdisc_B. - Qdisc_A's type must have '->graft()' function to create parent/child relationship. Let's say Q... | CVSS3: 7 | 0% Низкий | 7 месяцев назад |
![]() | CVE-2025-21702 In the Linux kernel, the following vulnerability has been resolved: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 Expected behaviour: In case we reach scheduler's limit, pfifo_tail_enqueue() will drop a packet in scheduler's queue and decrease scheduler's qlen by one. Then, pfifo_tail_enqueue() enqueue new packet and increase scheduler's qlen by one. Finally, pfifo_tail_enqueue() return `NET_XMIT_CN` status code. Weird behaviour: In case we set `sch->limit == 0` and trigger pfifo_tail_enqueue() on a scheduler that has no packet, the 'drop a packet' step will do nothing. This means the scheduler's qlen still has value equal 0. Then, we continue to enqueue new packet and increase scheduler's qlen by one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by one and return `NET_XMIT_CN` status code. The problem is: Let's say we have two qdiscs: Qdisc_A and Qdisc_B. - Qdisc_A's type must have '->graft()' function to create parent/child relationship. Let's | 0% Низкий | 7 месяцев назад | |
CVE-2025-21702 In the Linux kernel, the following vulnerability has been resolved: p ... | 0% Низкий | 7 месяцев назад | ||
GHSA-c82f-pmfx-x3vv In the Linux kernel, the following vulnerability has been resolved: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 Expected behaviour: In case we reach scheduler's limit, pfifo_tail_enqueue() will drop a packet in scheduler's queue and decrease scheduler's qlen by one. Then, pfifo_tail_enqueue() enqueue new packet and increase scheduler's qlen by one. Finally, pfifo_tail_enqueue() return `NET_XMIT_CN` status code. Weird behaviour: In case we set `sch->limit == 0` and trigger pfifo_tail_enqueue() on a scheduler that has no packet, the 'drop a packet' step will do nothing. This means the scheduler's qlen still has value equal 0. Then, we continue to enqueue new packet and increase scheduler's qlen by one. In summary, we can leverage pfifo_tail_enqueue() to increase qlen by one and return `NET_XMIT_CN` status code. The problem is: Let's say we have two qdiscs: Qdisc_A and Qdisc_B. - Qdisc_A's type must have '->graft()' function to create parent/child relationship. Let... | 0% Низкий | 7 месяцев назад | ||
![]() | BDU:2025-02167 Уязвимость функции pfifo_tail_enqueue() (net/sched/sch_fifo.c) ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации. | CVSS3: 7 | 0% Низкий | 7 месяцев назад |
![]() | SUSE-SU-2025:02710-1 Security update for the Linux Kernel (Live Patch 10 for SLE 15 SP6) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02704-1 Security update for the Linux Kernel (Live Patch 58 for SLE 15 SP3) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02693-1 Security update for the Linux Kernel (Live Patch 11 for SLE 15 SP6) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02689-1 Security update for the Linux Kernel (Live Patch 9 for SLE 15 SP6) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02687-1 Security update for the Linux Kernel (Live Patch 54 for SLE 15 SP3) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02676-1 Security update for the Linux Kernel (Live Patch 26 for SLE 15 SP5) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02637-1 Security update for the Linux Kernel RT (Live Patch 10 for SLE 15 SP6) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02619-1 Security update for the Linux Kernel (Live Patch 56 for SLE 15 SP3) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02608-1 Security update for the Linux Kernel (Live Patch 57 for SLE 15 SP3) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02606-1 Security update for the Linux Kernel (Live Patch 66 for SLE 12 SP5) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02602-1 Security update for the Linux Kernel RT (Live Patch 8 for SLE 15 SP6) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02708-1 Security update for the Linux Kernel (Live Patch 41 for SLE 15 SP4) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02697-1 Security update for the Linux Kernel (Live Patch 50 for SLE 15 SP3) | около 1 месяца назад | ||
![]() | SUSE-SU-2025:02673-1 Security update for the Linux Kernel (Live Patch 7 for SLE 15 SP6) | около 1 месяца назад |
Уязвимостей на страницу