CVE-2025-38019: mlxsw: spectrum_router: Fix use-after-free when deleting GRE net devices
Noroxi assessment
Priority: Monitor (action score 31/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.21% (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 92ec4855034b2c4d13f117558dc73d20581fa9ff, 9ab7945f3a61ed23da412e30f1e56414c05c4f06, abc43c1ffdbc801b0b04ac845bfaf1d42b8f68f7.
Low priority for now. Upgrade to Linux Linux 92ec4855034b2c4d13f117558dc73d20581fa9ff, 9ab7945f3a61ed23da412e30f1e56414c05c4f06, abc43c1ffdbc801b0b04ac845bfaf1d42b8f68f7 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: mlxsw: spectrum_router: Fix use-after-free when deleting GRE net devices The driver only offloads neighbors that are constructed on top of net devices registered by it or their uppers (which are all Ethernet). The device supports GRE encapsulation and decapsulation of forwarded traffic, but the driver will not offload dummy neighbors constructed on top of GRE net devices as they are not uppers of its net devices: # ip link add name gre1 up type gre tos inherit local 192.0.2.1 remote 198.51.100.1 # ip neigh add 0.0.0.0 lladdr 0.0.0.0 nud noarp dev gre1 $ ip neigh show dev gre1 nud noarp 0.0.0.0 lladdr 0.0.0.0 NOARP (Note that the neighbor is not marked with 'offload') When the driver is reloaded and the existing configuration is replayed, the driver does not perform the same check regarding existing neighbors and offloads the previously added one: # devlink dev reload pci/0000:01:00.0 $ ip neigh show dev gre1 nud noarp 0.0.0.0 lladdr 0.0.0.0 offload NOARP If the neighbor is later deleted, the driver will ignore the notification (given the GRE net device is not its upper) and will therefore keep referencing freed memory, resulting in a use-after-free [1] when the net device is deleted: # ip neigh del 0.0.0.0 lladdr 0.0.0.0 dev gre1 # ip link del dev gre1 Fix by skipping neighbor replay if the net device for which the replay is performed is not our upper. [1] BUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x1ea/0x200 Read of size 8 at addr ffff888155b0e420 by task ip/2282 [...] Call Trace: <TASK> dump_stack_lvl+0x6f/0xa0 print_address_description.constprop.0+0x6f/0x350 print_report+0x108/0x205 kasan_report+0xdf/0x110 mlxsw_sp_neigh_entry_update+0x1ea/0x200 mlxsw_sp_router_rif_gone_sync+0x2a8/0x440 mlxsw_sp_rif_destroy+0x1e9/0x750 mlxsw_sp_netdevice_ipip_ol_event+0x3c9/0xdc0 mlxsw_sp_router_netdevice_event+0x3ac/0x15e0 notifier_call_chain+0xca/0x150 call_netdevice_notifiers_info+0x7f/0x100 unregister_netdevice_many_notify+0xc8c/0x1d90 rtnl_dellink+0x34e/0xa50 rtnetlink_rcv_msg+0x6fb/0xb70 netlink_rcv_skb+0x131/0x360 netlink_unicast+0x426/0x710 netlink_sendmsg+0x75a/0xc20 __sock_sendmsg+0xc1/0x150 ____sys_sendmsg+0x5aa/0x7b0 ___sys_sendmsg+0xfc/0x180 __sys_sendmsg+0x121/0x1b0 do_syscall_64+0xbb/0x1d0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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 kernel6.6 and later · before 6.6.92
- linux linux kernel6.7 and later · before 6.12.30
- linux linux kernel6.13 and later · before 6.14.8
- linux linux kernel6.15
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
- 6.6affected
- 8fdb09a7674c61c4f0e5faf0d63b3ce500a341b0 and later · before f1ecccb5cdda39bca8cd17bb0b6cf61361e33578affected · git
- 8fdb09a7674c61c4f0e5faf0d63b3ce500a341b0 and later · before abc43c1ffdbc801b0b04ac845bfaf1d42b8f68f7affected · git
- 8fdb09a7674c61c4f0e5faf0d63b3ce500a341b0 and later · before 9ab7945f3a61ed23da412e30f1e56414c05c4f06affected · git
- 8fdb09a7674c61c4f0e5faf0d63b3ce500a341b0 and later · before 92ec4855034b2c4d13f117558dc73d20581fa9ffaffected · git
- before 6.6not affected · semver
- 6.6.92 and later · up to and including 6.6.*not affected · semver
- 6.12.30 and later · up to and including 6.12.*not affected · semver
- 6.14.8 and later · up to and including 6.14.*not affected · semver
- 6.15 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.30-1 | 6.12.30-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.6.1.160000.2.4 | 6.12.0-160000.6.1.160000.2.4 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-syms | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-zfcpdump | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-default-base | before 6.12.0-160000.6.1.160000.2.4 | 6.12.0-160000.6.1.160000.2.4 |
| SUSE:Linux Micro 6.2 | kernel-rt | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro 6.2 | kernel-source | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
| SUSE:Linux Micro Extras 6.2 | kernel-obs-build | before 6.12.0-160000.6.1 | 6.12.0-160000.6.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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
Published before and after this one in the same product
- ← EarlierCVE-2025-38017Jun 18, 2025 · fs/eventpoll: fix endless busy loop after timeout has expired22Monitor
- ← EarlierCVE-2025-38018Jun 18, 2025 · net/tls: fix kernel panic when alloc_page failed22Monitor
- Later →CVE-2025-38020Jun 18, 2025 · net/mlx5e: Disable MACsec offload for uplink representor profile22Monitor
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 | 92ec4855034b2c4d13f117558dc73d20581fa9ff | Vendor (CNA) |
| Linux Linux | 9ab7945f3a61ed23da412e30f1e56414c05c4f06 | Vendor (CNA) |
| Linux Linux | abc43c1ffdbc801b0b04ac845bfaf1d42b8f68f7 | Vendor (CNA) |
| Linux Linux | f1ecccb5cdda39bca8cd17bb0b6cf61361e33578 | Vendor (CNA) |
| debian:linux | 6.12.30-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.6.1.160000.2.4 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-zfcpdump | 6.12.0-160000.6.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.6.1.160000.2.4 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.6.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-rt | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.6.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-syms | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.12.0-160000.6.1 · SUSE:Linux Enterprise Server 16.0 | 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.
No history yet (it accumulates with the daily EPSS job).
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).
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.