CVE-2026-80851

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.12.*, <498386b6d402737db1e2eeed4c385acbf0ef9e34, 0, <=7.1.*, <5f77ddb2756340c1b05381674ca025d52998005e, <b4ac2a5ce5a96ec21ed48f60d30b52b1fb22c62a, 6.6.158, <=6.6.*, <6df4f05bc2991467939d7d80b6f7e121559cc3df, 4.7, <=6.18.*, <=7.2.*, 7.1.13, 6.18.49, <=*, <1e995498d29784a06a2b2899370a1926cfc8410d, <3d950e98f74af9611925a5226edced02155f6ed1, <4.7, 6.12.108, 459aa660eb1d8ce67080da1983bb81d716aa5a69, 7.2.3, 7.3

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.

Gravité et risque d'exploitation

CVE-2026-80851 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.17 %, ce qui la place devant 6.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.12.*, <498386b6d402737db1e2eeed4c385acbf0ef9e34, 0, <=7.1.*, <5f77ddb2756340c1b05381674ca025d52998005e, <b4ac2a5ce5a96ec21ed48f60d30b52b1fb22c62a, 6.6.158, <=6.6.*, <6df4f05bc2991467939d7d80b6f7e121559cc3df, 4.7, <=6.18.*, <=7.2.*, 7.1.13, 6.18.49, <=*, <1e995498d29784a06a2b2899370a1926cfc8410d, <3d950e98f74af9611925a5226edced02155f6ed1, <4.7, 6.12.108, 459aa660eb1d8ce67080da1983bb81d716aa5a69, 7.2.3, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références