Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40251: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy

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.15% (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 542f45486f1ce2d2dde75bd85aca0389ef7046c3, 715d9cda646a8a38ea8b2bb5afb679a7464055e2, 90e51e20bcec9bff5b2421ce1bd95704764655f5.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 542f45486f1ce2d2dde75bd85aca0389ef7046c3, 715d9cda646a8a38ea8b2bb5afb679a7464055e2, 90e51e20bcec9bff5b2421ce1bd95704764655f5 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: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy The function devl_rate_nodes_destroy is documented to "Unset parent for all rate objects". However, it was only calling the driver-specific `rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing the parent's refcount, without actually setting the `devlink_rate->parent` pointer to NULL. This leaves a dangling pointer in the `devlink_rate` struct, which cause refcount error in netdevsim[1] and mlx5[2]. In addition, this is inconsistent with the behavior of `devlink_nl_rate_parent_node_set`, where the parent pointer is correctly cleared. This patch fixes the issue by explicitly setting `devlink_rate->parent` to NULL after notifying the driver, thus fulfilling the function's documented behavior for all rate objects. [1] repro steps: echo 1 > /sys/bus/netdevsim/new_device devlink dev eswitch set netdevsim/netdevsim1 mode switchdev echo 1 > /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs devlink port function rate add netdevsim/netdevsim1/test_node devlink port function rate set netdevsim/netdevsim1/128 parent test_node echo 1 > /sys/bus/netdevsim/del_device dmesg: refcount_t: decrement hit 0; leaking memory. WARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0 CPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:refcount_warn_saturate+0x42/0xe0 Call Trace: <TASK> devl_rate_leaf_destroy+0x8d/0x90 __nsim_dev_port_del+0x6c/0x70 [netdevsim] nsim_dev_reload_destroy+0x11c/0x140 [netdevsim] nsim_drv_remove+0x2b/0xb0 [netdevsim] device_release_driver_internal+0x194/0x1f0 bus_remove_device+0xc6/0x130 device_del+0x159/0x3c0 device_unregister+0x1a/0x60 del_device_store+0x111/0x170 [netdevsim] kernfs_fop_write_iter+0x12e/0x1e0 vfs_write+0x215/0x3d0 ksys_write+0x5f/0xd0 do_syscall_64+0x55/0x10f0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 [2] devlink dev eswitch set pci/0000:08:00.0 mode switchdev devlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000 devlink port function rate add pci/0000:08:00.0/group1 devlink port function rate set pci/0000:08:00.0/32768 parent group1 modprobe -r mlx5_ib mlx5_fwctl mlx5_core dmesg: refcount_t: decrement hit 0; leaking memory. WARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0 CPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:refcount_warn_saturate+0x42/0xe0 Call Trace: <TASK> devl_rate_leaf_destroy+0x8d/0x90 mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core] mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core] mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core] mlx5_sf_esw_event+0xc4/0x120 [mlx5_core] notifier_call_chain+0x33/0xa0 blocking_notifier_call_chain+0x3b/0x50 mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core] mlx5_eswitch_disable+0x63/0x90 [mlx5_core] mlx5_unload+0x1d/0x170 [mlx5_core] mlx5_uninit_one+0xa2/0x130 [mlx5_core] remove_one+0x78/0xd0 [mlx5_core] pci_device_remove+0x39/0xa0 device_release_driver_internal+0x194/0x1f0 unbind_store+0x99/0xa0 kernfs_fop_write_iter+0x12e/0x1e0 vfs_write+0x215/0x3d0 ksys_write+0x5f/0xd0 do_syscall_64+0x53/0x1f0 entry_SYSCALL_64_after_hwframe+0x4b/0x53

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Dec 4, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

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%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2025-40251

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux 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.14 and later · before 6.1.164
  • linux linux kernel6.2 and later · before 6.6.118
  • linux linux kernel6.7 and later · before 6.12.60
  • linux linux kernel6.13 and later · before 6.17.10
  • linux linux kernel6.18

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.14affected
    • d7555984507822458b32a6405881038241d140be and later · before 90e51e20bcec9bff5b2421ce1bd95704764655f5affected · git
    • d7555984507822458b32a6405881038241d140be and later · before 715d9cda646a8a38ea8b2bb5afb679a7464055e2affected · git
    • d7555984507822458b32a6405881038241d140be and later · before c70df6c17d389cc743f0eb30160e2d6bc6910db8affected · git
    • d7555984507822458b32a6405881038241d140be and later · before 542f45486f1ce2d2dde75bd85aca0389ef7046c3affected · git
    • d7555984507822458b32a6405881038241d140be and later · before f94c1a114ac209977bdf5ca841b98424295ab1f0affected · git
    • before 5.14not affected · semver
    • 6.1.164 and later · up to and including 6.1.*not affected · semver
    • 6.6.118 and later · up to and including 6.6.*not affected · semver
    • 6.12.60 and later · up to and including 6.12.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:9kernelbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.27.1.el9_75.14.0-611.27.1.el9_7

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-13315Nov 19, 2025 · Unauthenticated log access in Twonky Server
    60This week
  • ← EarlierCVE-2025-13316Nov 19, 2025 · Hard-coded encryption keys in Twonky Server
    60This week
  • Later →CVE-2025-68211Dec 16, 2025 · ksm: use range-walk function to jump over holes in scan_get_next_rmap_item
    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 / packageFixed versionSource
Linux Linux542f45486f1ce2d2dde75bd85aca0389ef7046c3Vendor (CNA)
Linux Linux715d9cda646a8a38ea8b2bb5afb679a7464055e2Vendor (CNA)
Linux Linux90e51e20bcec9bff5b2421ce1bd95704764655f5Vendor (CNA)
Linux Linuxc70df6c17d389cc743f0eb30160e2d6bc6910db8Vendor (CNA)
Linux Linuxf94c1a114ac209977bdf5ca841b98424295ab1f0Vendor (CNA)
almalinux:kernel5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.27.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.164-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.164-1~deb11u1 · Debian:11Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)

+2

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.

EPSS, last 120 days

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.

Finders, 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

CVSS 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records