VDB

CVE-2026-80625

CVE-2026-80625 PUBLISHED

RDMA/hns: Fix memory leak of bonding resources

Reported by linux · Published August 28, 2026

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.

EPSS 0.20% · 9.5th percentile

Risk scores

EPSS Score
0.20%
9.5th percentile

Affected products

VendorProductVersions
LinuxLinuxb37ad2e290fc52e575572b04803a4f93f584df6c, b37ad2e290fc52e575572b04803a4f93f584df6c
LinuxLinux6.19, 0, 7.1.5
linuxlinux_kernel6.19, 6.19
LinuxLinux*, *, 6.19

Timeline

  • Aug 28, 2026 EPSS Score (11 in total, the first dated here)
  • Aug 28, 2026 Coalition ESS Score
  • Aug 28, 2026 CVE Published
  • Aug 28, 2026 CVE Updated
  • Sep 1, 2026 Security Advisory

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-80625
vulnetix vdb fixes CVE-2026-80625

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80625/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›