CVE-2026-99999
Last modified
CVE-2026-99999 is a critical-severity vulnerability rated 9.3/10 on the CVSS scale. 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.. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= f43798c27684ab925adde7d8acc34c78c6e50df8, < a464d950f31c89565cbaae038cc60db04fe01956; >= f43798c27684ab925adde7d8acc34c78c6e50df8, < 0fab003ef4698e0628060a45a48f14b43ba2a40a; >= f43798c27684ab925adde7d8acc34c78c6e50df8, < 94524b7b32691de2e2ce162c04d6cbc9106e5cbf; >= f43798c27684ab925adde7d8acc34c78c6e50df8, < a65f69e0f38ffbed1b128029e09097436416dc8b; >= f43798c27684ab925adde7d8acc34c78c6e50df8, < 32a8b0adaa18e52aaa0b246b5ffe683075354dbb; >= f43798c27684ab925adde7d8acc34c78c6e50df8, < f3e835af6226f1dd12160cbd696081e9b6155de0; >= f43798c27684ab925adde7d8acc34c78c6e50df8, < c3e33464746166264334641dc850a36eef7e6326; >= f43798c27684ab925adde7d8acc34c78c6e50df8, < 6785011f8b16abf40b1e9d8b2e332232b3e68822 |
| Linux | Linux | 2.6.27 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-99999?
How severe is CVE-2026-99999?
How do I fix CVE-2026-99999?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-9994Use after free in Core in Google Chrome on Windows prior to …8.3
- CVE-2026-9995Use after free in WebXR in Google Chrome prior to 148.0.7778…8.8
- CVE-2026-9996Out of bounds read in WebRTC in Google Chrome on Mac prior t…6.5
- CVE-2026-9997Use after free in Input in Google Chrome prior to 148.0.7778…8.3
- CVE-2026-9998Integer overflow in Skia in Google Chrome prior to 148.0.777…8.3
- CVE-2026-9999Inappropriate implementation in ANGLE in Google Chrome on Ma…8.8
Are you affected by CVE-2026-99999?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
