CVE-2026-80851

gtp: serialize PDP context updates

N/A
Published: September 4, 2026 at 03:55 PM UTC
Updated: October 30, 2026 at 01:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: gtp: serialize PDP context updates PDP contexts can be deleted through GTP_CMD_DELPDP or while the GTP network device is being unregistered. The latter is serialized by RTNL, but the generic-netlink delete path only holds RCU. Running both paths concurrently can therefore make both paths delete the same PDP context. The issue was found through static analysis and reproduced on a KASAN-enabled kernel by a simple two-thread program racing GTP_CMD_DELPDP against RTM_DELLINK: Oops: general protection fault, probably for non-canonical address KASAN: maybe wild-memory-access in range [0xdead000000000120-0xdead000000000127] RIP: gtp_genl_del_pdp+0x1c1/0x420 [gtp] RBP: dead000000000122 The second deletion dereferenced the poisoned hlist pprev pointer. Serialize gtp_pdp_add(), gtp_genl_del_pdp(), and gtp_dellink() with a shared mutex. Keep the mutex held until the final use of a PDP context in the NEWPDP path, and keep the RCU read-side section around the complete PDP context use in the DELPDP path.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.7459aa660eb1d8ce67080da1983bb81d716aa5a69
Vendor states this is fixed in 1e995498d29784a06a2b2899370a1926cfc8410d (fixed)
Vendor states this is fixed in 3d950e98f74af9611925a5226edced02155f6ed1 (fixed)
Vendor states this is fixed in 498386b6d402737db1e2eeed4c385acbf0ef9e34 (fixed)
Vendor states this is fixed in 5f77ddb2756340c1b05381674ca025d52998005e (fixed)
Vendor states this is fixed in 6df4f05bc2991467939d7d80b6f7e121559cc3df (fixed)
Vendor states this is fixed in b4ac2a5ce5a96ec21ed48f60d30b52b1fb22c62a (fixed)
Vendor states this is fixed in 4.7 (unaffected)
Vendor states this is fixed in 6.12.108 (unaffected)
Vendor states this is fixed in 6.18.49 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.1.13 (unaffected)
Vendor states this is fixed in 7.2.3 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card