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

In the Linux kernel, the following vulnerability has been resolved: cpumap: Zero-initialise xdp_rxq_info struct before running XDP program When running an XDP program that is attached to a cpumap entry, we don't initialise the xdp_rxq_info data structure being used in the xdp_buff that backs the XDP program invocation. Tobias noticed that this leads to random values being returned as the xdp_md->rx_queue_index value for XDP programs running in a cpumap. This means we're basically returning the contents of the uninitialised memory, which is bad. Fix this by zero-initialising the rxq data structure before running the XDP program.

In the Linux kernel, the following vulnerability has been resolved: cpumap: Zero-initialise xdp_rxq_info struct before running XDP program When running an XDP program that is attached to a cpumap entry, we don't initialise the xdp_rxq_info data structure being used in the xdp_buff that backs the XDP program invocation. Tobias noticed that this leads to random values being returned as the xdp_md->rx_queue_index value for XDP programs running in a cpumap. This means we're basically returning the contents of the uninitialised memory, which is bad. Fix this by zero-initialising the rxq data structure before running the XDP program.

In the Linux kernel, the following vulnerability has been resolved: cpumap: Zero-initialise xdp_rxq_info struct before running XDP program When running an XDP program that is attached to a cpumap entry, we don't initialise the xdp_rxq_info data structure being used in the xdp_buff that backs the XDP program invocation. Tobias noticed that this leads to random values being returned as the xdp_md->rx_queue_index value for XDP programs running in a cpumap. This means we're basically returning the contents of the uninitialised memory, which is bad. Fix this by zero-initialising the rxq data structure before running the XDP program.

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

In the Linux kernel, the following vulnerability has been resolved: cpumap: Zero-initialise xdp_rxq_info struct before running XDP program When running an XDP program that is attached to a cpumap entry, we don't initialise the xdp_rxq_info data structure being used in the xdp_buff that backs the XDP program invocation. Tobias noticed that this leads to random values being returned as the xdp_md->rx_queue_index value for XDP programs running in a cpumap. This means we're basically returning the contents of the uninitialised memory, which is bad. Fix this by zero-initialising the rxq data structure before running the XDP program.

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

ALT-PU-2024-18076: package `kernel-image-rt` update to version 5.10.213-alt1.rt105

ALT-PU-2024-17586: package `kernel-image-std-def` update to version 5.10.213-alt1

ALT-PU-2024-18468: package `kernel-image-un-def` update to version 6.6.22-alt1

ALT-PU-2024-18210: package `kernel-image-pine` update to version 6.6.22-alt1

ALT-PU-2024-18364: package `kernel-image-std-def` update to version 6.1.82-alt1

ALT-PU-2024-18057: package `kernel-image-un-def` update to version 6.1.82-alt1

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

ALT-PU-2024-18256: package `kernel-image-rt` update to version 6.1.82-alt1.rt27

Security update for the Linux Kernel

Security update for the Linux Kernel

ELSA-2024-9315: kernel security update (MODERATE)

Security update for the Linux Kernel

Security update for the Linux Kernel

ALT-PU-2024-18117: package `kernel-image-mp` update to version 6.7.12-alt1