CVE Catalog

CVE-2026-46257

MediumCVSS 5.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.10%

1th percentile - higher than 1% of all known CVEs

Summary

In the Linux kernel on ARM32 platforms, when SP804 is not registered as sched_clock, read_current_timer() calls sp804_read on an uninitialized sched_clkevt, causing a kernel Oops.

Risk Assessment

A kernel Oops can occur during timer read, leading to system instability or denial of service.

Recommendation

Apply the kernel patch that introduces a dedicated clkevt instance for the delay timer, separate from sched_clock.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS