{"api_version":"1","generated_at":"2026-09-12T11:45:07+00:00","cve":"CVE-2026-80625","urls":{"html":"https://cve.report/CVE-2026-80625","api":"https://cve.report/api/cve/CVE-2026-80625.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80625","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80625"},"summary":{"title":"RDMA/hns: Fix memory leak of bonding resources","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/hns: Fix memory leak of bonding resources\n\nIn a corner case of concurrent driver removal and driver reset,\nbonding resource is first released in hns_roce_hw_v2_exit() during\ndriver removal, and then is allocated again in hns_roce_register_device()\nduring driver reset. This leads to memory leak because the release\ntiming has already passed. This may also lead to a kernel panic\nas below because of the leaked notifier callback:\n\nCall trace:\n  0xffffa20fccc04978 (P)\n  raw_notifier_call_chain+0x20/0x38\n  call_netdevice_notifiers_info+0x60/0xb8\n  netdev_lower_state_changed+0x4c/0xb8\n\nAs Sashiko suggested, the teardown order of bonding resources should\nbe inverted to make sure the resources are released when the driver\nis removed.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-28 08:16:46","updated_at":"2026-08-28 08:16:46"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/bc4caea7a82bbcf94a34eff7094e7f9b501680ab","name":"https://git.kernel.org/stable/c/bc4caea7a82bbcf94a34eff7094e7f9b501680ab","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c0bd03b850d81a8914168d87ddf7f6ffa58875ef","name":"https://git.kernel.org/stable/c/c0bd03b850d81a8914168d87ddf7f6ffa58875ef","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80625","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80625","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b37ad2e290fc52e575572b04803a4f93f584df6c bc4caea7a82bbcf94a34eff7094e7f9b501680ab git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b37ad2e290fc52e575572b04803a4f93f584df6c c0bd03b850d81a8914168d87ddf7f6ffa58875ef git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.19","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80625","cve":"CVE-2026-80625","epss":"0.001550000","percentile":"0.050010000","score_date":"2026-08-30","updated_at":"2026-08-31 00:14:06"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/infiniband/hw/hns/hns_roce_hw_v2.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"bc4caea7a82bbcf94a34eff7094e7f9b501680ab","status":"affected","version":"b37ad2e290fc52e575572b04803a4f93f584df6c","versionType":"git"},{"lessThan":"c0bd03b850d81a8914168d87ddf7f6ffa58875ef","status":"affected","version":"b37ad2e290fc52e575572b04803a4f93f584df6c","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/infiniband/hw/hns/hns_roce_hw_v2.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.19"},{"lessThan":"6.19","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"6.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"6.19","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/hns: Fix memory leak of bonding resources\n\nIn a corner case of concurrent driver removal and driver reset,\nbonding resource is first released in hns_roce_hw_v2_exit() during\ndriver removal, and then is allocated again in hns_roce_register_device()\nduring driver reset. This leads to memory leak because the release\ntiming has already passed. This may also lead to a kernel panic\nas below because of the leaked notifier callback:\n\nCall trace:\n  0xffffa20fccc04978 (P)\n  raw_notifier_call_chain+0x20/0x38\n  call_netdevice_notifiers_info+0x60/0xb8\n  netdev_lower_state_changed+0x4c/0xb8\n\nAs Sashiko suggested, the teardown order of bonding resources should\nbe inverted to make sure the resources are released when the driver\nis removed."}],"providerMetadata":{"dateUpdated":"2026-08-28T06:48:43.583Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/bc4caea7a82bbcf94a34eff7094e7f9b501680ab"},{"url":"https://git.kernel.org/stable/c/c0bd03b850d81a8914168d87ddf7f6ffa58875ef"}],"title":"RDMA/hns: Fix memory leak of bonding resources","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80625","datePublished":"2026-08-28T06:48:43.583Z","dateReserved":"2026-08-26T14:34:25.775Z","dateUpdated":"2026-08-28T06:48:43.583Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-28 08:16:46","lastModifiedDate":"2026-08-28 08:16:46","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80625","Ordinal":"1","Title":"RDMA/hns: Fix memory leak of bonding resources","CVE":"CVE-2026-80625","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80625","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/hns: Fix memory leak of bonding resources\n\nIn a corner case of concurrent driver removal and driver reset,\nbonding resource is first released in hns_roce_hw_v2_exit() during\ndriver removal, and then is allocated again in hns_roce_register_device()\nduring driver reset. This leads to memory leak because the release\ntiming has already passed. This may also lead to a kernel panic\nas below because of the leaked notifier callback:\n\nCall trace:\n  0xffffa20fccc04978 (P)\n  raw_notifier_call_chain+0x20/0x38\n  call_netdevice_notifiers_info+0x60/0xb8\n  netdev_lower_state_changed+0x4c/0xb8\n\nAs Sashiko suggested, the teardown order of bonding resources should\nbe inverted to make sure the resources are released when the driver\nis removed.","Type":"Description","Title":"RDMA/hns: Fix memory leak of bonding resources"}]}}}