CVE-2026-80625

RDMA/hns: Fix memory leak of bonding resources

Published Aug 28, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

RDMA/hns: Fix memory leak of bonding resources

In a corner case of concurrent driver removal and driver reset,
bonding resource is first released in hns_roce_hw_v2_exit() during
driver removal, and then is allocated again in hns_roce_register_device()
during driver reset. This leads to memory leak because the release
timing has already passed. This may also lead to a kernel panic
as below because of the leaked notifier callback:

Call trace:
0xffffa20fccc04978 (P)
raw_notifier_call_chain+0x20/0x38
call_netdevice_notifiers_info+0x60/0xb8
netdev_lower_state_changed+0x4c/0xb8

As Sashiko suggested, the teardown order of bonding resources should
be inverted to make sure the resources are released when the driver
is removed.

Analysis

AI-generated

Technical impact

The flaw lies in the concurrent removal and re‑initialization of the hns_roce v2 RDMA driver. During driver removal the bonding resources are released, but a reset later allocates them again, leaking the notifier callback. When the notifier chain is later invoked, the dangling reference triggers a kernel panic, halting the system.

Affected Systems

All kernel builds that incorporate the unpatched hns_roce v2 driver. The vulnerability is present in Linux kernel releases before the bc4caea7a revert commit. Because the driver is part of the kernel, any distribution shipping such a kernel version is affected.

Risk and Exploitability

The CVSS score is 5.5, and the EPSS score is reported as less than 1%, indicating a very low current exploitation probability. The vulnerability is not listed in the CISA KEV catalog, so no confirmed exploitation has been reported. Based on the description, it is inferred that an attacker would need elevated privileges to unload and reload the RDMA driver, which is typically a privileged local operation. If such an action were achieved, a kernel panic could be forced, causing denial of service.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to include the bc4caea7a commit that corrects the bonding resource teardown order.
  • If a kernel upgrade is not feasible, disable or remove the hns_roce driver until the patch is applied.
  • Monitor system logs for kernel panic or OOM events related to notifier chains and enforce strict controls on driver unload and reload operations.

Generated by OpenCVE AI on September 1, 2026 at 17:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8887-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8889-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-2 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9003-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9043-1 Linux kernel (NVIDIA) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-826
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Weaknesses CWE-401
CWE-459
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix memory leak of bonding resources In a corner case of concurrent driver removal and driver reset, bonding resource is first released in hns_roce_hw_v2_exit() during driver removal, and then is allocated again in hns_roce_register_device() during driver reset. This leads to memory leak because the release timing has already passed. This may also lead to a kernel panic as below because of the leaked notifier callback: Call trace: 0xffffa20fccc04978 (P) raw_notifier_call_chain+0x20/0x38 call_netdevice_notifiers_info+0x60/0xb8 netdev_lower_state_changed+0x4c/0xb8 As Sashiko suggested, the teardown order of bonding resources should be inverted to make sure the resources are released when the driver is removed.
Title RDMA/hns: Fix memory leak of bonding resources
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-401

    Missing Release of Memory after Effective Lifetime

  • CWE-459

    Incomplete Cleanup

  • CWE-826

    Premature Release of Resource During Expected Lifetime

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Aug 28, 2026, 6:48 AM
Reserved
Aug 26, 2026, 2:34 PM
Status
Received
Published
Aug 28, 2026, 8:16 AM
Modified
Aug 28, 2026, 8:16 AM
Severity
Moderate
Public date
Aug 28, 2026, 12:00 AM