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-93146time/namespace: Validate nanosecond field in proc_timens_set_offset()

Description

In the Linux kernel, the following vulnerability has been resolved: time/namespace: Validate nanosecond field in proc_timens_set_offset() The function validates tv_sec to be within [-KTIME_SEC_MAX, KTIME_SEC_MAX] but never validates that tv_nsec is within the valid range of [0, NSEC_PER_SEC-1] before using it in timespec64_add(). timespec64_add() expects both timespec64 structures to have normalized values with tv_nsec in the range [0, 999999999]. If off->val.tv_nsec contains invalid values (negative or >= NSEC_PER_SEC), it could lead to incorrect calculations or unexpected behavior. Add validation to ensure tv_nsec is within the valid range before performing the addition.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 43 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.21% · top 88% 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 04a8682a71becdb639ec9c0d82b315a2baef7a5d – < ce0dd307dfa3193fbf06371b7c819a6bff7d3d68
    • affected 04a8682a71becdb639ec9c0d82b315a2baef7a5d – < 5b8a40de738b7c4896c2edbc6262bd1b3462ded0
    • affected 04a8682a71becdb639ec9c0d82b315a2baef7a5d – < b20d7085ab314672447322c10cc5d1ba443e3b8e
    • affected 04a8682a71becdb639ec9c0d82b315a2baef7a5d – < db667d2970c756cc7b483f45f272440f845a665b
    • affected 04a8682a71becdb639ec9c0d82b315a2baef7a5d – < 1f0c3c0c36c7aedf55a60d9c71c4bd258b8937ce
    • affected 04a8682a71becdb639ec9c0d82b315a2baef7a5d – < 06aba58e58492d2b8eae059274caed29025ea96e
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .