In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix bpf_sk_select_reuseport() memory leak
As pointed out in the original comment, lookup in sockmap can return a TCP
ESTABLISHED socket. Such TCP socket may have had SO_ATTACH_REUSEPORT_EBPF
set before it was ESTABLISHED. In other words, a non-NULL sk_reuseport_cb
does not imply a non-refcounted socket.
Drop sk's reference in both error paths.
unreferenced object 0xffff888101911800 (size 2048):
comm "test_progs", pid 44109, jiffies 4297131437
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
80 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 9336483b):
__kmalloc_noprof+0x3bf/0x560
__reuseport_alloc+0x1d/0x40
reuseport_alloc+0xca/0x150
reuseport_attach_prog+0x87/0x140
sk_reuseport_attach_bpf+0xc8/0x100
sk_setsockopt+0x1181/0x1990
do_sock_setsockopt+0x12b/0x160
__sys_setsockopt+0x7b/0xc0
__x64_sys_setsockopt+0x1b/0x30
do_syscall_64+0x93/0x180
entry_SYSCALL_64_after_hwframe+0x76/0x7e
Security readout for executives and security teams
Plain-English summary
CVE-2025-21683 is a Linux kernel memory leak in BPF reuseport socket selection. A local user could potentially trigger resource exhaustion, affecting system availability, but the sources do not indicate data theft or remote compromise.
Executive priority
Treat as a moderate Linux availability risk. Patch through normal kernel maintenance, with higher urgency for shared infrastructure where local users or workloads could stress kernel memory.
Technical view
The bug is in bpf_sk_select_reuseport(), where sockmap lookup can return an established TCP socket with sk_reuseport_cb set. Error paths failed to drop the socket reference, creating a CWE-401 memory leak. CVSS is 5.5, local, low privilege, availability impact only.
Likely exposure
Exposure is mainly Linux systems running affected kernel versions or vendor distributions carrying the vulnerable code. Internet-facing status alone is not the key factor because the CVSS vector is local with privileges required.
Exploitation context
No provided source reports active exploitation, and the CVE is not in KEV. The documented impact is local availability degradation through memory leakage, not confidentiality or integrity compromise.
Researcher notes
Evidence supports a kernel reference leak in BPF reuseport handling. The source bundle provides fix commits and advisories, but not proof-of-concept status, real-world exploitation, or detailed per-distribution affected package matrices beyond referenced advisories.
Mitigation direction
Apply kernel updates that include the referenced stable fixes.
Check Linux distribution advisories for backported fixes and package versions.
For Debian LTS systems, review the linked March 2025 advisories.
For Siemens environments, review SSA-265688 for affected product guidance.
Prioritize shared multi-user and container-host Linux systems.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded systems.
Compare installed kernels against vendor advisories and fixed stable branches.
Confirm updated kernels are booted, not only installed.
Review vulnerability scanner findings for CVE-2025-21683 against distribution backport status.
Check whether relevant Siemens products are present in the environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.