gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 459aa660eb1d8ce67080da1983bb81d716aa5a69 · < 7677eb2cbf2cc7446de474c01a6b06277c0051e5| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel’s GTP newlink error path can free hash tables before a concurrent packet-receive operation has finished using them. If that error path overlaps with GTP packet reception, the receive operation may access freed memory. The input does not establish authentication or user-interaction requirements.
Engineers running Linux kernels with GTP support should check their kernel versions against the vendor advisory; affected versions were not provided.