Linux Kernel up to 7.2.3 timer-sun4i driver drivers/timer-sun4i.c sun4i_clkevt_next_event improper synchronization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.2.3. It has been classified as critical. This impacts the function sun4i_clkevt_next_event of the file drivers/timer-sun4i.c of the component timer-sun4i driver. Performing a manipulation results in improper synchronization. This vulnerability is reported as CVE-2026-93219. The attack requires a local approach. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.2.3. It has been classified as critical. This affects the function sun4i_clkevt_next_event of the file drivers/timer-sun4i.c of the component timer-sun4i driver. The manipulation with an unknown input leads to a improper synchronization vulnerability. CWE is classifying the issue as CWE-662. The product utilizes multiple threads or processes to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes. This is going to have an impact on availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-93219 since 09/17/2026. The exploitability is told to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4 or 7.3-rc1 eliminates this vulnerability. Applying the patch 0cc4b14d7401d50e53a01f1554147ee075ee6943/53a3bc024b8e5d284468cce84957cded5f859f98/753a220084dfc4d737f2ab9eaddc9a01a397edd7/ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44/151eb52f8712017c8f7b00bb2305e8916cb9e3dc/bf38be01d43c4e4ca903aff7236d8486a950a252/f0efafcdf6eec1f3361bfd8c811420198f55c8bb/d21808328225ab8cee46885bf9a0dffcefbe630e is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Improper synchronization
CWE: CWE-662
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.270/5.15.221/6.1.188/6.6.157/6.12.109/6.18.50/7.2.4/7.3-rc1
Patch: 0cc4b14d7401d50e53a01f1554147ee075ee6943/53a3bc024b8e5d284468cce84957cded5f859f98/753a220084dfc4d737f2ab9eaddc9a01a397edd7/ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44/151eb52f8712017c8f7b00bb2305e8916cb9e3dc/bf38be01d43c4e4ca903aff7236d8486a950a252/f0efafcdf6eec1f3361bfd8c811420198f55c8bb/d21808328225ab8cee46885bf9a0dffcefbe630e

Timelineinfo

09/17/2026 CVE reserved
09/24/2026 +7 days Advisory disclosed
09/24/2026 +0 days VulDB entry created
09/24/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-93219 (🔒)
GCVE (CVE): GCVE-0-2026-93219
GCVE (VulDB): GCVE-100-409407

Entryinfo

Created: 09/24/2026 17:38
Changes: 09/24/2026 17:38 (60)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!