{
  "id": "CVE-2026-74314",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-74314",
  "published_at": "2026-08-15T05:58:12.766Z",
  "title": "bpf: Cancel special fields on map value recycle",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Cancel special fields on map value recycle\n\nMap update and delete paths currently call bpf_obj_free_fields() when a\nvalue is being replaced or recycled. That makes field destruction depend\non the context of the update/delete operation. For tracing programs this\ncan include NMI context, where referenced kptr destructors, uptr\nunpinning, and graph root destruction are not generally safe.\n\nIntroduce bpf_obj_cancel_fields() for the reusable-value path. It only\nperforms NMI-safe cleanup for timer, workqueue, and task_work fields.\nFields that need full destruction are left attached to the recycled value\nand are destroyed by the final cleanup path instead.\n\nSwitch array and hashtab update/delete/recycle paths to this cancel\nhelper. Keep bpf_obj_free_fields() for final map destruction and for\nbpf_mem_alloc destructors. Preallocated hashtabs do not have allocator\ndestructors, so teardown continues to walk the normal and extra elements\nand fully destroy their fields.\n\nThis deliberately relaxes the eager-free semantics of map update/delete\nfor special fields. Programs that relied on a recycled map slot becoming\nempty immediately after update/delete were relying on behavior that\ncannot be implemented safely from every BPF execution context without\noffloading arbitrary destructors.\n\nThere is a chance this change breaks programs making assumptions\nregarding the eager freeing of fields. If so, we can relax semantics to\ncancellation only when irqs_disabled() is true in the future. However,\ntheoretically, map values that get reused eagerly already have weaker\nguarantees as parallel users can recreate freed fields before the new\nelement becomes visible again.",
  "cvss_by_source": {
    "cna": 7.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 14a324f6a67ef6a53e04362a70160a47eb8afffa, \u003c 9ea734e2cc0143d7429ab7dc0b20c85e5836183c",
          "\u003e= 14a324f6a67ef6a53e04362a70160a47eb8afffa, \u003c a3a81d247651218e47153f2d2afd7aee236726fd",
          "f0462d38589422bc9e27fd3c6343dfeb6b3db2f9",
          "\u003e= 5.18.18, \u003c 5.19"
        ],
        "fixed_in": [
          "9ea734e2cc0143d7429ab7dc0b20c85e5836183c",
          "a3a81d247651218e47153f2d2afd7aee236726fd",
          "5.19"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "5.19"
        ],
        "fixed_in": [
          "0",
          "7.1.5",
          "7.2"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 9ea734e2cc0143d7429ab7dc0b20c85e5836183c or a3a81d247651218e47153f2d2afd7aee236726fd or 5.19 or later.",
      "Upgrade Linux to 0 or 7.1.5 or 7.2 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
