CVE-2023-52986: bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener
Vulnerability summary
CVE-2023-52986 is a medium (CVSS 5.5) Uncontrolled Recursion vulnerability in linux. EPSS estimates a 0.28% chance of exploitation in the next 30 days, higher than 20.6% of scored vulnerabilities.
Not severe (CVSS 5.5, local access); no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 3 · Related 2Timeline
- 27-03-2025PublishedVulnerability first disclosed.
- 11-05-2026Last modifiedVulnerability information updated.
Description
In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener A listening socket linked to a sockmap has its sk_prot overridden. It points to one of the struct proto variants in tcp_bpf_prots. The variant depends on the socket's family and which sockmap programs are attached. A child socket cloned from a TCP listener initially inherits their sk_prot. But before cloning is finished, we restore the child's proto to the listener's original non-tcp_bpf_prots one. This happens in tcp_create_openreq_child -> tcp_bpf_clone. Today, in tcp_bpf_clone we detect if the child's proto should be restored by checking only for the TCP_BPF_BASE proto variant. This is not correct. The sk_prot of listening socket linked to a sockmap can point to to any variant in tcp_bpf_prots. If the listeners sk_prot happens to be not the TCP_BPF_BASE variant, then the child socket unintentionally is left if the inherited sk_prot by tcp_bpf_clone. This leads to issues like infinite recursion on close [1], because the child state is otherwise not set up for use with tcp_bpf_prot operations. Adjust the check in tcp_bpf_clone to detect all of tcp_bpf_prots variants. Note that it wouldn't be sufficient to check the socket state when overriding the sk_prot in tcp_bpf_update_proto in order to always use the TCP_BPF_BASE variant for listening sockets. Since commit b8b8315e39ff ("bpf, sockmap: Remove unhash handler for BPF sockmap usage") it is possible for a socket to transition to TCP_LISTEN state while already linked to a sockmap, e.g. connect() -> insert into map -> connect(AF_UNSPEC) -> listen(). [1]: https://lore.kernel.org/all/00000000000073b14905ef2e7401@google.com/
CVSS metrics
3 scores · 3 sources · 1 version- OSV · UbuntuEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- OSV · DebianEcosystem advisory · calculated5.5MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS trend
Probability
0.28%
Chance of exploitation in the next 30 days
Percentile
21%
Versus all other CVEs
30-day change
No change 0.00 pp
From 0.28% on 04-10-2026
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeAffected systems
Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.
Ubuntu96 products
- linux< 5.15.0-72.79
- linux-allwinner-5.19All versions (No fix recorded)
- linux-aws< 5.15.0-1036.40
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Linux2 products
- linux≥ e80251555f0befd1271e74b080bccf0ff0348bfc, < 9bd6074e1872d22190a8da30e796cbf937d334f0 | ≥ e80251555f0befd1271e74b080bccf0ff0348bfc, < c681d7a4ed3d360de0574f4d6b7305a8de8dc54f | ≥ e80251555f0befd1271e74b080bccf0ff0348bfc, < 12b0ec7c6953e1602957926439e5297095d7d065 | ≥ e80251555f0befd1271e74b080bccf0ff0348bfc, < ddce1e091757d0259107c6c0c7262df201de2b66 | 5.7
- linux_kernel≥ 5.7, < 5.10.168 | ≥ 5.11, < 5.15.93 | ≥ 5.16, < 6.1.11 | 6.2:rc1 | 6.2:rc2 | 6.2:rc3 | 6.2:rc4 | 6.2:rc5 | 6.2:rc6
Debian1 product
- linux< 6.1.11-1
3 vendors · 99 products