Title: Linux, Description: En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:

clocksource/drivers/timer-sp804: Corregir un Oops cuando se llama a read_current_timer en plataformas ARM32 donde el SP804 no está registrado como el sched_clock.

En SP804, el temporizador de retardo comparte la misma instancia de clkevt con sched_clock. En algunas plataformas, cuando se llama a sp804_clocksource_and_sched_clock_init con use_sched_clock no establecido en 1, sched_clkevt no se inicializa correctamente. Sin embargo, sp804_register_delay_timer se invoca incondicionalmente, y read_current_timer() posteriormente llama a sp804_read en un sched_clkevt no inicializado, lo que lleva a un Oops del kernel al acceder a sched_clkevt->value.

Declarar una instancia de clkevt dedicada exclusivamente para el temporizador de retardo, en lugar de compartir el mismo clkevt con sched_clock. Esto asegura que read_current_timer continúe funcionando correctamente independientemente de si SP804 es seleccionado como el sched_clock.

[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","programFiles":["drivers/clocksource/timer-sp804.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","versions":[{"version":"640594a04f119338019b0aeed70c7301216595b3","lessThan":"693b0b594b0f278bafa784984129c0c0f988e352","versionType":"git","status":"affected"},{"version":"640594a04f119338019b0aeed70c7301216595b3","lessThan":"694921a93f3e3621e067afc545cedf6fe3b234a9","versionType":"git","status":"affected"}]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","programFiles":["drivers/clocksource/timer-sp804.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","versions":[{"version":"6.19","status":"affected"},{"version":"0","lessThan":"6.19","versionType":"semver","status":"unaffected"},{"version":"6.19.4","lessThanOrEqual":"6.19.*","versionType":"semver","status":"unaffected"},{"version":"7.0","lessThanOrEqual":"*","versionType":"original_commit_for_fix","status":"unaffected"}]}]

AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CWE-908

OR
          *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 6.19.4

kernel.org: https://git.kernel.org/stable/c/693b0b594b0f278bafa784984129c0c0f988e352 Types: Patch

kernel.org: https://git.kernel.org/stable/c/694921a93f3e3621e067afc545cedf6fe3b234a9 Types: Patch

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

clocksource/drivers/timer-sp804: Fix an Oops when read_current_timer is called on ARM32 platforms where the SP804 is not registered as the sched_clock.

On SP804, the delay timer shares the same clkevt instance with
sched_clock. On some platforms, when
sp804_clocksource_and_sched_clock_init is called with use_sched_clock
not set to 1, sched_clkevt is not properly initialized. However,
sp804_register_delay_timer is invoked unconditionally, and
read_current_timer() subsequently calls sp804_read on an uninitialized
sched_clkevt, leading to a kernel Oops when accessing
sched_clkevt->value.

Declare a dedicated clkevt instance exclusively for delay timer,
instead of sharing the same clkevt with sched_clock.  This ensures
that read_current_timer continues to work correctly regardless of
whether SP804 is selected as the sched_clock.

https://git.kernel.org/stable/c/693b0b594b0f278bafa784984129c0c0f988e352

https://git.kernel.org/stable/c/694921a93f3e3621e067afc545cedf6fe3b234a9