CVE-2026-23273
Use-After-Free Race Condition in Linux Kernel macvlan Network Driver
Publication date: 2026-03-20
Last updated on: 2026-04-02
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19.0-rc8 |
| linux_kernel | linux_kernel | 6.19.0-rc8 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's macvlan networking component. It is caused by a race condition in the macvlan_common_newlink() function, where a network device (@dev) might be made visible before an error is detected. This leads to a situation where the caller frees the device while it is still in use, violating the Read-Copy-Update (RCU) grace period rules. This can cause a use-after-free bug, potentially leading to memory corruption or kernel crashes.
How can this vulnerability impact me? :
The vulnerability can cause a use-after-free condition in the Linux kernel's networking stack, which may lead to system instability, crashes, or potential exploitation by attackers to execute arbitrary code or cause denial of service. This impacts the reliability and security of systems using the affected macvlan functionality.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to reproduce the race condition using specific ip link commands that trigger the macvlan_common_newlink() error path.
The following commands were used to reproduce the issue and can help detect it:
- ip link add p1 type veth peer p2
- ip link set address 00:00:00:00:00:20 dev p1
- ip link set up dev p1
- ip link set up dev p2
- ip link add mv0 link p2 type macvlan mode source
- (ip link add invalid% link p2 type macvlan mode source macaddr add 00:00:00:00:00:20 &) ; sleep 0.5 ; ping -c1 -I p1 1.2.3.4
If the vulnerability is present, you may see errors such as 'RTNETLINK answers: Invalid argument' and kernel BUG reports related to slab-use-after-free in macvlan_forward_source.
What immediate steps should I take to mitigate this vulnerability?
I don't know