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

In the Linux kernel, the following vulnerability has been resolved: libbpf: Handle size overflow for ringbuf mmap The maximum size of ringbuf is 2GB on x86-64 host, so 2 * max_entries will overflow u32 when mapping producer page and data pages. Only casting max_entries to size_t is not enough, because for 32-bits application on 64-bits kernel the size of read-only mmap region also could overflow size_t. So fixing it by casting the size of read-only mmap region into a __u64 and checking whether or not there will be overflow during mmap.

In the Linux kernel, the following vulnerability has been resolved: libbpf: Handle size overflow for ringbuf mmap The maximum size of ringbuf is 2GB on x86-64 host, so 2 * max_entries will overflow u32 when mapping producer page and data pages. Only casting max_entries to size_t is not enough, because for 32-bits application on 64-bits kernel the size of read-only mmap region also could overflow size_t. So fixing it by casting the size of read-only mmap region into a __u64 and checking whether or not there will be overflow during mmap.

In the Linux kernel, the following vulnerability has been resolved: libbpf: Handle size overflow for ringbuf mmap The maximum size of ringbuf is 2GB on x86-64 host, so 2 * max_entries will overflow u32 when mapping producer page and data pages. Only casting max_entries to size_t is not enough, because for 32-bits application on 64-bits kernel the size of read-only mmap region also could overflow size_t. So fixing it by casting the size of read-only mmap region into a __u64 and checking whether or not there will be overflow during mmap.

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

In the Linux kernel, the following vulnerability has been resolved: libbpf: Handle size overflow for ringbuf mmap The maximum size of ringbuf is 2GB on x86-64 host, so 2 * max_entries will overflow u32 when mapping producer page and data pages. Only casting max_entries to size_t is not enough, because for 32-bits application on 64-bits kernel the size of read-only mmap region also could overflow size_t. So fixing it by casting the size of read-only mmap region into a __u64 and checking whether or not there will be overflow during mmap.

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

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

ALT-PU-2022-7765: package `kernel-image-std-kvm` update to version 5.10.158-alt1

ALT-PU-2022-7817: package `kernel-image-std-def` update to version 5.15.82-alt1

ALT-PU-2022-3306: package `kernel-image-un-def` update to version 6.0.12-alt1

ALT-PU-2022-3311: package `kernel-image-rt` update to version 5.10.158-alt1.rt77

ALT-PU-2022-3310: package `kernel-image-rt` update to version 5.10.158-alt1.rt77

ALT-PU-2022-3303: package `kernel-image-mp` update to version 6.0.12-alt1

ALT-PU-2023-1066: package `kernel-image-std-def` update to version 5.10.163-alt1

ALT-PU-2023-1044: package `kernel-image-un-def` update to version 5.15.87-alt1

ALT-PU-2022-3371: package `kernel-image-rpi-un` update to version 6.1.0-alt1

ALT-PU-2022-3364: package `kernel-image-rpi-un` update to version 6.1.0-alt1

ALT-PU-2023-7682: package `kernel-image-rpi-def` update to version 5.15.92-alt2

ALT-PU-2023-7007: package `kernel-image-rpi-def` update to version 5.15.92-alt1