CVE-2025-22103: net: fix NULL pointer dereference in l3mdev_l3_rcv
In the Linux kernel, the following vulnerability has been resolved:
net: fix NULL pointer dereference in l3mdev_l3_rcv
When delete l3s ipvlan:
ip link del link eth0 ipvlan1 type ipvlan mode l3s
This may cause a null pointer dereference:
Call trace:
ip_rcv_finish+0x48/0xd0
ip_rcv+0x5c/0x100
__netif_receive_skb_one_core+0x64/0xb0
__netif_receive_skb+0x20/0x80
process_backlog+0xb4/0x204
napi_poll+0xe8/0x294
net_rx_action+0xd8/0x22c
__do_softirq+0x12c/0x354
This is because l3mdev_l3_rcv() visit dev->l3mdev_ops after
ipvlan_l3s_unregister() assign the dev->l3mdev_ops to NULL. The process
like this:
(CPU1) | (CPU2)
l3mdev_l3_rcv() |
check dev->priv_flags: |
master = skb->dev; |
|
| ipvlan_l3s_unregister()
| set dev->priv_flags
| dev->l3mdev_ops = NULL;
|
visit master->l3mdev_ops |
To avoid this by do not set dev->l3mdev_ops when unregister l3s ipvlan.
Security readout for executives and security teams
Plain-English summary
CVE-2025-22103 is a Linux kernel networking bug that can cause a NULL pointer dereference when an L3S ipvlan interface is deleted. The likely business impact is availability disruption on systems using this specialized networking feature. Public sources do not report active exploitation or data compromise.
Executive priority
Treat as a targeted availability risk, not a broad emergency. Patch in normal high-priority kernel maintenance windows, faster for container or network infrastructure using ipvlan L3S.
Technical view
The issue is a race in l3mdev_l3_rcv(): it checks device flags, while ipvlan_l3s_unregister() can set dev->l3mdev_ops to NULL before it is accessed. The upstream fix avoids clearing dev->l3mdev_ops during L3S ipvlan unregister. CVE data lists Linux kernel exposure and links stable kernel commits.
Likely exposure
Exposure is most relevant to Linux hosts using ipvlan in L3S mode. Container, virtualization, or network automation hosts that create and delete ipvlan interfaces should be reviewed first. Systems not using L3S ipvlan are less likely to be affected.
Exploitation context
The public record describes a crash condition during deletion of an L3S ipvlan interface. CISA KEV is false in the provided bundle, and no cited source reports active exploitation. Required privileges are not stated in the sources.
Researcher notes
The source bundle lacks CVSS, CWE, detailed version ranges, and privilege analysis. The safest validation path is commit-based or vendor-package confirmation. Avoid assuming exploitability beyond the documented NULL dereference during L3S ipvlan deletion.
Mitigation direction
Apply kernel updates that include the linked upstream stable fixes.
Prioritize Linux hosts using ipvlan L3S networking.
If packaged kernels are used, follow the Linux distribution vendor advisory.
Reduce unnecessary L3S ipvlan creation and deletion until patched.
Validation and detection
Inventory Linux kernel versions on hosts using ipvlan.
Check whether ipvlan L3S interfaces are deployed.
Confirm the running kernel includes one of the linked stable fixes.
Review kernel logs for NULL pointer dereference traces in l3mdev_l3_rcv or ipvlan unregister paths.
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.
cve · low confidence lookup
CVE-2025-22103 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Apr 16, 2025, 14:12 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.