CVE-2023-52986: bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 12b0ec7c6953e1602957926439e5297095d7d065, 9bd6074e1872d22190a8da30e796cbf937d334f0, c681d7a4ed3d360de0574f4d6b7305a8de8dc54f.
Low priority for now. Upgrade to Linux Linux 12b0ec7c6953e1602957926439e5297095d7d065, 9bd6074e1872d22190a8da30e796cbf937d334f0, c681d7a4ed3d360de0574f4d6b7305a8de8dc54f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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/
- Published
- Mar 27, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-674
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.7 and later · before 5.10.168
- linux linux kernel5.11 and later · before 5.15.93
- linux linux kernel5.16 and later · before 6.1.11
- linux linux kernel6.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.7affected
- e80251555f0befd1271e74b080bccf0ff0348bfc and later · before 9bd6074e1872d22190a8da30e796cbf937d334f0affected · git
- e80251555f0befd1271e74b080bccf0ff0348bfc and later · before c681d7a4ed3d360de0574f4d6b7305a8de8dc54faffected · git
- e80251555f0befd1271e74b080bccf0ff0348bfc and later · before 12b0ec7c6953e1602957926439e5297095d7d065affected · git
- e80251555f0befd1271e74b080bccf0ff0348bfc and later · before ddce1e091757d0259107c6c0c7262df201de2b66affected · git
- before 5.7not affected · semver
- 5.10.168 and later · up to and including 5.10.*not affected · semver
- 5.15.93 and later · up to and including 5.15.*not affected · semver
- 6.1.11 and later · up to and including 6.1.*not affected · semver
- 6.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.11-1 | 6.1.11-1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-64kb | before 5.14.21-150500.55.103.1 | 5.14.21-150500.55.103.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-docs | before 5.14.21-150500.55.103.1 | 5.14.21-150500.55.103.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-obs-build | before 5.14.21-150500.55.103.1 | 5.14.21-150500.55.103.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-syms | before 5.14.21-150500.55.103.1 | 5.14.21-150500.55.103.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_26 | before 1-150500.11.3.1 | 1-150500.11.3.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-default | before 5.14.21-150500.55.103.1 | 5.14.21-150500.55.103.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-default-base | before 5.14.21-150500.55.103.1.150500.6.49.1 | 5.14.21-150500.55.103.1.150500.6.49.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-rt | before 5.14.21-150500.13.94.1 | 5.14.21-150500.13.94.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-source | before 5.14.21-150500.55.103.1 | 5.14.21-150500.55.103.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-source-rt | before 5.14.21-150500.13.94.1 | 5.14.21-150500.13.94.1 |
| SUSE:Linux Enterprise Server 15 SP5-LTSS | kernel-zfcpdump | before 5.14.21-150500.55.103.1 | 5.14.21-150500.55.103.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52981Mar 27, 2025 · drm/i915: Fix request ref counting during error capture & debugfs dump22Monitor
- ← EarlierCVE-2023-52982Mar 27, 2025 · fscache: Use wait_on_bit() to wait for the freeing of relinquished volume22Monitor
- Later →CVE-2023-52987Mar 27, 2025 · ASoC: SOF: ipc4-mtrace: prevent underflow in sof_ipc4_priority_mask_dfs_write()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 12b0ec7c6953e1602957926439e5297095d7d065 | Vendor (CNA) |
| Linux Linux | 9bd6074e1872d22190a8da30e796cbf937d334f0 | Vendor (CNA) |
| Linux Linux | c681d7a4ed3d360de0574f4d6b7305a8de8dc54f | Vendor (CNA) |
| Linux Linux | ddce1e091757d0259107c6c0c7262df201de2b66 | Vendor (CNA) |
| debian:linux | 6.1.11-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-64kb | 5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:kernel-default | 5.14.21-150500.55.103.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-default-base | 5.14.21-150500.55.103.1.150500.6.49.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-docs | 5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5_Update_26 | 1-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-obs-build | 5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:kernel-rt | 5.14.21-150500.13.94.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-source | 5.14.21-150500.55.103.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-source-rt | 5.14.21-150500.13.94.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-syms | 5.14.21-150500.55.103.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:kernel-zfcpdump | 5.14.21-150500.55.103.1 · SUSE:Linux Enterprise Server 15 SP5-LTSS | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-43185405 days apartksmbd: fix signededness bug in smb_direct_prepare_negotiation()39Monitor
- CVE-2025-38459120 days apartatm: clip: Fix infinite recursive call of clip_push().31Monitor
- CVE-2024-35886312 days apartipv6: Fix infinite recursion in fib6_dump_done().31Monitor
- CVE-2026-53202455 days apartaccel/ivpu: Fix signed integer truncation in IPC receive31Monitor
- CVE-2026-53267455 days apartnetfilter: nft_ct: bail out on template ct in get eval31Monitor
- CVE-2026-53395479 days apartnfsd: fix dead ACL conflict guard in nfsd4_create30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-674 · Uncontrolled RecursionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.