Waiman Long

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** A issue in the Linux kernel has been identified where the `clocksource verify choose cpus()` function is invoked with preemption disabled, leading to the acquisition of sleeping locks in atomic context. This occurs because `get random u32()` is called to obtain random numbers, which can acquire the `batched entropy 32` local lock and/or the `base crng.lock` spinlock. In PREEMPT RT kernels, these locks are sleeping locks and cannot be acquired in atomic context, resulting in a bug report. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel versions prior to 6.6.50 **Description** A divide-by-0 panic can occur in the `padata mt helper()` function when `ps->chunk size` is 0. This happens when the `min chunk` in the passed-in `padata mt job` structure is 0. The issue is resolved by ensuring that `chunk size` is at least 1, regardless of the input parameters. **Recommendations** To resolve this issue, update the Linux kernel to version 6.6.50 or later. If updating is not possible, ensure that the `chunk size` is set to at least 1 in the `padata do multithreaded()` function to prevent the divide-by-0 panic.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to a NULL pointer dereference in the `pfn section valid()` function. This occurs due to a race condition with `section deactivate()` where `ms->usage` can be cleared. The addition of a `READ ONCE()` call around `ms->usage` is not sufficient to prevent the NULL pointer dereference, and a check of its value before dereferencing is necessary. There is no information provided about the estimated number of potentially affected devices or real-world incidents where this issue was exploited. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.