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-99999ipv4: validate checksum_start before completing checksum

Description

In the Linux kernel, the following vulnerability has been resolved: ipv4: validate checksum_start before completing checksum If a packet with bad checksum metadata gets into the ipv4 stack, skb_checksum_help can corrupt the network header and cause a bunch of mischief. This was discovered and reported by Paulos, and has been reporoduced by others independently since. We really shouldn't allow such packets in, but as a defence in depth measure, let's also check before we complete the checksum. A more complete validation at input is forthcoming, but needs more work.

Timeline

  1. ID reserved

    By Linux

  2. · 20 days later

    Published

  3. · 9 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

CVSS scores of CVE-2026-99999, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.3CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.3CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.79% · top 43% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected f43798c27684ab925adde7d8acc34c78c6e50df8 – < a464d950f31c89565cbaae038cc60db04fe01956
    • affected f43798c27684ab925adde7d8acc34c78c6e50df8 – < 0fab003ef4698e0628060a45a48f14b43ba2a40a
    • affected f43798c27684ab925adde7d8acc34c78c6e50df8 – < 94524b7b32691de2e2ce162c04d6cbc9106e5cbf
    • affected f43798c27684ab925adde7d8acc34c78c6e50df8 – < a65f69e0f38ffbed1b128029e09097436416dc8b
    • affected f43798c27684ab925adde7d8acc34c78c6e50df8 – < 32a8b0adaa18e52aaa0b246b5ffe683075354dbb
    • affected f43798c27684ab925adde7d8acc34c78c6e50df8 – < f3e835af6226f1dd12160cbd696081e9b6155de0
    • affected f43798c27684ab925adde7d8acc34c78c6e50df8 – < c3e33464746166264334641dc850a36eef7e6326
    • affected f43798c27684ab925adde7d8acc34c78c6e50df8 – < 6785011f8b16abf40b1e9d8b2e332232b3e68822
  • Linux · Linux

    • affected 2.6.27
    • unaffected < 2.6.27
    • unaffected 5.10.272 – ≤ 5.10.*
    • unaffected 5.15.223 – ≤ 5.15.*
    • unaffected 6.1.190 – ≤ 6.1.*
    • unaffected 6.6.159 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .