1. Home
  2. Vulnerabilities
  3. CVE-2026-93219
0.0
NA
CVE-2026-93219
clocksource/drivers/timer-sun4i: Advertise a real minimum delta
Overview
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.

Details
INFO

Published Date :

Sept. 24, 2026, 4:17 p.m.

Last Modified :

Sept. 24, 2026, 4:17 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Impact
Affected Products

The following products are affected by CVE-2026-93219 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Fix timer synchronization delay by advertising a larger minimum event delta.
  • Adjust timer synchronization compensation value.
  • Ensure minimum event delta is at least one hardware tick.
  • Apply kernel updates with the fix.
References
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-93219.

URL Resource
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
https://git.kernel.org/stable/c/d21808328225ab8cee46885bf9a0dffcefbe630e
https://git.kernel.org/stable/c/ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44
https://git.kernel.org/stable/c/f0efafcdf6eec1f3361bfd8c811420198f55c8bb
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-93219 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-93219 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-93219 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2026-93219 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Sep. 24, 2026

    Action Type Old Value New Value
    Added 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.
    Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/93xxx/CVE-2026-93219.json">CVE-2026-93219</a>
    Added Reference https://git.kernel.org/stable/c/0cc4b14d7401d50e53a01f1554147ee075ee6943
    Added Reference https://git.kernel.org/stable/c/151eb52f8712017c8f7b00bb2305e8916cb9e3dc
    Added Reference https://git.kernel.org/stable/c/53a3bc024b8e5d284468cce84957cded5f859f98
    Added Reference https://git.kernel.org/stable/c/753a220084dfc4d737f2ab9eaddc9a01a397edd7
    Added Reference https://git.kernel.org/stable/c/bf38be01d43c4e4ca903aff7236d8486a950a252
    Added Reference https://git.kernel.org/stable/c/d21808328225ab8cee46885bf9a0dffcefbe630e
    Added Reference https://git.kernel.org/stable/c/ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44
    Added Reference https://git.kernel.org/stable/c/f0efafcdf6eec1f3361bfd8c811420198f55c8bb
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CVSS
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.