Strix
64.5K

CVE-2026-93219

Unknown

Last modified

CVE-2026-93219 is a vulnerability of currently unknown severity. 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.

Description

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 12e1480bcb4920c1b02b3793cb48756497919a60, < 0cc4b14d7401d50e53a01f1554147ee075ee6943; >= 12e1480bcb4920c1b02b3793cb48756497919a60, < 53a3bc024b8e5d284468cce84957cded5f859f98; >= 12e1480bcb4920c1b02b3793cb48756497919a60, < 753a220084dfc4d737f2ab9eaddc9a01a397edd7; >= 12e1480bcb4920c1b02b3793cb48756497919a60, < ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44; >= 12e1480bcb4920c1b02b3793cb48756497919a60, < 151eb52f8712017c8f7b00bb2305e8916cb9e3dc; >= 12e1480bcb4920c1b02b3793cb48756497919a60, < bf38be01d43c4e4ca903aff7236d8486a950a252; >= 12e1480bcb4920c1b02b3793cb48756497919a60, < f0efafcdf6eec1f3361bfd8c811420198f55c8bb; >= 12e1480bcb4920c1b02b3793cb48756497919a60, < d21808328225ab8cee46885bf9a0dffcefbe630e
LinuxLinux3.13

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is 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.
How severe is CVE-2026-93219?
Severity scoring for CVE-2026-93219 is pending analysis.
How do I fix CVE-2026-93219?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-93219?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST