Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93219clocksource/drivers/timer-sun4i: Advertise a real minimum delta

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 25 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 12e1480bcb4920c1b02b3793cb48756497919a60 – < 0cc4b14d7401d50e53a01f1554147ee075ee6943
    • affected 12e1480bcb4920c1b02b3793cb48756497919a60 – < 53a3bc024b8e5d284468cce84957cded5f859f98
    • affected 12e1480bcb4920c1b02b3793cb48756497919a60 – < 753a220084dfc4d737f2ab9eaddc9a01a397edd7
    • affected 12e1480bcb4920c1b02b3793cb48756497919a60 – < ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44
    • affected 12e1480bcb4920c1b02b3793cb48756497919a60 – < 151eb52f8712017c8f7b00bb2305e8916cb9e3dc
    • affected 12e1480bcb4920c1b02b3793cb48756497919a60 – < bf38be01d43c4e4ca903aff7236d8486a950a252
    • affected 12e1480bcb4920c1b02b3793cb48756497919a60 – < f0efafcdf6eec1f3361bfd8c811420198f55c8bb
    • affected 12e1480bcb4920c1b02b3793cb48756497919a60 – < d21808328225ab8cee46885bf9a0dffcefbe630e
  • Linux · Linux

    • affected 3.13
    • unaffected < 3.13
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93219 badge
[![CVE-2026-93219](https://cveledger.app/badge/CVE-2026-93219.svg)](https://cveledger.app/cve/CVE-2026-93219)

Record last updated .