CVE-2025-21852: net: Add rx_skb of kfree_skb to raw_tp_null_args[].
In the Linux kernel, the following vulnerability has been resolved:
net: Add rx_skb of kfree_skb to raw_tp_null_args[].
Yan Zhai reported a BPF prog could trigger a null-ptr-deref [0]
in trace_kfree_skb if the prog does not check if rx_sk is NULL.
Commit c53795d48ee8 ("net: add rx_sk to trace_kfree_skb") added
rx_sk to trace_kfree_skb, but rx_sk is optional and could be NULL.
Let's add kfree_skb to raw_tp_null_args[] to let the BPF verifier
validate such a prog and prevent the issue.
Now we fail to load such a prog:
libbpf: prog 'drop': -- BEGIN PROG LOAD LOG --
0: R1=ctx() R10=fp0
; int BPF_PROG(drop, struct sk_buff *skb, void *location, @ kfree_skb_sk_null.bpf.c:21
0: (79) r3 = *(u64 *)(r1 +24)
func 'kfree_skb' arg3 has btf_id 5253 type STRUCT 'sock'
1: R1=ctx() R3_w=trusted_ptr_or_null_sock(id=1)
; bpf_printk("sk: %d, %d\n", sk, sk->__sk_common.skc_family); @ kfree_skb_sk_null.bpf.c:24
1: (69) r4 = *(u16 *)(r3 +16)
R3 invalid mem access 'trusted_ptr_or_null_'
processed 2 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0
-- END PROG LOAD LOG --
Note this fix requires commit 838a10bd2ebf ("bpf: Augment raw_tp
arguments with PTR_MAYBE_NULL").
[0]:
BUG: kernel NULL pointer dereference, address: 0000000000000010
PF: supervisor read access in kernel mode
PF: error_code(0x0000) - not-present page
PGD 0 P4D 0
PREEMPT SMP
RIP: 0010:bpf_prog_5e21a6db8fcff1aa_drop+0x10/0x2d
Call Trace:
<TASK>
? __die+0x1f/0x60
? page_fault_oops+0x148/0x420
? search_bpf_extables+0x5b/0x70
? fixup_exception+0x27/0x2c0
? exc_page_fault+0x75/0x170
? asm_exc_page_fault+0x22/0x30
? bpf_prog_5e21a6db8fcff1aa_drop+0x10/0x2d
bpf_trace_run4+0x68/0xd0
? unix_stream_connect+0x1f4/0x6f0
sk_skb_reason_drop+0x90/0x120
unix_stream_connect+0x1f4/0x6f0
__sys_connect+0x7f/0xb0
__x64_sys_connect+0x14/0x20
do_syscall_64+0x47/0xc30
entry_SYSCALL_64_after_hwframe+0x4b/0x53
Security readout for executives and security teams
Plain-English summary
CVE-2025-21852 is a Linux kernel flaw where a locally run BPF program can trigger a kernel null pointer dereference, causing a denial of service. The known impact is availability loss, not data theft or privilege escalation.
Executive priority
Treat as a routine but real availability risk for Linux fleets. Prioritize patching multi-tenant or developer systems where local BPF use is plausible; emergency response is not supported by current evidence.
Technical view
The issue is CWE-476 in Linux networking tracepoint handling. trace_kfree_skb gained an optional rx_sk argument, but verifier metadata did not mark kfree_skb raw tracepoint arguments as nullable, allowing unsafe BPF access to a NULL sock pointer and kernel crash.
Likely exposure
Exposure is limited to affected Linux kernel builds where a local user or process can load relevant BPF programs. Internet-facing services are not directly exposed by the source evidence.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction, with high availability impact. The bundle marks KEV as false and provides no cited evidence of active exploitation.
Researcher notes
The fix adds kfree_skb to raw_tp_null_args so the BPF verifier treats the sock argument as possibly NULL and rejects unsafe dereference. The source evidence is patch-level and does not document exploit use beyond the reported crash trigger.
Mitigation direction
Apply vendor kernel updates containing the referenced stable fixes.
When backporting, include prerequisite commit 838a10bd2ebf as noted upstream.
Prioritize shared Linux systems where local users or workloads can load BPF programs.
Check distribution advisories for supported package versions and deployment guidance.
Validation and detection
Inventory Linux kernel versions against vendor advisories for CVE-2025-21852.
Verify patched kernels include one of the referenced stable commits or an equivalent backport.
Confirm BPF-loading capability is limited to expected trusted users or services.
Review crash reports for null pointer dereferences involving trace_kfree_skb or kfree_skb.
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-476: 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-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.