Количество 29
Количество 29
CVE-2026-46043
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long before payload_size() is used. However, payload_size() subtracts both the attacker-controlled BTH pad field and RXE_ICRC_SIZE from pkt->paylen: payload_size = pkt->paylen - offset[RXE_PAYLOAD] - bth_pad(pkt) - RXE_ICRC_SIZE This means a short packet can still make payload_size() underflow even if it includes enough bytes for the fixed headers. Simply requiring header_size(pkt) + RXE_ICRC_SIZE is not sufficient either, because a packet with a forged non-zero BTH pad can still leave payload_size() negative and pass an underflowed value to later receive-path users. Fix this by validating pkt->paylen against the full minimum length required by payload_size(): header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE.
CVE-2026-46043
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long before payload_size() is used. However, payload_size() subtracts both the attacker-controlled BTH pad field and RXE_ICRC_SIZE from pkt->paylen: payload_size = pkt->paylen - offset[RXE_PAYLOAD] - bth_pad(pkt) - RXE_ICRC_SIZE This means a short packet can still make payload_size() underflow even if it includes enough bytes for the fixed headers. Simply requiring header_size(pkt) + RXE_ICRC_SIZE is not sufficient either, because a packet with a forged non-zero BTH pad can still leave payload_size() negative and pass an underflowed value to later receive-path users. Fix this by validating pkt->paylen against the full minimum length required by payload_size(): header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE.
CVE-2026-46043
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long before payload_size() is used. However, payload_size() subtracts both the attacker-controlled BTH pad field and RXE_ICRC_SIZE from pkt->paylen: payload_size = pkt->paylen - offset[RXE_PAYLOAD] - bth_pad(pkt) - RXE_ICRC_SIZE This means a short packet can still make payload_size() underflow even if it includes enough bytes for the fixed headers. Simply requiring header_size(pkt) + RXE_ICRC_SIZE is not sufficient either, because a packet with a forged non-zero BTH pad can still leave payload_size() negative and pass an underflowed value to later receive-path users. Fix this by validating pkt->paylen against the full minimum length required by payload_size(): header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE.
CVE-2026-46043
RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv
CVE-2026-46043
In the Linux kernel, the following vulnerability has been resolved: R ...
ROS-20261013-73-0177
Уязвимость kernel-lt
GHSA-ww3w-m544-ppj6
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long before payload_size() is used. However, payload_size() subtracts both the attacker-controlled BTH pad field and RXE_ICRC_SIZE from pkt->paylen: payload_size = pkt->paylen - offset[RXE_PAYLOAD] - bth_pad(pkt) - RXE_ICRC_SIZE This means a short packet can still make payload_size() underflow even if it includes enough bytes for the fixed headers. Simply requiring header_size(pkt) + RXE_ICRC_SIZE is not sufficient either, because a packet with a forged non-zero BTH pad can still leave payload_size() negative and pass an underflowed value to later receive-path users. Fix this by validating pkt->paylen against the full minimum length required by payload_size(): header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE.
ELSA-2026-500121
ELSA-2026-500121: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2026:2421-1
Security update for the Linux Kernel
SUSE-SU-2026:2383-1
Security update for the Linux Kernel
RLSA-2026:70402
Important: kernel security, bug fix, and enhancement update
ELSA-2026-70402
ELSA-2026-70402: kernel security, bug fix, and enhancement update (IMPORTANT)
SUSE-SU-2026:2310-1
Security update for the Linux Kernel
RLSA-2026:68570
Important: kernel security, bug fix, and enhancement update
ELSA-2026-68570
ELSA-2026-68570: kernel security, bug fix, and enhancement update (IMPORTANT)
openSUSE-SU-2026:20965-1
Security update for the Linux Kernel
SUSE-SU-2026:2450-1
Security update for the Linux Kernel
SUSE-SU-2026:2591-1
Security update for the Linux Kernel
SUSE-SU-2026:2482-1
Security update for the Linux Kernel
ALT-PU-2026-7515
ALT-PU-2026-7515: package `kernel-image-6.18` update to version 6.18.29-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-46043 In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long before payload_size() is used. However, payload_size() subtracts both the attacker-controlled BTH pad field and RXE_ICRC_SIZE from pkt->paylen: payload_size = pkt->paylen - offset[RXE_PAYLOAD] - bth_pad(pkt) - RXE_ICRC_SIZE This means a short packet can still make payload_size() underflow even if it includes enough bytes for the fixed headers. Simply requiring header_size(pkt) + RXE_ICRC_SIZE is not sufficient either, because a packet with a forged non-zero BTH pad can still leave payload_size() negative and pass an underflowed value to later receive-path users. Fix this by validating pkt->paylen against the full minimum length required by payload_size(): header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE. | CVSS3: 9.1 | 1% Низкий | 5 месяцев назад | |
CVE-2026-46043 In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long before payload_size() is used. However, payload_size() subtracts both the attacker-controlled BTH pad field and RXE_ICRC_SIZE from pkt->paylen: payload_size = pkt->paylen - offset[RXE_PAYLOAD] - bth_pad(pkt) - RXE_ICRC_SIZE This means a short packet can still make payload_size() underflow even if it includes enough bytes for the fixed headers. Simply requiring header_size(pkt) + RXE_ICRC_SIZE is not sufficient either, because a packet with a forged non-zero BTH pad can still leave payload_size() negative and pass an underflowed value to later receive-path users. Fix this by validating pkt->paylen against the full minimum length required by payload_size(): header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE. | CVSS3: 7 | 1% Низкий | 5 месяцев назад | |
CVE-2026-46043 In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long before payload_size() is used. However, payload_size() subtracts both the attacker-controlled BTH pad field and RXE_ICRC_SIZE from pkt->paylen: payload_size = pkt->paylen - offset[RXE_PAYLOAD] - bth_pad(pkt) - RXE_ICRC_SIZE This means a short packet can still make payload_size() underflow even if it includes enough bytes for the fixed headers. Simply requiring header_size(pkt) + RXE_ICRC_SIZE is not sufficient either, because a packet with a forged non-zero BTH pad can still leave payload_size() negative and pass an underflowed value to later receive-path users. Fix this by validating pkt->paylen against the full minimum length required by payload_size(): header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE. | CVSS3: 9.1 | 1% Низкий | 5 месяцев назад | |
CVE-2026-46043 RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv | CVSS3: 7 | 1% Низкий | 5 месяцев назад | |
CVE-2026-46043 In the Linux kernel, the following vulnerability has been resolved: R ... | CVSS3: 9.1 | 1% Низкий | 5 месяцев назад | |
ROS-20261013-73-0177 Уязвимость kernel-lt | CVSS3: 9.1 | 1% Низкий | 1 день назад | |
GHSA-ww3w-m544-ppj6 In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long before payload_size() is used. However, payload_size() subtracts both the attacker-controlled BTH pad field and RXE_ICRC_SIZE from pkt->paylen: payload_size = pkt->paylen - offset[RXE_PAYLOAD] - bth_pad(pkt) - RXE_ICRC_SIZE This means a short packet can still make payload_size() underflow even if it includes enough bytes for the fixed headers. Simply requiring header_size(pkt) + RXE_ICRC_SIZE is not sufficient either, because a packet with a forged non-zero BTH pad can still leave payload_size() negative and pass an underflowed value to later receive-path users. Fix this by validating pkt->paylen against the full minimum length required by payload_size(): header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE. | CVSS3: 9.1 | 1% Низкий | 5 месяцев назад | |
ELSA-2026-500121 ELSA-2026-500121: Unbreakable Enterprise kernel security update (IMPORTANT) | 2 месяца назад | |||
SUSE-SU-2026:2421-1 Security update for the Linux Kernel | 4 месяца назад | |||
SUSE-SU-2026:2383-1 Security update for the Linux Kernel | 4 месяца назад | |||
RLSA-2026:70402 Important: kernel security, bug fix, and enhancement update | 20 дней назад | |||
ELSA-2026-70402 ELSA-2026-70402: kernel security, bug fix, and enhancement update (IMPORTANT) | 13 дней назад | |||
SUSE-SU-2026:2310-1 Security update for the Linux Kernel | 4 месяца назад | |||
RLSA-2026:68570 Important: kernel security, bug fix, and enhancement update | 25 дней назад | |||
ELSA-2026-68570 ELSA-2026-68570: kernel security, bug fix, and enhancement update (IMPORTANT) | 27 дней назад | |||
openSUSE-SU-2026:20965-1 Security update for the Linux Kernel | 4 месяца назад | |||
SUSE-SU-2026:2450-1 Security update for the Linux Kernel | 4 месяца назад | |||
SUSE-SU-2026:2591-1 Security update for the Linux Kernel | 4 месяца назад | |||
SUSE-SU-2026:2482-1 Security update for the Linux Kernel | 4 месяца назад | |||
ALT-PU-2026-7515 ALT-PU-2026-7515: package `kernel-image-6.18` update to version 6.18.29-alt1 | CVSS3: 9.8 | 5 месяцев назад |
Уязвимостей на страницу