# CVE-2026-80625: RDMA/hns: Fix memory leak of bonding resources

> A race condition in the Linux kernel RDMA driver causes a memory leak and potential kernel panic during concurrent driver removal and reset.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-80625, GHSA-q7c4-mw3p-rvrq, UBUNTU-CVE-2026-80625

## What is CVE-2026-80625?

CVE-2026-80625 is a memory corruption vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-80625?


## How do I fix CVE-2026-80625?

Apply the vendor's patch.

## Is CVE-2026-80625 being exploited?

There is no known exploitation of CVE-2026-80625 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80625 and fix it if it is affected.

What it is: CVE-2026-80625 is a memory corruption vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80625 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80625/ (Markdown: https://insights.sbomify.com/CVE-2026-80625/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80625
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80625
- OSV: https://osv.dev/vulnerability/CVE-2026-80625

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80625/
Summaries are generated and may contain mistakes; the official description above is the record.