CVE-2026-93219: Linux kernel · clocksource/drivers/timer-sun4i: Advertise a real minimum delta
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f0efafcdf6eec1f3361bfd8c811420198f55c8bb : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:01 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f0efafcdf6eec1f3361bfd8c811420198f55c8bb, ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44, d21808328225ab8cee46885bf9a0dffcefbe630e +5
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. Users should update to a kernel version that includes the fix identified by the provided commit hashes. No additional mitigation is required once the fix is applied.
Description
A vulnerability in the Linux kernel's sun4i timer clocksource driver caused the clockevents core to program zero-tick intervals due to an incorrect advertised minimum delta. This could lead to the next timer event being stuck, resulting in a boot hang on affected hardware such as the Allwinner D1. The issue was fixed by advertising one extra tick as the minimum delta to ensure timer events are scheduled correctly.
References
- git.kernel.org/stable/c/0cc4b14d7401d50e53a01f1554147ee075ee6943 (opens in a new tab)
- git.kernel.org/stable/c/53a3bc024b8e5d284468cce84957cded5f859f98 (opens in a new tab)
- git.kernel.org/stable/c/753a220084dfc4d737f2ab9eaddc9a01a397edd7 (opens in a new tab)
- git.kernel.org/stable/c/ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44 (opens in a new tab)
- git.kernel.org/stable/c/151eb52f8712017c8f7b00bb2305e8916cb9e3dc (opens in a new tab)
- git.kernel.org/stable/c/bf38be01d43c4e4ca903aff7236d8486a950a252 (opens in a new tab)
- git.kernel.org/stable/c/f0efafcdf6eec1f3361bfd8c811420198f55c8bb (opens in a new tab)
- git.kernel.org/stable/c/d21808328225ab8cee46885bf9a0dffcefbe630e (opens in a new tab)