CVE-2024-50252: mlxsw: spectrum_ipip: Fix memory leak when changing remote IPv6 address
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.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 12ae97c531fcd3bfd774d4dfeaeac23eafe24280, 31384aa2ad05c29c7745000f321154f42de24d1a, c1bbdbe07f0bc3bc9f87efe4672d67208c6d6942; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.
Low priority for now. Upgrade to Linux Linux 12ae97c531fcd3bfd774d4dfeaeac23eafe24280, 31384aa2ad05c29c7745000f321154f42de24d1a, c1bbdbe07f0bc3bc9f87efe4672d67208c6d6942; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-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: mlxsw: spectrum_ipip: Fix memory leak when changing remote IPv6 address The device stores IPv6 addresses that are used for encapsulation in linear memory that is managed by the driver. Changing the remote address of an ip6gre net device never worked properly, but since cited commit the following reproducer [1] would result in a warning [2] and a memory leak [3]. The problem is that the new remote address is never added by the driver to its hash table (and therefore the device) and the old address is never removed from it. Fix by programming the new address when the configuration of the ip6gre net device changes and removing the old one. If the address did not change, then the above would result in increasing the reference count of the address and then decreasing it. [1] # ip link add name bla up type ip6gre local 2001:db8:1::1 remote 2001:db8:2::1 tos inherit ttl inherit # ip link set dev bla type ip6gre remote 2001:db8:3::1 # ip link del dev bla # devlink dev reload pci/0000:01:00.0 [2] WARNING: CPU: 0 PID: 1682 at drivers/net/ethernet/mellanox/mlxsw/spectrum.c:3002 mlxsw_sp_ipv6_addr_put+0x140/0x1d0 Modules linked in: CPU: 0 UID: 0 PID: 1682 Comm: ip Not tainted 6.12.0-rc3-custom-g86b5b55bc835 #151 Hardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023 RIP: 0010:mlxsw_sp_ipv6_addr_put+0x140/0x1d0 [...] Call Trace: <TASK> mlxsw_sp_router_netdevice_event+0x55f/0x1240 notifier_call_chain+0x5a/0xd0 call_netdevice_notifiers_info+0x39/0x90 unregister_netdevice_many_notify+0x63e/0x9d0 rtnl_dellink+0x16b/0x3a0 rtnetlink_rcv_msg+0x142/0x3f0 netlink_rcv_skb+0x50/0x100 netlink_unicast+0x242/0x390 netlink_sendmsg+0x1de/0x420 ____sys_sendmsg+0x2bd/0x320 ___sys_sendmsg+0x9a/0xe0 __sys_sendmsg+0x7a/0xd0 do_syscall_64+0x9e/0x1a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f [3] unreferenced object 0xffff898081f597a0 (size 32): comm "ip", pid 1626, jiffies 4294719324 hex dump (first 32 bytes): 20 01 0d b8 00 02 00 00 00 00 00 00 00 00 00 01 ............... 21 49 61 83 80 89 ff ff 00 00 00 00 01 00 00 00 !Ia............. backtrace (crc fd9be911): [<00000000df89c55d>] __kmalloc_cache_noprof+0x1da/0x260 [<00000000ff2a1ddb>] mlxsw_sp_ipv6_addr_kvdl_index_get+0x281/0x340 [<000000009ddd445d>] mlxsw_sp_router_netdevice_event+0x47b/0x1240 [<00000000743e7757>] notifier_call_chain+0x5a/0xd0 [<000000007c7b9e13>] call_netdevice_notifiers_info+0x39/0x90 [<000000002509645d>] register_netdevice+0x5f7/0x7a0 [<00000000c2e7d2a9>] ip6gre_newlink_common.isra.0+0x65/0x130 [<0000000087cd6d8d>] ip6gre_newlink+0x72/0x120 [<000000004df7c7cc>] rtnl_newlink+0x471/0xa20 [<0000000057ed632a>] rtnetlink_rcv_msg+0x142/0x3f0 [<0000000032e0d5b5>] netlink_rcv_skb+0x50/0x100 [<00000000908bca63>] netlink_unicast+0x242/0x390 [<00000000cdbe1c87>] netlink_sendmsg+0x1de/0x420 [<0000000011db153e>] ____sys_sendmsg+0x2bd/0x320 [<000000003b6d53eb>] ___sys_sendmsg+0x9a/0xe0 [<00000000cae27c62>] __sys_sendmsg+0x7a/0xd0
- Published
- Nov 9, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-401
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.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 kernel5.17 and later · before 6.1.116
- linux linux kernel6.2 and later · before 6.6.60
- linux linux kernel6.7 and later · before 6.11.7
- linux linux kernel6.12
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
- 5.17affected
- cf42911523e02026cb56d329e584ae5923e94ba1 and later · before d8f298eb6659eb6a38e26b79e77de4449dc6e61baffected · git
- cf42911523e02026cb56d329e584ae5923e94ba1 and later · before 31384aa2ad05c29c7745000f321154f42de24d1aaffected · git
- cf42911523e02026cb56d329e584ae5923e94ba1 and later · before c1bbdbe07f0bc3bc9f87efe4672d67208c6d6942affected · git
- cf42911523e02026cb56d329e584ae5923e94ba1 and later · before 12ae97c531fcd3bfd774d4dfeaeac23eafe24280affected · git
- before 5.17not affected · semver
- 6.1.116 and later · up to and including 6.1.*not affected · semver
- 6.6.60 and later · up to and including 6.6.*not affected · semver
- 6.11.7 and later · up to and including 6.11.*not affected · semver
- 6.12 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 |
|---|---|---|---|
| AlmaLinux:9 | bpftool | before 7.4.0-503.21.1.el9_5 | 7.4.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-core | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-503.21.1.el9_5 | 5.14.0-503.21.1.el9_5 |
+96
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-2024-50249Nov 9, 2024 · ACPI: CPPC: Make rmw_lock a raw_spin_lock22Monitor
- ← EarlierCVE-2024-50250Nov 9, 2024 · fsdax: dax_unshare_iter needs to copy entire blocks28Monitor
- Later →CVE-2024-50253Nov 9, 2024 · bpf: Check the validity of nr_words in bpf_iter_bits_new()22Monitor
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 | 12ae97c531fcd3bfd774d4dfeaeac23eafe24280 | Vendor (CNA) |
| Linux Linux | 31384aa2ad05c29c7745000f321154f42de24d1a | Vendor (CNA) |
| Linux Linux | c1bbdbe07f0bc3bc9f87efe4672d67208c6d6942 | Vendor (CNA) |
| Linux Linux | d8f298eb6659eb6a38e26b79e77de4449dc6e61b | Vendor (CNA) |
| azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 7.4.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-503.21.1.el9_5 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.119-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.4.0-503.21.1.el9_5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-503.21.1.el9_5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-503.21.1.el9_5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-503.21.1.el9_5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-503.21.1.el9_5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-503.21.1.el9_5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-503.21.1.el9_5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-503.21.1.el9_5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-503.21.1.el9_5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-503.21.1.el9_5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-503.21.1.el9_5 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+1
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).
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-401 · Missing Release of Memory after Effective LifetimeCVSS 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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.