RDMA/hns: Fix memory leak of bonding resources
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 7.1.5
- CVEs
- CVE-2026-80625
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 17:45 UTC · Revision 1
Source evidence
RDMA/hns: Fix memory leak of bonding resources
core-osv · Original sourcePublished 28 Aug 2026, 06:48 UTC
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.
osv:CVE-2026-80625
Kernel
Fixed versions: 7.1.5
Complete source record
{
"id": "f4bc57e197210b32cdad3d9e4fabdf9982529068d733313a70a984364986a04a",
"url": "https://osv.dev/vulnerability/CVE-2026-80625",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "RDMA/hns: Fix memory leak of bonding resources",
"summary": "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.",
"evidence": "osv:CVE-2026-80625",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "7.1.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-80625",
"aliases": [
"CVE-2026-80625"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "b37ad2e290fc52e575572b04803a4f93f584df6c"
},
{
"fixed": "bc4caea7a82bbcf94a34eff7094e7f9b501680ab"
},
{
"fixed": "c0bd03b850d81a8914168d87ddf7f6ffa58875ef"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80625.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80625.json"
}
}
],
"modified": "2026-10-28T02:30:38.025198162Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/bc4caea7a82bbcf94a34eff7094e7f9b501680ab",
"https://git.kernel.org/stable/c/c0bd03b850d81a8914168d87ddf7f6ffa58875ef",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80625.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-80625",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80625.json"
}
},
"related_cves": [
{
"value": "CVE-2026-80625",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 505433,
"published_at": "2026-08-28T06:48:43.583+00:00"
}