Поиск уязвимостей
Количество 24
Количество 24
CVE-2024-35839
In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead of net_device link. To peek into the original net_device we will use de...
CVE-2024-35839
In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead of net_device link. To peek into the original net_device we will use de...
CVE-2024-35839
In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead
CVE-2024-35839
netfilter: bridge: replace physindev with physinif in nf_bridge_info
CVE-2024-35839
In the Linux kernel, the following vulnerability has been resolved: n ...
GHSA-gw6v-2949-7c2m
In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex inst...
BDU:2025-13352
Уязвимость компонента netfilter ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ELSA-2024-5928
ELSA-2024-5928: kernel security update (IMPORTANT)
ROS-20251017-02
Множественные уязвимости kernel-lt
RLSA-2024:8856
Moderate: kernel security update
ELSA-2024-8856
ELSA-2024-8856: kernel security update (MODERATE)
ALT-PU-2024-18054
ALT-PU-2024-18054: package `kernel-image-un-def` update to version 6.1.75-alt1
SUSE-SU-2025:0153-1
Security update for the Linux Kernel
SUSE-SU-2025:0117-1
Security update for the Linux Kernel
SUSE-SU-2025:0154-1
Security update for the Linux Kernel
ALT-PU-2024-18358
ALT-PU-2024-18358: package `kernel-image-std-def` update to version 6.1.75-alt2
ALT-PU-2024-18254
ALT-PU-2024-18254: package `kernel-image-rt` update to version 6.1.75-alt1.rt23
SUSE-SU-2025:02334-1
Security update for the Linux Kernel
ALT-PU-2024-18462
ALT-PU-2024-18462: package `kernel-image-un-def` update to version 6.6.14-alt1
ALT-PU-2024-18203
ALT-PU-2024-18203: package `kernel-image-pine` update to version 6.6.14-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-35839 In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead of net_device link. To peek into the original net_device we will use de... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35839 In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead of net_device link. To peek into the original net_device we will use de... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35839 In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-35839 netfilter: bridge: replace physindev with physinif in nf_bridge_info | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
CVE-2024-35839 In the Linux kernel, the following vulnerability has been resolved: n ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-gw6v-2949-7c2m In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex inst... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2025-13352 Уязвимость компонента netfilter ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
ELSA-2024-5928 ELSA-2024-5928: kernel security update (IMPORTANT) | около 2 лет назад | |||
ROS-20251017-02 Множественные уязвимости kernel-lt | CVSS3: 7.8 | около 1 года назад | ||
RLSA-2024:8856 Moderate: kernel security update | около 2 лет назад | |||
ELSA-2024-8856 ELSA-2024-8856: kernel security update (MODERATE) | около 2 лет назад | |||
ALT-PU-2024-18054 ALT-PU-2024-18054: package `kernel-image-un-def` update to version 6.1.75-alt1 | CVSS3: 9.8 | почти 3 года назад | ||
SUSE-SU-2025:0153-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2025:0117-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2025:0154-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2024-18358 ALT-PU-2024-18358: package `kernel-image-std-def` update to version 6.1.75-alt2 | CVSS3: 9.8 | почти 3 года назад | ||
ALT-PU-2024-18254 ALT-PU-2024-18254: package `kernel-image-rt` update to version 6.1.75-alt1.rt23 | CVSS3: 9.8 | почти 3 года назад | ||
SUSE-SU-2025:02334-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2024-18462 ALT-PU-2024-18462: package `kernel-image-un-def` update to version 6.6.14-alt1 | CVSS3: 9.8 | почти 3 года назад | ||
ALT-PU-2024-18203 ALT-PU-2024-18203: package `kernel-image-pine` update to version 6.6.14-alt1 | CVSS3: 9.8 | почти 3 года назад |
Уязвимостей на страницу