Поиск уязвимостей

In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix ia_size underflow iattr::ia_size is a loff_t, which is a signed 64-bit type. NFSv3 and NFSv4 both define file size as an unsigned 64-bit type. Thus there is a range of valid file size values an NFS client can send that is already larger than Linux can handle. Currently decode_fattr4() dumps a full u64 value into ia_size. If that value happens to be larger than S64_MAX, then ia_size underflows. I'm about to fix up the NFSv3 behavior as well, so let's catch the underflow in the common code path: nfsd_setattr().

In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix ia_size underflow iattr::ia_size is a loff_t, which is a signed 64-bit type. NFSv3 and NFSv4 both define file size as an unsigned 64-bit type. Thus there is a range of valid file size values an NFS client can send that is already larger than Linux can handle. Currently decode_fattr4() dumps a full u64 value into ia_size. If that value happens to be larger than S64_MAX, then ia_size underflows. I'm about to fix up the NFSv3 behavior as well, so let's catch the underflow in the common code path: nfsd_setattr().

In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix ia_size underflow iattr::ia_size is a loff_t, which is a signed 64-bit type. NFSv3 and NFSv4 both define file size as an unsigned 64-bit type. Thus there is a range of valid file size values an NFS client can send that is already larger than Linux can handle. Currently decode_fattr4() dumps a full u64 value into ia_size. If that value happens to be larger than S64_MAX, then ia_size underflows. I'm about to fix up the NFSv3 behavior as well, so let's catch the underflow in the common code path: nfsd_setattr().

In the Linux kernel, the following vulnerability has been resolved: N ...

In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix ia_size underflow iattr::ia_size is a loff_t, which is a signed 64-bit type. NFSv3 and NFSv4 both define file size as an unsigned 64-bit type. Thus there is a range of valid file size values an NFS client can send that is already larger than Linux can handle. Currently decode_fattr4() dumps a full u64 value into ia_size. If that value happens to be larger than S64_MAX, then ia_size underflows. I'm about to fix up the NFSv3 behavior as well, so let's catch the underflow in the common code path: nfsd_setattr().

Уязвимость компонента NFSD ядра операционной системы Linux, позволяющая нарушителю выполнить произвольный код

ALT-PU-2024-18066: package `kernel-image-std-def` update to version 5.10.220-alt2

Множественные уязвимости kernel-lt

ELSA-2025-20553: Unbreakable Enterprise kernel security update (IMPORTANT)

ALT-PU-2022-1410: package `kernel-image-un-def` update to version 5.15.25-alt1

ALT-PU-2022-1388: package `kernel-image-std-def` update to version 5.15.25-alt1

Security update for the Linux Kernel

ALT-PU-2022-1387: package `kernel-image-un-def` update to version 5.16.11-alt1

Security update for the Linux Kernel

ALT-PU-2024-9973: package `kernel-image-rt` update to version 5.10.221-alt1.rt113

Security update for the Linux Kernel

Security update for the Linux Kernel

ALT-PU-2022-1456: package `kernel-image-mp` update to version 5.16.12-alt1

ALT-PU-2022-1441: package `kernel-image-rpi-un` update to version 5.15.25-alt1

Security update for the Linux Kernel