CVE-2026-93219

clocksource/drivers/timer-sun4i: Advertise a real minimum delta

N/A
Published: September 24, 2026 at 03:10 PM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

12e1480bcb4920c1b02b3793cb48756497919a603.13
Vendor states this is fixed in 0cc4b14d7401d50e53a01f1554147ee075ee6943 (fixed)
Vendor states this is fixed in 151eb52f8712017c8f7b00bb2305e8916cb9e3dc (fixed)
Vendor states this is fixed in 53a3bc024b8e5d284468cce84957cded5f859f98 (fixed)
Vendor states this is fixed in 753a220084dfc4d737f2ab9eaddc9a01a397edd7 (fixed)
Vendor states this is fixed in bf38be01d43c4e4ca903aff7236d8486a950a252 (fixed)
Vendor states this is fixed in d21808328225ab8cee46885bf9a0dffcefbe630e (fixed)
Vendor states this is fixed in ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44 (fixed)
Vendor states this is fixed in f0efafcdf6eec1f3361bfd8c811420198f55c8bb (fixed)
Vendor states this is fixed in 3.13 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card