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

In the Linux kernel, the following vulnerability has been resolved: binder: signal epoll threads of self-work In (e)poll mode, threads often depend on I/O events to determine when data is ready for consumption. Within binder, a thread may initiate a command via BINDER_WRITE_READ without a read buffer and then make use of epoll_wait() or similar to consume any responses afterwards. It is then crucial that epoll threads are signaled via wakeup when they queue their own work. Otherwise, they risk waiting indefinitely for an event leaving their work unhandled. What is worse, subsequent commands won't trigger a wakeup either as the thread has pending work.

In the Linux kernel, the following vulnerability has been resolved: binder: signal epoll threads of self-work In (e)poll mode, threads often depend on I/O events to determine when data is ready for consumption. Within binder, a thread may initiate a command via BINDER_WRITE_READ without a read buffer and then make use of epoll_wait() or similar to consume any responses afterwards. It is then crucial that epoll threads are signaled via wakeup when they queue their own work. Otherwise, they risk waiting indefinitely for an event leaving their work unhandled. What is worse, subsequent commands won't trigger a wakeup either as the thread has pending work.

In the Linux kernel, the following vulnerability has been resolved: binder: signal epoll threads of self-work In (e)poll mode, threads often depend on I/O events to determine when data is ready for consumption. Within binder, a thread may initiate a command via BINDER_WRITE_READ without a read buffer and then make use of epoll_wait() or similar to consume any responses afterwards. It is then crucial that epoll threads are signaled via wakeup when they queue their own work. Otherwise, they risk waiting indefinitely for an event leaving their work unhandled. What is worse, subsequent commands won't trigger a wakeup either as the thread has pending work.

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

In the Linux kernel, the following vulnerability has been resolved: binder: signal epoll threads of self-work In (e)poll mode, threads often depend on I/O events to determine when data is ready for consumption. Within binder, a thread may initiate a command via BINDER_WRITE_READ without a read buffer and then make use of epoll_wait() or similar to consume any responses afterwards. It is then crucial that epoll threads are signaled via wakeup when they queue their own work. Otherwise, they risk waiting indefinitely for an event leaving their work unhandled. What is worse, subsequent commands won't trigger a wakeup either as the thread has pending work.

Уязвимость функции binder_enqueue_thread_work_ilocked() в модуле drivers/android/binder.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании

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

ALT-PU-2024-2868: package `kernel-image-un-def` update to version 6.1.79-alt1

ALT-PU-2024-18361: package `kernel-image-std-def` update to version 6.1.79-alt1

ALT-PU-2024-3144: package `kernel-image-rt` update to version 6.1.79-alt1.rt25

ALT-PU-2024-18464: package `kernel-image-un-def` update to version 6.6.18-alt1

ALT-PU-2024-18207: package `kernel-image-pine` update to version 6.6.18-alt1

ALT-PU-2024-3273: package `kernel-image-rt` update to version 5.10.210-alt1.rt102

ALT-PU-2024-3457: package `kernel-image-std-def` update to version 5.10.211-alt1

ALT-PU-2024-3415: package `kernel-image-mp` update to version 6.7.8-alt1

ALT-PU-2024-6818: package `kernel-image-rpi-un` update to version 6.6.23-alt1

ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1