Linux Kernel up to 7.3-rc6 ipv4 skb_checksum_help stack-based overflow

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.4 | $5k-$25k | 4.33+ |
Summary
A vulnerability labeled as very critical has been found in Linux Kernel up to 7.3-rc6. This affects the function skb_checksum_help of the component ipv4. Such manipulation leads to stack-based overflow.
This vulnerability is documented as CVE-2026-99999. The attack can be executed remotely. There is not any exploit available.
The affected component should be upgraded.
Details
A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 7.3-rc6. Affected by this issue is the function skb_checksum_help of the component ipv4. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-99999 since 09/25/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 10/15/2026).
Upgrading to version 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.57, 7.2.11 or 7.3-rc7 eliminates this vulnerability. Applying the patch a464d950f31c89565cbaae038cc60db04fe01956/0fab003ef4698e0628060a45a48f14b43ba2a40a/94524b7b32691de2e2ce162c04d6cbc9106e5cbf/a65f69e0f38ffbed1b128029e09097436416dc8b/32a8b0adaa18e52aaa0b246b5ffe683075354dbb/f3e835af6226f1dd12160cbd696081e9b6155de0/c3e33464746166264334641dc850a36eef7e6326/6785011f8b16abf40b1e9d8b2e332232b3e68822 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 5.10.271
- 5.15.222
- 6.1.189
- 6.6.158
- 6.12.112
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 6.18.45
- 6.18.46
- 6.18.47
- 6.18.48
- 6.18.49
- 6.18.50
- 6.18.51
- 6.18.52
- 6.18.53
- 6.18.54
- 6.18.55
- 6.18.56
- 7.2.0
- 7.2.1
- 7.2.2
- 7.2.3
- 7.2.4
- 7.2.5
- 7.2.6
- 7.2.7
- 7.2.8
- 7.2.9
- 7.2.10
- 7.3-rc1
- 7.3-rc2
- 7.3-rc3
- 7.3-rc4
- 7.3-rc5
- 7.3-rc6
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.7VulDB Meta Temp Score: 9.4
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.3
CNA Vector (Linux): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.272/5.15.223/6.1.190/6.6.159/6.12.113/6.18.57/7.2.11/7.3-rc7
Patch: a464d950f31c89565cbaae038cc60db04fe01956/0fab003ef4698e0628060a45a48f14b43ba2a40a/94524b7b32691de2e2ce162c04d6cbc9106e5cbf/a65f69e0f38ffbed1b128029e09097436416dc8b/32a8b0adaa18e52aaa0b246b5ffe683075354dbb/f3e835af6226f1dd12160cbd696081e9b6155de0/c3e33464746166264334641dc850a36eef7e6326/6785011f8b16abf40b1e9d8b2e332232b3e68822
Timeline
09/25/2026 CVE reserved10/15/2026 Advisory disclosed
10/15/2026 VulDB entry created
10/15/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-99999 (🔒)
GCVE (CVE): GCVE-0-2026-99999
GCVE (VulDB): GCVE-100-420626
Entry
Created: 10/15/2026 15:00Changes: 10/15/2026 15:00 (68)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.