CVE Catalog

CVE-2026-93219

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, the timer-sun4i clock driver advertises TIMER_SYNC_TICKS as the minimum delta, allowing the clockevents core to call set_next_event() with a value that programs a zero-tick interval. This can leave the next event stuck and cause a boot hang on Allwinner D1.

Risk Assessment

This can prevent system boot on Allwinner D1 platforms, posing an availability risk.

Recommendation

Update the Linux kernel to a version containing the fix that advertises one extra tick as the minimum delta.

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-sun4i: Advertise a real minimum delta sun4i_clkevt_next_event() compensates for the timer stop/start synchronization delay by programming evt - TIMER_SYNC_TICKS into the hardware interval register. The clockevent device currently advertises TIMER_SYNC_TICKS as min_delta_ticks, so the clockevents core is allowed to call set_next_event() with evt == TIMER_SYNC_TICKS. That programs a zero-tick interval. With oneshot/highres/nohz timer operation this can leave the next event stuck, which was observed as a boot hang on Allwinner D1 after the clockevents core started reusing forced minimum-delta events. Advertise one extra tick instead, so the smallest event accepted by the core still programs at least one hardware tick after the synchronization compensation.

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