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

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.4$5k-$25k4.33+

Summaryinfo

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.

Detailsinfo

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.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.7
VulDB 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): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Stack-based overflow
CWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Timelineinfo

09/25/2026 CVE reserved
10/15/2026 +20 days Advisory disclosed
10/15/2026 +0 days VulDB entry created
10/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-99999 (🔒)
GCVE (CVE): GCVE-0-2026-99999
GCVE (VulDB): GCVE-100-420626

Entryinfo

Created: 10/15/2026 15:00
Changes: 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.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!