Количество 87
Количество 87
SUSE-SU-2026:3746-1
Security update for the Linux Kernel RT (Live Patch 12 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:3744-1
Security update for the Linux Kernel (Live Patch 38 for SUSE Linux Enterprise 15 SP5)
SUSE-SU-2026:3771-1
Security update for the Linux Kernel (Live Patch 10 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:3760-1
Security update for the Linux Kernel (Live Patch 25 for SUSE Linux Enterprise 15 SP6)
SUSE-SU-2026:3768-1
Security update for the Linux Kernel (Live Patch 7 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:3761-1
Security update for the Linux Kernel (Live Patch 8 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:3748-1
Security update for the Linux Kernel RT (Live Patch 8 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:3719-1
Security update for the Linux Kernel (Live Patch 20 for SUSE Linux Enterprise 15 SP6)
SUSE-SU-2026:3754-1
Security update for the Linux Kernel (Live Patch 4 for SUSE Linux Enterprise 15 SP7)
CVE-2026-52993
In the Linux kernel, the following vulnerability has been resolved: tipc: fix double-free in tipc_buf_append() tipc_msg_validate() can potentially reallocate the skb it is validating, freeing the old one. In tipc_buf_append(), it was being called with a pointer to a local variable which was a copy of the caller's skb pointer. If the skb was reallocated and validation subsequently failed, the error handling path would free the original skb pointer, which had already been freed, leading to double-free. Fix this by checking if head now points to a newly allocated reassembled skb. If it does, reassign *headbuf for later freeing operations.
CVE-2026-52993
In the Linux kernel, the following vulnerability has been resolved: tipc: fix double-free in tipc_buf_append() tipc_msg_validate() can potentially reallocate the skb it is validating, freeing the old one. In tipc_buf_append(), it was being called with a pointer to a local variable which was a copy of the caller's skb pointer. If the skb was reallocated and validation subsequently failed, the error handling path would free the original skb pointer, which had already been freed, leading to double-free. Fix this by checking if head now points to a newly allocated reassembled skb. If it does, reassign *headbuf for later freeing operations.
CVE-2026-52993
In the Linux kernel, the following vulnerability has been resolved: tipc: fix double-free in tipc_buf_append() tipc_msg_validate() can potentially reallocate the skb it is validating, freeing the old one. In tipc_buf_append(), it was being called with a pointer to a local variable which was a copy of the caller's skb pointer. If the skb was reallocated and validation subsequently failed, the error handling path would free the original skb pointer, which had already been freed, leading to double-free. Fix this by checking if head now points to a newly allocated reassembled skb. If it does, reassign *headbuf for later freeing operations.
CVE-2026-52993
tipc: fix double-free in tipc_buf_append()
CVE-2026-52993
In the Linux kernel, the following vulnerability has been resolved: t ...
SUSE-SU-2026:3044-1
Security update for the Linux Kernel
SUSE-SU-2026:3089-1
Security update for the Linux Kernel
CVE-2026-64530
In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle tcf_classify() can return TC_ACT_CONSUMED while the skb is held by the defragmentation engine (e.g. act_ct on out-of-order fragments). When that happens the skb is no longer owned by the caller and must not be touched again. tcf_qevent_handle() did not handle TC_ACT_CONSUMED: it fell through the switch and returned the skb to the caller as if classification had passed. The only qdisc that wires up qevents today is RED, via three call sites (qe_mark on RED_PROB_MARK/HARD_MARK, qe_early_drop on congestion_drop) red_enqueue() was continuing to operate on an skb it no longer owns in this case -- enqueueing it, dropping it, or updating statistics. Resulting in a UAF. tc qdisc add dev eth0 root handle 1: red ... qevent early_drop block 10 tc filter add block 10 ... action ct (with ct defrag enabled and traffic that produces out-of-order fragments, e.g. a fra...
CVE-2026-64530
In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle tcf_classify() can return TC_ACT_CONSUMED while the skb is held by the defragmentation engine (e.g. act_ct on out-of-order fragments). When that happens the skb is no longer owned by the caller and must not be touched again. tcf_qevent_handle() did not handle TC_ACT_CONSUMED: it fell through the switch and returned the skb to the caller as if classification had passed. The only qdisc that wires up qevents today is RED, via three call sites (qe_mark on RED_PROB_MARK/HARD_MARK, qe_early_drop on congestion_drop) red_enqueue() was continuing to operate on an skb it no longer owns in this case -- enqueueing it, dropping it, or updating statistics. Resulting in a UAF. tc qdisc add dev eth0 root handle 1: red ... qevent early_drop block 10 tc filter add block 10 ... action ct (with ct defrag enabled and traffic that produces out-of-order fragments, e.g. a fra...
CVE-2026-64530
In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle tcf_classify() can return TC_ACT_CONSUMED while the skb is held by the defragmentation engine (e.g. act_ct on out-of-order fragments). When that happens the skb is no longer owned by the caller and must not be touched again. tcf_qevent_handle() did not handle TC_ACT_CONSUMED: it fell through the switch and returned the skb to the caller as if classification had passed. The only qdisc that wires up qevents today is RED, via three call sites (qe_mark on RED_PROB_MARK/HARD_MARK, qe_early_drop on congestion_drop) red_enqueue() was continuing to operate on an skb it no longer owns in this case -- enqueueing it, dropping it, or updating statistics. Resulting in a UAF. tc qdisc add dev eth0 root handle 1: red ... qevent early_drop block 10 tc filter add block 10 ... action ct (with ct defrag enabled and traffic that produces out-of-order fragments,
CVE-2026-64530
net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
SUSE-SU-2026:3746-1 Security update for the Linux Kernel RT (Live Patch 12 for SUSE Linux Enterprise 15 SP7) | 17 дней назад | |||
SUSE-SU-2026:3744-1 Security update for the Linux Kernel (Live Patch 38 for SUSE Linux Enterprise 15 SP5) | 17 дней назад | |||
SUSE-SU-2026:3771-1 Security update for the Linux Kernel (Live Patch 10 for SUSE Linux Enterprise 15 SP7) | 17 дней назад | |||
SUSE-SU-2026:3760-1 Security update for the Linux Kernel (Live Patch 25 for SUSE Linux Enterprise 15 SP6) | 17 дней назад | |||
SUSE-SU-2026:3768-1 Security update for the Linux Kernel (Live Patch 7 for SUSE Linux Enterprise 15 SP7) | 17 дней назад | |||
SUSE-SU-2026:3761-1 Security update for the Linux Kernel (Live Patch 8 for SUSE Linux Enterprise 15 SP7) | 17 дней назад | |||
SUSE-SU-2026:3748-1 Security update for the Linux Kernel RT (Live Patch 8 for SUSE Linux Enterprise 15 SP7) | 17 дней назад | |||
SUSE-SU-2026:3719-1 Security update for the Linux Kernel (Live Patch 20 for SUSE Linux Enterprise 15 SP6) | 18 дней назад | |||
SUSE-SU-2026:3754-1 Security update for the Linux Kernel (Live Patch 4 for SUSE Linux Enterprise 15 SP7) | 17 дней назад | |||
CVE-2026-52993 In the Linux kernel, the following vulnerability has been resolved: tipc: fix double-free in tipc_buf_append() tipc_msg_validate() can potentially reallocate the skb it is validating, freeing the old one. In tipc_buf_append(), it was being called with a pointer to a local variable which was a copy of the caller's skb pointer. If the skb was reallocated and validation subsequently failed, the error handling path would free the original skb pointer, which had already been freed, leading to double-free. Fix this by checking if head now points to a newly allocated reassembled skb. If it does, reassign *headbuf for later freeing operations. | CVSS3: 9.8 | 0% Низкий | 3 месяца назад | |
CVE-2026-52993 In the Linux kernel, the following vulnerability has been resolved: tipc: fix double-free in tipc_buf_append() tipc_msg_validate() can potentially reallocate the skb it is validating, freeing the old one. In tipc_buf_append(), it was being called with a pointer to a local variable which was a copy of the caller's skb pointer. If the skb was reallocated and validation subsequently failed, the error handling path would free the original skb pointer, which had already been freed, leading to double-free. Fix this by checking if head now points to a newly allocated reassembled skb. If it does, reassign *headbuf for later freeing operations. | CVSS3: 7 | 0% Низкий | 3 месяца назад | |
CVE-2026-52993 In the Linux kernel, the following vulnerability has been resolved: tipc: fix double-free in tipc_buf_append() tipc_msg_validate() can potentially reallocate the skb it is validating, freeing the old one. In tipc_buf_append(), it was being called with a pointer to a local variable which was a copy of the caller's skb pointer. If the skb was reallocated and validation subsequently failed, the error handling path would free the original skb pointer, which had already been freed, leading to double-free. Fix this by checking if head now points to a newly allocated reassembled skb. If it does, reassign *headbuf for later freeing operations. | CVSS3: 9.8 | 0% Низкий | 3 месяца назад | |
CVE-2026-52993 tipc: fix double-free in tipc_buf_append() | CVSS3: 9.8 | 0% Низкий | 3 месяца назад | |
CVE-2026-52993 In the Linux kernel, the following vulnerability has been resolved: t ... | CVSS3: 9.8 | 0% Низкий | 3 месяца назад | |
SUSE-SU-2026:3044-1 Security update for the Linux Kernel | около 2 месяцев назад | |||
SUSE-SU-2026:3089-1 Security update for the Linux Kernel | около 2 месяцев назад | |||
CVE-2026-64530 In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle tcf_classify() can return TC_ACT_CONSUMED while the skb is held by the defragmentation engine (e.g. act_ct on out-of-order fragments). When that happens the skb is no longer owned by the caller and must not be touched again. tcf_qevent_handle() did not handle TC_ACT_CONSUMED: it fell through the switch and returned the skb to the caller as if classification had passed. The only qdisc that wires up qevents today is RED, via three call sites (qe_mark on RED_PROB_MARK/HARD_MARK, qe_early_drop on congestion_drop) red_enqueue() was continuing to operate on an skb it no longer owns in this case -- enqueueing it, dropping it, or updating statistics. Resulting in a UAF. tc qdisc add dev eth0 root handle 1: red ... qevent early_drop block 10 tc filter add block 10 ... action ct (with ct defrag enabled and traffic that produces out-of-order fragments, e.g. a fra... | CVSS3: 9.8 | 1% Низкий | около 2 месяцев назад | |
CVE-2026-64530 In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle tcf_classify() can return TC_ACT_CONSUMED while the skb is held by the defragmentation engine (e.g. act_ct on out-of-order fragments). When that happens the skb is no longer owned by the caller and must not be touched again. tcf_qevent_handle() did not handle TC_ACT_CONSUMED: it fell through the switch and returned the skb to the caller as if classification had passed. The only qdisc that wires up qevents today is RED, via three call sites (qe_mark on RED_PROB_MARK/HARD_MARK, qe_early_drop on congestion_drop) red_enqueue() was continuing to operate on an skb it no longer owns in this case -- enqueueing it, dropping it, or updating statistics. Resulting in a UAF. tc qdisc add dev eth0 root handle 1: red ... qevent early_drop block 10 tc filter add block 10 ... action ct (with ct defrag enabled and traffic that produces out-of-order fragments, e.g. a fra... | CVSS3: 7.8 | 1% Низкий | 3 месяца назад | |
CVE-2026-64530 In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle tcf_classify() can return TC_ACT_CONSUMED while the skb is held by the defragmentation engine (e.g. act_ct on out-of-order fragments). When that happens the skb is no longer owned by the caller and must not be touched again. tcf_qevent_handle() did not handle TC_ACT_CONSUMED: it fell through the switch and returned the skb to the caller as if classification had passed. The only qdisc that wires up qevents today is RED, via three call sites (qe_mark on RED_PROB_MARK/HARD_MARK, qe_early_drop on congestion_drop) red_enqueue() was continuing to operate on an skb it no longer owns in this case -- enqueueing it, dropping it, or updating statistics. Resulting in a UAF. tc qdisc add dev eth0 root handle 1: red ... qevent early_drop block 10 tc filter add block 10 ... action ct (with ct defrag enabled and traffic that produces out-of-order fragments, | CVSS3: 9.8 | 1% Низкий | около 2 месяцев назад | |
CVE-2026-64530 net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle | CVSS3: 7 | 1% Низкий | около 1 месяца назад |
Уязвимостей на страницу