Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

Linux kernel macvlan RCU grace period use-after-free in macvlan_common_newlink()

IdentifiersCVE-2026-23273CWE-416· Use After Free

CVE-2026-23273 is a Linux kernel vulnerability in the macvlan networking subsystem caused by a race condition in the error path of macvlan_common_newlink(). The function can make a newly created macvlan device visible to other execution contexts before detecting an error. If link creation then fails, the caller may directly free the associated net_device via free_netdev(dev) without waiting for an RCU grace period. Concurrent packet-processing paths, specifically macvlan_forward_source() as reached from macvlan_handle_frame(), can still hold or obtain references to the device and subsequently dereference freed memory, resulting in a slab use-after-free. The issue was demonstrated with a reproducer using veth interfaces and a macvlan interface in source mode, and KASAN reported the fault in drivers/net/macvlan.c at lines 408 and 444.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful triggering of the race causes a kernel slab use-after-free in the macvlan data path. This can lead to kernel memory corruption, kernel crashes, and denial of service. Given the nature of use-after-free conditions in kernel context, there is also potential for further impact such as privilege escalation or other compromise of confidentiality, integrity, and availability, although the provided content specifically demonstrates the bug as a KASAN-detected use-after-free and crash condition.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by restricting untrusted local users' ability to create or manipulate network links via rtnetlink, and avoid or disable use of macvlan interfaces in source mode where operationally feasible. Limit CAP_NET_ADMIN access and container or namespace configurations that permit local network device creation. These measures may reduce the likelihood of exploitation but do not eliminate the underlying race; patching is the definitive mitigation.

Remediation

Patch, then assume compromise.

Apply a kernel update that includes the fix for CVE-2026-23273. The fix ensures that the error path in macvlan_common_newlink() observes an RCU grace period before the device is freed, either within macvlan itself or via the core networking stack. Vendor-fixed package versions in the provided content include, among others, SUSE kernel-default >= 5.14.21-150500.55.166.1 for several SLES 15 SP5/Micro 5.5 lines, >= 6.4.0-150600.23.112.1 for several SLES 15 SP6 lines, >= 6.4.0-150700.53.55.1 for several SLES 15 SP7 lines, and >= 6.12.0-160000.33.1 for SLES 16.0, SUSE Linux Micro 6.2, and openSUSE Leap 16.0. Use the vendor-maintained kernel package for the affected distribution.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.