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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.270, 5.15.221, 6.1.188, 6.12.109, 6.18.50, 6.6.157, 7.2.4
- CVEs
- CVE-2026-93219
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 06:32 UTC · Revision 1
Source evidence
clocksource/drivers/timer-sun4i: Advertise a real minimum delta
core-osv · Original sourcePublished 24 Sept 2026, 15:10 UTC
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.
osv:CVE-2026-93219
Kernel
Fixed versions: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4
Complete source record
{
"id": "dcd0383ab813cc4851fb75e880074b062d67e0a46c855bc046c57bf193e88ed7",
"url": "https://osv.dev/vulnerability/CVE-2026-93219",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "clocksource/drivers/timer-sun4i: Advertise a real minimum delta",
"summary": "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.",
"evidence": "osv:CVE-2026-93219",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.270",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.221",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.188",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.157",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.109",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.50",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-93219",
"aliases": [
"CVE-2026-93219"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "12e1480bcb4920c1b02b3793cb48756497919a60"
},
{
"fixed": "0cc4b14d7401d50e53a01f1554147ee075ee6943"
},
{
"fixed": "53a3bc024b8e5d284468cce84957cded5f859f98"
},
{
"fixed": "753a220084dfc4d737f2ab9eaddc9a01a397edd7"
},
{
"fixed": "ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44"
},
{
"fixed": "151eb52f8712017c8f7b00bb2305e8916cb9e3dc"
},
{
"fixed": "bf38be01d43c4e4ca903aff7236d8486a950a252"
},
{
"fixed": "f0efafcdf6eec1f3361bfd8c811420198f55c8bb"
},
{
"fixed": "d21808328225ab8cee46885bf9a0dffcefbe630e"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-93219.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.13.0"
},
{
"fixed": "5.10.270"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.221"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.188"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.157"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.109"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.50"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-93219.json"
}
}
],
"modified": "2026-10-28T02:30:26.453573929Z",
"provider": "osv",
"references": [
"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",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/93xxx/CVE-2026-93219.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-93219",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/93xxx/CVE-2026-93219.json"
}
},
"related_cves": [
{
"value": "CVE-2026-93219",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 493076,
"published_at": "2026-09-24T15:10:42.9+00:00"
}