Поиск уязвимостей
Количество 25
Количество 25
CVE-2026-46306
In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 00000039 ...
CVE-2026-46306
In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 00000039 ...
CVE-2026-46306
In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 0000003
CVE-2026-46306
flow_dissector: do not dissect PPPoE PFC frames
CVE-2026-46306
In the Linux kernel, the following vulnerability has been resolved: f ...
ROS-20260708-80-0003
Уязвимость kernel-lt
GHSA-vm8v-fr63-mfh4
In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 0000...
BDU:2026-10467
Уязвимость модуля net/core/flow_dissector.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260708-73-0001
Уязвимость kernel-lt
RLSA-2026:66180
Important: kernel security, bug fix, and enhancement update
ELSA-2026-66180-0
ELSA-2026-66180-0: kernel security, bug fix, and enhancement update (IMPORTANT)
RLSA-2026:68531
Important: kernel security update
RLSA-2026:64775
Important: kernel security, bug fix, and enhancement update
ELSA-2026-68531
ELSA-2026-68531: kernel security update (IMPORTANT)
ELSA-2026-64775-0
ELSA-2026-64775-0: kernel security, bug fix, and enhancement update (IMPORTANT)
SUSE-SU-2026:3810-1
Security update for the Linux Kernel
SUSE-SU-2026:3790-1
Security update for the Linux Kernel
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)
ALT-PU-2026-8628
ALT-PU-2026-8628: package `kernel-image-6.18` update to version 6.18.34-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-46306 In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 00000039 ... | CVSS3: 7.5 | 0% Низкий | 5 месяцев назад | |
CVE-2026-46306 In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 00000039 ... | CVSS3: 6.5 | 0% Низкий | 5 месяцев назад | |
CVE-2026-46306 In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 0000003 | CVSS3: 7.5 | 0% Низкий | 5 месяцев назад | |
CVE-2026-46306 flow_dissector: do not dissect PPPoE PFC frames | CVSS3: 7 | 0% Низкий | 5 месяцев назад | |
CVE-2026-46306 In the Linux kernel, the following vulnerability has been resolved: f ... | CVSS3: 7.5 | 0% Низкий | 5 месяцев назад | |
ROS-20260708-80-0003 Уязвимость kernel-lt | CVSS3: 7.5 | 0% Низкий | 4 месяца назад | |
GHSA-vm8v-fr63-mfh4 In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the flow dissector driver has assumed an uncompressed frame until the blamed commit. During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures. The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface: $ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 0000... | CVSS3: 7.5 | 0% Низкий | 5 месяцев назад | |
BDU:2026-10467 Уязвимость модуля net/core/flow_dissector.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7.5 | 0% Низкий | 7 месяцев назад | |
ROS-20260708-73-0001 Уязвимость kernel-lt | CVSS3: 7.5 | 0% Низкий | 4 месяца назад | |
RLSA-2026:66180 Important: kernel security, bug fix, and enhancement update | около 2 месяцев назад | |||
ELSA-2026-66180-0 ELSA-2026-66180-0: kernel security, bug fix, and enhancement update (IMPORTANT) | около 2 месяцев назад | |||
RLSA-2026:68531 Important: kernel security update | около 2 месяцев назад | |||
RLSA-2026:64775 Important: kernel security, bug fix, and enhancement update | 2 месяца назад | |||
ELSA-2026-68531 ELSA-2026-68531: kernel security update (IMPORTANT) | около 2 месяцев назад | |||
ELSA-2026-64775-0 ELSA-2026-64775-0: kernel security, bug fix, and enhancement update (IMPORTANT) | около 2 месяцев назад | |||
SUSE-SU-2026:3810-1 Security update for the Linux Kernel | 2 месяца назад | |||
SUSE-SU-2026:3790-1 Security update for the Linux Kernel | 3 месяца назад | |||
ALT-PU-2026-8598 ALT-PU-2026-8598: package `kernel-image-un-def` update to version 6.1.175-alt1 | CVSS3: 9.8 | 5 месяцев назад | ||
ELBA-2026-500163 ELBA-2026-500163: Unbreakable Enterprise kernel bug fix update (NA) | 3 месяца назад | |||
ALT-PU-2026-8628 ALT-PU-2026-8628: package `kernel-image-6.18` update to version 6.18.34-alt1 | CVSS3: 10 | 5 месяцев назад |
Уязвимостей на страницу