Количество 21
Количество 21
CVE-2026-43496
In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_red: Replace direct dequeue call with peek and qdisc_dequeue_peeked When red qdisc has children (eg qfq qdisc) whose peek() callback is qdisc_peek_dequeued(), we could get a kernel panic. When the parent of such qdiscs (eg illustrated in patch #3 as tbf) wants to retrieve an skb from its child (red in this case), it will do the following: 1a. do a peek() - and when sensing there's an skb the child can offer, then - the child in this case(red) calls its child's (qfq) peek. qfq does the right thing and will return the gso_skb queue packet. Note: if there wasnt a gso_skb entry then qfq will store it there. 1b. invoke a dequeue() on the child (red). And herein lies the problem. - red will call the child's dequeue() which will essentially just try to grab something of qfq's queue. [ 78.667668][ T363] KASAN: null-ptr-deref in range [0x0000000000000048-0x000000000000004f] [ 78.667927][ T363] CPU: 1 UID...
CVE-2026-43496
In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_red: Replace direct dequeue call with peek and qdisc_dequeue_peeked When red qdisc has children (eg qfq qdisc) whose peek() callback is qdisc_peek_dequeued(), we could get a kernel panic. When the parent of such qdiscs (eg illustrated in patch #3 as tbf) wants to retrieve an skb from its child (red in this case), it will do the following: 1a. do a peek() - and when sensing there's an skb the child can offer, then - the child in this case(red) calls its child's (qfq) peek. qfq does the right thing and will return the gso_skb queue packet. Note: if there wasnt a gso_skb entry then qfq will store it there. 1b. invoke a dequeue() on the child (red). And herein lies the problem. - red will call the child's dequeue() which will essentially just try to grab something of qfq's queue. [ 78.667668][ T363] KASAN: null-ptr-deref in range [0x0000000000000048-0x000000000000004f] [ 78.667927][ T363] CPU: 1 UID...
CVE-2026-43496
In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_red: Replace direct dequeue call with peek and qdisc_dequeue_peeked When red qdisc has children (eg qfq qdisc) whose peek() callback is qdisc_peek_dequeued(), we could get a kernel panic. When the parent of such qdiscs (eg illustrated in patch #3 as tbf) wants to retrieve an skb from its child (red in this case), it will do the following: 1a. do a peek() - and when sensing there's an skb the child can offer, then - the child in this case(red) calls its child's (qfq) peek. qfq does the right thing and will return the gso_skb queue packet. Note: if there wasnt a gso_skb entry then qfq will store it there. 1b. invoke a dequeue() on the child (red). And herein lies the problem. - red will call the child's dequeue() which will essentially just try to grab something of qfq's queue. [ 78.667668][ T363] KASAN: null-ptr-deref in range [0x0000000000000048-0x000000000000004f
CVE-2026-43496
net/sched: sch_red: Replace direct dequeue call with peek and qdisc_dequeue_peeked
CVE-2026-43496
In the Linux kernel, the following vulnerability has been resolved: n ...
GHSA-86mq-wj5h-4fr6
In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_red: Replace direct dequeue call with peek and qdisc_dequeue_peeked When red qdisc has children (eg qfq qdisc) whose peek() callback is qdisc_peek_dequeued(), we could get a kernel panic. When the parent of such qdiscs (eg illustrated in patch #3 as tbf) wants to retrieve an skb from its child (red in this case), it will do the following: 1a. do a peek() - and when sensing there's an skb the child can offer, then - the child in this case(red) calls its child's (qfq) peek. qfq does the right thing and will return the gso_skb queue packet. Note: if there wasnt a gso_skb entry then qfq will store it there. 1b. invoke a dequeue() on the child (red). And herein lies the problem. - red will call the child's dequeue() which will essentially just try to grab something of qfq's queue. [ 78.667668][ T363] KASAN: null-ptr-deref in range [0x0000000000000048-0x0000000000000...
BDU:2026-09582
Уязвимость функции qdisc_peek_dequeued() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20261012-80-0098
Уязвимость kernel-lt
ROS-20261012-73-0097
Уязвимость kernel-lt
SUSE-SU-2026:3594-1
Security update for the Linux Kernel
ALT-PU-2026-8600
ALT-PU-2026-8600: package `kernel-image-std-def` update to version 5.10.258-alt1
ALT-PU-2026-8598
ALT-PU-2026-8598: package `kernel-image-un-def` update to version 6.1.175-alt1
ELBA-2026-500163
ELBA-2026-500163: Unbreakable Enterprise kernel bug fix update (NA)
SUSE-SU-2026:3166-1
Security update for the Linux Kernel
SUSE-SU-2026:3130-1
Security update for the Linux Kernel
ALT-PU-2026-8628
ALT-PU-2026-8628: package `kernel-image-6.18` update to version 6.18.34-alt1
ALT-PU-2026-9890
ALT-PU-2026-9890: package `kernel-image-rpi-un` update to version 6.12.94-alt1
openSUSE-SU-2026:21555-1
Security update for the Linux Kernel
ALT-PU-2026-9892
ALT-PU-2026-9892: package `kernel-image-6.12` update to version 6.12.94-alt1
ALT-PU-2026-11671
ALT-PU-2026-11671: package `kernel-image-rt` update to version 6.12.98-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-43496 In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_red: Replace direct dequeue call with peek and qdisc_dequeue_peeked When red qdisc has children (eg qfq qdisc) whose peek() callback is qdisc_peek_dequeued(), we could get a kernel panic. When the parent of such qdiscs (eg illustrated in patch #3 as tbf) wants to retrieve an skb from its child (red in this case), it will do the following: 1a. do a peek() - and when sensing there's an skb the child can offer, then - the child in this case(red) calls its child's (qfq) peek. qfq does the right thing and will return the gso_skb queue packet. Note: if there wasnt a gso_skb entry then qfq will store it there. 1b. invoke a dequeue() on the child (red). And herein lies the problem. - red will call the child's dequeue() which will essentially just try to grab something of qfq's queue. [ 78.667668][ T363] KASAN: null-ptr-deref in range [0x0000000000000048-0x000000000000004f] [ 78.667927][ T363] CPU: 1 UID... | CVSS3: 5.5 | 0% Низкий | 5 месяцев назад | |
CVE-2026-43496 In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_red: Replace direct dequeue call with peek and qdisc_dequeue_peeked When red qdisc has children (eg qfq qdisc) whose peek() callback is qdisc_peek_dequeued(), we could get a kernel panic. When the parent of such qdiscs (eg illustrated in patch #3 as tbf) wants to retrieve an skb from its child (red in this case), it will do the following: 1a. do a peek() - and when sensing there's an skb the child can offer, then - the child in this case(red) calls its child's (qfq) peek. qfq does the right thing and will return the gso_skb queue packet. Note: if there wasnt a gso_skb entry then qfq will store it there. 1b. invoke a dequeue() on the child (red). And herein lies the problem. - red will call the child's dequeue() which will essentially just try to grab something of qfq's queue. [ 78.667668][ T363] KASAN: null-ptr-deref in range [0x0000000000000048-0x000000000000004f] [ 78.667927][ T363] CPU: 1 UID... | CVSS3: 5.5 | 0% Низкий | 5 месяцев назад | |
CVE-2026-43496 In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_red: Replace direct dequeue call with peek and qdisc_dequeue_peeked When red qdisc has children (eg qfq qdisc) whose peek() callback is qdisc_peek_dequeued(), we could get a kernel panic. When the parent of such qdiscs (eg illustrated in patch #3 as tbf) wants to retrieve an skb from its child (red in this case), it will do the following: 1a. do a peek() - and when sensing there's an skb the child can offer, then - the child in this case(red) calls its child's (qfq) peek. qfq does the right thing and will return the gso_skb queue packet. Note: if there wasnt a gso_skb entry then qfq will store it there. 1b. invoke a dequeue() on the child (red). And herein lies the problem. - red will call the child's dequeue() which will essentially just try to grab something of qfq's queue. [ 78.667668][ T363] KASAN: null-ptr-deref in range [0x0000000000000048-0x000000000000004f | CVSS3: 5.5 | 0% Низкий | 5 месяцев назад | |
CVE-2026-43496 net/sched: sch_red: Replace direct dequeue call with peek and qdisc_dequeue_peeked | CVSS3: 5.5 | 0% Низкий | 5 месяцев назад | |
CVE-2026-43496 In the Linux kernel, the following vulnerability has been resolved: n ... | CVSS3: 5.5 | 0% Низкий | 5 месяцев назад | |
GHSA-86mq-wj5h-4fr6 In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_red: Replace direct dequeue call with peek and qdisc_dequeue_peeked When red qdisc has children (eg qfq qdisc) whose peek() callback is qdisc_peek_dequeued(), we could get a kernel panic. When the parent of such qdiscs (eg illustrated in patch #3 as tbf) wants to retrieve an skb from its child (red in this case), it will do the following: 1a. do a peek() - and when sensing there's an skb the child can offer, then - the child in this case(red) calls its child's (qfq) peek. qfq does the right thing and will return the gso_skb queue packet. Note: if there wasnt a gso_skb entry then qfq will store it there. 1b. invoke a dequeue() on the child (red). And herein lies the problem. - red will call the child's dequeue() which will essentially just try to grab something of qfq's queue. [ 78.667668][ T363] KASAN: null-ptr-deref in range [0x0000000000000048-0x0000000000000... | CVSS3: 5.5 | 0% Низкий | 5 месяцев назад | |
BDU:2026-09582 Уязвимость функции qdisc_peek_dequeued() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | 6 месяцев назад | |
ROS-20261012-80-0098 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 13 дней назад | |
ROS-20261012-73-0097 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 13 дней назад | |
SUSE-SU-2026:3594-1 Security update for the Linux Kernel | 2 месяца назад | |||
ALT-PU-2026-8600 ALT-PU-2026-8600: package `kernel-image-std-def` update to version 5.10.258-alt1 | CVSS3: 9.8 | 4 месяца назад | ||
ALT-PU-2026-8598 ALT-PU-2026-8598: package `kernel-image-un-def` update to version 6.1.175-alt1 | CVSS3: 9.8 | 4 месяца назад | ||
ELBA-2026-500163 ELBA-2026-500163: Unbreakable Enterprise kernel bug fix update (NA) | 3 месяца назад | |||
SUSE-SU-2026:3166-1 Security update for the Linux Kernel | 3 месяца назад | |||
SUSE-SU-2026:3130-1 Security update for the Linux Kernel | 3 месяца назад | |||
ALT-PU-2026-8628 ALT-PU-2026-8628: package `kernel-image-6.18` update to version 6.18.34-alt1 | CVSS3: 10 | 5 месяцев назад | ||
ALT-PU-2026-9890 ALT-PU-2026-9890: package `kernel-image-rpi-un` update to version 6.12.94-alt1 | CVSS3: 10 | 4 месяца назад | ||
openSUSE-SU-2026:21555-1 Security update for the Linux Kernel | 2 месяца назад | |||
ALT-PU-2026-9892 ALT-PU-2026-9892: package `kernel-image-6.12` update to version 6.12.94-alt1 | CVSS3: 10 | 4 месяца назад | ||
ALT-PU-2026-11671 ALT-PU-2026-11671: package `kernel-image-rt` update to version 6.12.98-alt1 | CVSS3: 10 | 3 месяца назад |
Уязвимостей на страницу