VYPR
Unrated severityNVD Advisory· Published Mar 25, 2026· Updated Apr 18, 2026

CVE-2026-23304

CVE-2026-23304

Description

In the Linux kernel, the following vulnerability has been resolved:

ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu()

l3mdev_master_dev_rcu() can return NULL when the slave device is being un-slaved from a VRF. All other callers deal with this, but we lost the fallback to loopback in ip6_rt_pcpu_alloc() -> ip6_rt_get_dev_rcu() with commit 4832c30d5458 ("net: ipv6: put host and anycast routes on device with address").

KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f] RIP: 0010:ip6_rt_pcpu_alloc (net/ipv6/route.c:1418) Call Trace: ip6_pol_route (net/ipv6/route.c:2318) fib6_rule_lookup (net/ipv6/fib6_rules.c:115) ip6_route_output_flags (net/ipv6/route.c:2607) vrf_process_v6_outbound (drivers/net/vrf.c:437)

I was tempted to rework the un-slaving code to clear the flag first and insert synchronize_rcu() before we remove the upper. But looks like the explicit fallback to loopback_dev is an established pattern. And I guess avoiding the synchronize_rcu() is nice, too.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A NULL pointer dereference in the Linux kernel's IPv6 routing code can be triggered when a VRF slave device is un-slaved, leading to a system crash.

Vulnerability

Description

In the Linux kernel, the function ip6_rt_get_dev_rcu() can return NULL when called from ip6_rt_pcpu_alloc() if the slave device is being removed from a VRF. This occurs because l3mdev_master_dev_rcu() returns NULL in that race condition, and the fallback to the loopback device was removed by commit 4832c30d5458 ("net: ipv6: put host and anycast routes on device with address"). The fix commits [1][2][3][4] reintroduce the fallback to prevent the NULL pointer dereference.

Exploitation

The vulnerability is triggered during VRF outbound processing when a slave device is being un-slaved. The call path is vrf_process_v6_outbound -> ip6_route_output_flags -> fib6_rule_lookup -> ip6_pol_route -> ip6_rt_pcpu_alloc, where the NULL pointer dereference occurs. An attacker with the ability to influence VRF configuration or network namespaces could potentially trigger this race condition.

Impact

Successful exploitation results in a NULL pointer dereference, causing a kernel panic and denial of service. The KASAN report confirms the null-ptr-deref in the range [0x0000000000000108-0x000000000000010f].

Mitigation

The fix reintroduces the fallback to the loopback device when l3mdev_master_dev_rcu() returns NULL. The patch has been applied to stable kernel trees as seen in commits [1], [2], [3], and [4]. Users should update to the latest stable kernel versions containing these fixes.

AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

8

News mentions

0

No linked articles in our index yet.