{
  "cveId": "CVE-2026-80625",
  "url": "https://patchblox.com/security/cve/CVE-2026-80625",
  "summary": "CVE-2026-80625 is fixed in linux on 1 platform by DEBIAN-CVE-2026-80625 (version 7.1.5-1), released August 29, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix memory leak of bonding resources...",
  "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\u002B0x20/0x38   call_netdevice_notifiers_info\u002B0x60/0xb8   netdev_lower_state_changed\u002B0x4c/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.",
  "published": "2026-08-28T08:16:46Z",
  "severity": "",
  "epss": 0.00198,
  "epssPercentile": 0.09566,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.1.5-1",
      "fix": "DEBIAN-CVE-2026-80625",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-80625",
      "released": "2026-08-29T00:46:20Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T19:12:23Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}