Linux
ipv4: validate checksum_start before completing checksum
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= f43798c27684ab925adde7d8acc34c78c6e50df8, < a464d950f31c89565cbaae038cc60db04fe01956
- >= f43798c27684ab925adde7d8acc34c78c6e50df8, < 0fab003ef4698e0628060a45a48f14b43ba2a40a
- >= f43798c27684ab925adde7d8acc34c78c6e50df8, < 94524b7b32691de2e2ce162c04d6cbc9106e5cbf
- >= f43798c27684ab925adde7d8acc34c78c6e50df8, < a65f69e0f38ffbed1b128029e09097436416dc8b
- >= f43798c27684ab925adde7d8acc34c78c6e50df8, < 32a8b0adaa18e52aaa0b246b5ffe683075354dbb
- >= f43798c27684ab925adde7d8acc34c78c6e50df8, < f3e835af6226f1dd12160cbd696081e9b6155de0
- >= f43798c27684ab925adde7d8acc34c78c6e50df8, < c3e33464746166264334641dc850a36eef7e6326
- >= f43798c27684ab925adde7d8acc34c78c6e50df8, < 6785011f8b16abf40b1e9d8b2e332232b3e68822
Fixed in a464d950f31c89565cbaae038cc60db04fe01956, 0fab003ef4698e0628060a45a48f14b43ba2a40a, 94524b7b32691de2e2ce162c04d6cbc9106e5cbf, a65f69e0f38ffbed1b128029e09097436416dc8b, 32a8b0adaa18e52aaa0b246b5ffe683075354dbb, f3e835af6226f1dd12160cbd696081e9b6155de0, c3e33464746166264334641dc850a36eef7e6326, 6785011f8b16abf40b1e9d8b2e332232b3e68822
- 2.6.27
Fixed in 0, 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.57, 7.2.11, 7.3
Mitigation
Upgrade Linux to a464d950f31c89565cbaae038cc60db04fe01956 or 0fab003ef4698e0628060a45a48f14b43ba2a40a or 94524b7b32691de2e2ce162c04d6cbc9106e5cbf or a65f69e0f38ffbed1b128029e09097436416dc8b or 32a8b0adaa18e52aaa0b246b5ffe683075354dbb or f3e835af6226f1dd12160cbd696081e9b6155de0 or c3e33464746166264334641dc850a36eef7e6326 or 6785011f8b16abf40b1e9d8b2e332232b3e68822 or later.
Upgrade Linux to 0 or 5.10.272 or 5.15.223 or 6.1.190 or 6.6.159 or 6.12.113 or 6.18.57 or 7.2.11 or 7.3 or later.
Timeline
Days relative to CVE publicationFirst public PoC 1.8 days after publication; not in CISA KEV. First PoC: PeronGH/CVE-2026-99999 (created 17 Oct 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.9 PoCs · 3 pending · 1 informational · 2 suspicious or fake
PoCs 9
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| PeronGH/CVE-2026-99999 | 17 Oct 2026 +1.8 d | 14 Nov 2026 | 22 | PoC
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| 01luyicheng/CVE-2026-99999 | 18 Oct 2026 +3 d | 14 Nov 2026 | 5 | PoC |
| gandli/CVE-2026-99999-pwnescape | 19 Oct 2026 +3.7 d | 14 Nov 2026 | 2 | PoC
Flags · score 35
Below the suspicion threshold (50); does not change the assessment. |
| shizuku198411/CVE-2026-99999-KVM-checksum-metadata-non-destructive-PoC | 19 Oct 2026 +3.9 d | 14 Nov 2026 | 0 | PoC |
| alvaroguzmancode/CVE-2026-99999 | 19 Oct 2026 +4.1 d | 14 Nov 2026 | 0 | PoC |
| debuman/cve-2026-99999-scanner | 20 Oct 2026 +4.8 d | 14 Nov 2026 | 1 | Scanner
Flags · score 35
Below the suspicion threshold (50); does not change the assessment. |
| 01luyicheng/CVE-2026-99999-analysis | 20 Oct 2026 +4.9 d | 14 Nov 2026 | 0 | PoC |
| 01luyicheng/CVE-2026-99999-exploit | 20 Oct 2026 +4.9 d | 14 Nov 2026 | 0 | PoC |
| unixreaper/CVE-2026-99999-Research | 25 Oct 2026 +9.7 d | 14 Nov 2026 | 0 | PoC via PoC Index
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Pending 3
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| Quaerendir/cve-2026-99999-audit | 17 Oct 2026 +1.9 d | 14 Nov 2026 | 3 | Pending
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| kingahmadr/CVE-2026-99999-kernel-check | 18 Oct 2026 +2.9 d | 14 Nov 2026 | 0 | Pending
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| nsrg-fmlorg/kpatch-cve-2026-98432 | 29 Oct 2026 +14 d | 15 Nov 2026 | 1 | Pending |
Informational 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| MChorfa/csumguard | 16 Oct 2026 +1.2 d | 14 Nov 2026 | 3 | Informational · detection
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
Suspicious or fake 2
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| nsrg-fmlorg/kpatch-alma-cve-2026-99999 | 18 Oct 2026 +2.9 d | 14 Nov 2026 | 0 | Suspicious · score 100
Why suspicious
|
| nsrg-fmlorg/kpatch-rocky-cve-2026-99999 | 19 Oct 2026 +4 d | 14 Nov 2026 | 2 | Suspicious · score 100
Why suspicious
|
Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. Do not run PoC code from unknown sources.