CVE-2026-80851

UnknownEPSS 0.17%

Last modified

CVE-2026-80851 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.17%

6.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 459aa660eb1d8ce67080da1983bb81d716aa5a69, < d8ebf8875fb97b3e39aa226af78f9c619e96ee31; >= 459aa660eb1d8ce67080da1983bb81d716aa5a69, < 6e5472c1c1619793cbadb02bccf7d2d9f826052f; >= 459aa660eb1d8ce67080da1983bb81d716aa5a69, < d9a83492ffc99f228d91873473e3820300525f00; >= 459aa660eb1d8ce67080da1983bb81d716aa5a69, < b4ac2a5ce5a96ec21ed48f60d30b52b1fb22c62a; >= 459aa660eb1d8ce67080da1983bb81d716aa5a69, < 5f77ddb2756340c1b05381674ca025d52998005e; >= 459aa660eb1d8ce67080da1983bb81d716aa5a69, < 3d950e98f74af9611925a5226edced02155f6ed1; >= 459aa660eb1d8ce67080da1983bb81d716aa5a69, < 6df4f05bc2991467939d7d80b6f7e121559cc3df; >= 459aa660eb1d8ce67080da1983bb81d716aa5a69, < 1e995498d29784a06a2b2899370a1926cfc8410d; >= 459aa660eb1d8ce67080da1983bb81d716aa5a69, < 498386b6d402737db1e2eeed4c385acbf0ef9e34
LinuxLinux4.7

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80851?
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.
How severe is CVE-2026-80851?
Severity scoring for CVE-2026-80851 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-80851?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-80851?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST