CVE-2026-89789 — gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free
In the Linux kernel, the following vulnerability has been resolved: gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free gtp_newlink()'s error path frees tid_hash and addr_hash without waiting for an RCU grace period after clearing sk_user_data. A concurrent gtp_encap_recv() in softirq may still hold the gtp_dev pointer obtained via rcu_dereference_sk_user_data() and access the freed memory. BUG: KASAN: slab-use-after-free in gtp0_pdp_find+0x1f6/0x200 (gtp.c:152) Call Trace: <IRQ> gtp0_pdp_find+0x1f6/0x200 gtp_encap_recv+0x527/0x24b0 udp_queue_rcv_one_skb+0x75f/0xc10 Add synchronize_net() before the kfree calls in out_hashtable, which covers all error paths from both gtp_encap_enable() and gtp_create_sockets().
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 459aa660eb1d8ce67080da1983bb81d716aa5a69 and < fcafb2b1430824bae4258c01a439ec97ca0c6973≥ 459aa660eb1d8ce67080da1983bb81d716aa5a69 and < 3ca3da5c305caa873ddb81e8c6b118143f6dd3d1≥ 459aa660eb1d8ce67080da1983bb81d716aa5a69 and < 6f815c2fb6ab20385f81c353cdad0ea3b88132af≥ 459aa660eb1d8ce67080da1983bb81d716aa5a69 and < e3b9aa0773abd5d4ed90be41ce5306c146d5b09e≥ 459aa660eb1d8ce67080da1983bb81d716aa5a69 and < fd8396cfecbd904468c71362f08aaa25f96d5337≥ 459aa660eb1d8ce67080da1983bb81d716aa5a69 and < 7677eb2cbf2cc7446de474c01a6b06277c0051e5≥ 459aa660eb1d8ce67080da1983bb81d716aa5a69 and < 8d85498016a5bb56339734a14c276209fa65bafc≥ 459aa660eb1d8ce67080da1983bb81d716aa5a69 and < d989e22ae9802c52c56ad4284d0caf26696cf6ae and 1 moreversion 4.7 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/3ca3da5c305caa873ddb81e8c6b118143f6dd3d1
- git.kernel.org/stable/c/d989e22ae9802c52c56ad4284d0caf26696cf6ae
- git.kernel.org/stable/c/fd8396cfecbd904468c71362f08aaa25f96d5337
- git.kernel.org/stable/c/8d85498016a5bb56339734a14c276209fa65bafc
- git.kernel.org/stable/c/6f815c2fb6ab20385f81c353cdad0ea3b88132af
- git.kernel.org/stable/c/7677eb2cbf2cc7446de474c01a6b06277c0051e5
- git.kernel.org/stable/c/e3b9aa0773abd5d4ed90be41ce5306c146d5b09e
- git.kernel.org/stable/c/fcafb2b1430824bae4258c01a439ec97ca0c6973
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-89789 is "gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.