In the Linux kernel, the following vulnerability has been resolved:
clocksource/drivers/timer-sp804: Fix an Oops when readcurrenttimer 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 schedclock. On some platforms, when sp804clocksourceandschedclockinit is called with useschedclock not set to 1, schedclkevt is not properly initialized. However, sp804registerdelaytimer is invoked unconditionally, and readcurrenttimer() subsequently calls sp804read on an uninitialized schedclkevt, 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 schedclock. This ensures that readcurrenttimer continues to work correctly regardless of whether SP804 is selected as the schedclock.
{
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46257.json"
}