CVE-2026-93219
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.
- EPSS
- 0.2% chance of exploitation in the next 30 days; higher than 7% of CVEs (scores of 2026-10-25)
- Published
- Modified
- Record from
- the NVD, synced
References
- https://git.kernel.org/stable/c/0cc4b14d7401d50e53a01f1554147ee075ee6943
- https://git.kernel.org/stable/c/151eb52f8712017c8f7b00bb2305e8916cb9e3dc
- https://git.kernel.org/stable/c/53a3bc024b8e5d284468cce84957cded5f859f98
- https://git.kernel.org/stable/c/753a220084dfc4d737f2ab9eaddc9a01a397edd7
- https://git.kernel.org/stable/c/bf38be01d43c4e4ca903aff7236d8486a950a252