Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 0cc4b14d7401d50e53a01f1554147ee075ee6943, 151eb52f8712017c8f7b00bb2305e8916cb9e3dc, 53a3bc024b8e5d284468cce84957cded5f859f98; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.1-1.

Low priority for now. Upgrade to Linux Linux 0cc4b14d7401d50e53a01f1554147ee075ee6943, 151eb52f8712017c8f7b00bb2305e8916cb9e3dc, 53a3bc024b8e5d284468cce84957cded5f859f98; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 24, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-93219

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.13affected
    • 12e1480bcb4920c1b02b3793cb48756497919a60 and later · before 0cc4b14d7401d50e53a01f1554147ee075ee6943affected · git
    • 12e1480bcb4920c1b02b3793cb48756497919a60 and later · before 53a3bc024b8e5d284468cce84957cded5f859f98affected · git
    • 12e1480bcb4920c1b02b3793cb48756497919a60 and later · before 753a220084dfc4d737f2ab9eaddc9a01a397edd7affected · git
    • 12e1480bcb4920c1b02b3793cb48756497919a60 and later · before ebba4d0aeba0e8eb3a9676380fc2652de8ab1c44affected · git
    • 12e1480bcb4920c1b02b3793cb48756497919a60 and later · before 151eb52f8712017c8f7b00bb2305e8916cb9e3dcaffected · git
    • 12e1480bcb4920c1b02b3793cb48756497919a60 and later · before bf38be01d43c4e4ca903aff7236d8486a950a252affected · git
    • 12e1480bcb4920c1b02b3793cb48756497919a60 and later · before f0efafcdf6eec1f3361bfd8c811420198f55c8bbaffected · git
    • 12e1480bcb4920c1b02b3793cb48756497919a60 and later · before d21808328225ab8cee46885bf9a0dffcefbe630eaffected · git
    • before 3.13not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-93217Sep 24, 2026 · mm/madvise: skip device-private PMDs in cold and pageout walks
    0Monitor
  • ← EarlierCVE-2026-93218Sep 24, 2026 · mm/huge_memory: skip device-private PMDs in madvise_free_huge_pmd
    0Monitor
  • Later →CVE-2026-93220Sep 24, 2026 · sched_ext: Keep kick_sync waiting on the rq's own CPU
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0cc4b14d7401d50e53a01f1554147ee075ee6943Vendor (CNA)
Linux Linux151eb52f8712017c8f7b00bb2305e8916cb9e3dcVendor (CNA)
Linux Linux53a3bc024b8e5d284468cce84957cded5f859f98Vendor (CNA)
Linux Linux753a220084dfc4d737f2ab9eaddc9a01a397edd7Vendor (CNA)
Linux Linuxbf38be01d43c4e4ca903aff7236d8486a950a252Vendor (CNA)
Linux Linuxd21808328225ab8cee46885bf9a0dffcefbe630eVendor (CNA)
Linux Linuxebba4d0aeba0e8eb3a9676380fc2652de8ab1c44Vendor (CNA)
Linux Linuxf0efafcdf6eec1f3361bfd8c811420198f55c8bbVendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records