Linux Kernel up to 7.2.2 xfrm handle_esp null pointer dereference

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.
7.2$0-$5k0.41-

Summaryinfo

A vulnerability identified as critical has been detected in Linux Kernel up to 7.2.2. Impacted is the function handle_esp of the component xfrm. This manipulation causes null pointer dereference. This vulnerability appears as CVE-2026-80846. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 7.2.2. Affected by this vulnerability is the function handle_esp of the component xfrm. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: xfrm: drop ESP-in-TCP packets with no ingress device ESP-in-TCP receives records through the TCP strparser. handle_esp() restores skb->dev from the saved skb_iif before passing the packet into the XFRM input path. Queued TCP data can be processed after the original ingress device has been removed, for example during veth or net namespace teardown. In that case dev_get_by_index_rcu() returns NULL. The XFRM IPv4 and IPv6 input paths both expect skb->dev to be valid while building the route lookup, so queued ESP-in-TCP data can dereference a NULL device. Drop the packet if the saved ingress device can no longer be resolved. Such a packet can no longer be routed through the normal XFRM receive path, and this preserves the existing behaviour for packets whose ingress device still exists.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-80846 since 08/26/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/04/2026).

Upgrading to version 5.10.269, 5.15.220, 6.1.187, 6.6.156, 6.12.108, 6.18.49, 7.1.13, 7.2.3 or 7.3-rc1 eliminates this vulnerability. Applying the patch 239d0f71af09dc2029fd4d730cb24b8c83aaa43a/f00235f9d12301183d61f75fbe4105506f3e5140/6af5cdb03819a5ce6e945992635c6c5e91045367/2dd1609cadff46c4b20ce53b91ab9cce1380456a/c296d25efbc840be24de83f56d43bc47e714ace9/328e40aa774b446969c69b654c52a051a95af8a1/7911e0236616487b89db6bd3ba3f408abd10eb23/943d95233b8b4a88994e244fcf466f8c403d63f1/e1d7c5ac1c246ce5775f604515de0a59fbf2116e is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 7.2

VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
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.269/5.15.220/6.1.187/6.6.156/6.12.108/6.18.49/7.1.13/7.2.3/7.3-rc1
Patch: 239d0f71af09dc2029fd4d730cb24b8c83aaa43a/f00235f9d12301183d61f75fbe4105506f3e5140/6af5cdb03819a5ce6e945992635c6c5e91045367/2dd1609cadff46c4b20ce53b91ab9cce1380456a/c296d25efbc840be24de83f56d43bc47e714ace9/328e40aa774b446969c69b654c52a051a95af8a1/7911e0236616487b89db6bd3ba3f408abd10eb23/943d95233b8b4a88994e244fcf466f8c403d63f1/e1d7c5ac1c246ce5775f604515de0a59fbf2116e

Timelineinfo

08/26/2026 CVE reserved
09/04/2026 +9 days Advisory disclosed
09/04/2026 +0 days VulDB entry created
09/04/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80846 (🔒)
GCVE (CVE): GCVE-0-2026-80846
GCVE (VulDB): GCVE-100-398953

Entryinfo

Created: 09/04/2026 18:31
Changes: 09/04/2026 18:31 (59)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!