{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.5-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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.",
  "id": "DEBIAN-CVE-2026-80625",
  "modified": "2026-09-14T16:47:35.403740339Z",
  "published": "2026-08-28T08:16:46.647Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-80625"
    }
  ],
  "upstream": [
    "CVE-2026-80625"
  ]
}