CVE-2026-93219 — clocksource/drivers/timer-sun4i: Advertise a real minimum delta
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 12e1480bcb4920c1b02b3793cb48756497919a60 and < 0cc4b14d7401d50e53a01f1554147ee075ee6943≥ 12e1480bcb4920c1b02b3793cb48756497919a60 and < 53a3bc024b8e5d284468cce84957cded5f859f98≥ 12e1480bcb4920c1b02b3793cb48756497919a60 and < 753a220084dfc4d737f2ab9eaddc9a01a397edd7≥ 12e1480bcb4920c1b02b3793cb48756497919a60 and < ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44≥ 12e1480bcb4920c1b02b3793cb48756497919a60 and < 151eb52f8712017c8f7b00bb2305e8916cb9e3dc≥ 12e1480bcb4920c1b02b3793cb48756497919a60 and < bf38be01d43c4e4ca903aff7236d8486a950a252≥ 12e1480bcb4920c1b02b3793cb48756497919a60 and < f0efafcdf6eec1f3361bfd8c811420198f55c8bb≥ 12e1480bcb4920c1b02b3793cb48756497919a60 and < d21808328225ab8cee46885bf9a0dffcefbe630e and 1 moreversion 3.13 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/f0efafcdf6eec1f3361bfd8c811420198f55c8bb
- git.kernel.org/stable/c/ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44
- git.kernel.org/stable/c/753a220084dfc4d737f2ab9eaddc9a01a397edd7
- git.kernel.org/stable/c/53a3bc024b8e5d284468cce84957cded5f859f98
- git.kernel.org/stable/c/d21808328225ab8cee46885bf9a0dffcefbe630e
- git.kernel.org/stable/c/bf38be01d43c4e4ca903aff7236d8486a950a252
- git.kernel.org/stable/c/151eb52f8712017c8f7b00bb2305e8916cb9e3dc
- git.kernel.org/stable/c/0cc4b14d7401d50e53a01f1554147ee075ee6943
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 2d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 2d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 3d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 3d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 3d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-93219 is "clocksource/drivers/timer-sun4i: Advertise a real minimum delta", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.