vrf: Fix a potential NPD when removing a port from a VRF
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2674d603a9e6970463b2b9ebcf8e31e90beae169, 2c022f582fd16a470df6ed9e7fb7e9fc48946d49, 3db8d078f7f652379ee394132b169d304f6eb4c1; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2674d603a9e6970463b2b9ebcf8e31e90beae169, 2c022f582fd16a470df6ed9e7fb7e9fc48946d49, 3db8d078f7f652379ee394132b169d304f6eb4c1; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: vrf: Fix a potential NPD when removing a port from a VRF RCU readers that identified a net device as a VRF port using netif_is_l3_slave() assume that a subsequent call to netdev_master_upper_dev_get_rcu() will return a VRF device. They then continue to dereference its l3mdev operations. This assumption is not always correct and can result in a NPD [1]. There is no RCU synchronization when removing a port from a VRF, so it is possible for an RCU reader to see a new master device (e.g., a bridge) that does not have l3mdev operations. Fix by adding RCU synchronization after clearing the IFF_L3MDEV_SLAVE flag. Skip this synchronization when a net device is removed from a VRF as part of its deletion and when the VRF device itself is deleted. In the latter case an RCU grace period will pass by the time RTNL is released. [1] BUG: kernel NULL pointer dereference, address: 0000000000000000 [...] RIP: 0010:l3mdev_fib_table_rcu (net/l3mdev/l3mdev.c:181) [...] Call Trace: <TASK> l3mdev_fib_table_by_index (net/l3mdev/l3mdev.c:201 net/l3mdev/l3mdev.c:189) __inet_bind (net/ipv4/af_inet.c:499 (discriminator 3)) inet_bind_sk (net/ipv4/af_inet.c:469) __sys_bind (./include/linux/file.h:62 (discriminator 1) ./include/linux/file.h:83 (discriminator 1) net/socket.c:1951 (discriminator 1)) __x64_sys_bind (net/socket.c:1969 (discriminator 1) net/socket.c:1967 (discriminator 1) net/socket.c:1967 (discriminator 1)) do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)
- Published
- Jun 24, 2026
- Updated
- Jul 8, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.12 and later · before 5.10.258
- linux linux kernel5.11 and later · before 5.15.209
- linux linux kernel5.16 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.141
- linux linux kernel6.7 and later · before 6.12.91
- linux linux kernel6.13 and later · before 6.18.33
- linux linux kernel6.19 and later · before 7.0.10
- linux linux kernel7.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.12affected
- fdeea7be88b12742bfd50d9e19a06c0d2e702400 and later · before 2c022f582fd16a470df6ed9e7fb7e9fc48946d49affected · git
- fdeea7be88b12742bfd50d9e19a06c0d2e702400 and later · before 4ab6fc60ed5a0344b60711b09bff1dc238d8d6a4affected · git
- fdeea7be88b12742bfd50d9e19a06c0d2e702400 and later · before 468defa0b70902a22f4478c1207624bc1b31c124affected · git
- fdeea7be88b12742bfd50d9e19a06c0d2e702400 and later · before 3db8d078f7f652379ee394132b169d304f6eb4c1affected · git
- fdeea7be88b12742bfd50d9e19a06c0d2e702400 and later · before 8c2b792f04a3db97c9d8d2a45817e93f8884baf5affected · git
- fdeea7be88b12742bfd50d9e19a06c0d2e702400 and later · before a7a97f2303e63ede105c1d55ef53dc497364e11daffected · git
- fdeea7be88b12742bfd50d9e19a06c0d2e702400 and later · before d47204c127992da0c976ac9747070a575912e0feaffected · git
- fdeea7be88b12742bfd50d9e19a06c0d2e702400 and later · before 2674d603a9e6970463b2b9ebcf8e31e90beae169affected · git
- before 4.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.10-1 | 7.0.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2026-52921Jun 24, 2026 · netfilter: ipset: stop hash:* range iteration at end22Monitor
- ← EarlierCVE-2026-52922Jun 24, 2026 · batman-adv: dat: handle forward allocation error30Monitor
- Later →CVE-2026-52926Jun 24, 2026 · batman-adv: clear current gateway during teardown22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2674d603a9e6970463b2b9ebcf8e31e90beae169 | Vendor (CNA) |
| Linux Linux | 2c022f582fd16a470df6ed9e7fb7e9fc48946d49 | Vendor (CNA) |
| Linux Linux | 3db8d078f7f652379ee394132b169d304f6eb4c1 | Vendor (CNA) |
| Linux Linux | 468defa0b70902a22f4478c1207624bc1b31c124 | Vendor (CNA) |
| Linux Linux | 4ab6fc60ed5a0344b60711b09bff1dc238d8d6a4 | Vendor (CNA) |
| Linux Linux | 8c2b792f04a3db97c9d8d2a45817e93f8884baf5 | Vendor (CNA) |
| Linux Linux | a7a97f2303e63ede105c1d55ef53dc497364e11d | Vendor (CNA) |
| Linux Linux | d47204c127992da0c976ac9747070a575912e0fe | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.143.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0440 · Jun 25, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2c022f582fd16a470df6ed9e7fb7e9fc48946d49
- git.kernel.org/stable/c/3db8d078f7f652379ee394132b169d304f6eb4c1
- git.kernel.org/stable/c/468defa0b70902a22f4478c1207624bc1b31c124
- git.kernel.org/stable/c/4ab6fc60ed5a0344b60711b09bff1dc238d8d6a4
- git.kernel.org/stable/c/8c2b792f04a3db97c9d8d2a45817e93f8884baf5
- git.kernel.org/stable/c/a7a97f2303e63ede105c1d55ef53dc497364e11d
- git.kernel.org/stable/c/d47204c127992da0c976ac9747070a575912e0fe
Vendor advisories and official records. Exploit/PoC links are deliberately left out.