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-89765

timers/itimer: Zero-init old itimerval before copy to userspace

Description

In the Linux kernel, the following vulnerability has been resolved: timers/itimer: Zero-init old itimerval before copy to userspace On native sparc64, struct __kernel_old_timeval contains a four-byte hole after tv_usec because tv_sec is 64-bit while __kernel_suseconds_t is 32-bit. put_itimerval() fills only the named fields in a stack-allocated __kernel_old_itimerval and copies the entire object to userspace, so getitimer() can expose the two padding holes. Zero-initialize the aggregate before assigning the fields so implicit padding is deterministic before it crosses the user/kernel boundary.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 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.20% · top 90% of all CVEs (12 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 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6d4b937251386d9c6f968e7802f0cb16a8523772
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4ea70146ab9376092297eb8b622ef1792797f2cf
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a17b345daff46fec4af9f1ecbdf350208016dd15
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < bdfda99c5763822a9a888e8af0ad7d9312ffcfe2
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4c66719dd1e4023c5e3f7d050f1bbefec3dfbeb4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2bf5e8f7c9bf4ad3be343a9a6e3e50a34264d25e
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 00ef529a5402f41eb1d227916437e237450719f9
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 18c7d85864e554adc8fad1e8d2e9d2cb6c3911c8
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • 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-89765 badge
[![CVE-2026-89765](https://cveledger.app/badge/CVE-2026-89765.svg)](https://cveledger.app/cve/CVE-2026-89765)

Record last updated .