PoC Monitor
← All CVEs
CVE-2026-74314published 15 Aug 2026 05:58 UTCData: JSON · API

Linux

bpf: Cancel special fields on map value recycle

In the Linux kernel, the following vulnerability has been resolved: bpf: Cancel special fields on map value recycle Map update and delete paths currently call bpf_obj_free_fields() when a value is being replaced or recycled. That makes field destruction depend on the context of the update/delete operation. For tracing programs this can include NMI context, where referenced kptr destructors, uptr unpinning, and graph root destruction are not generally safe. Introduce bpf_obj_cancel_fields() for the reusable-value path. It only performs NMI-safe cleanup for timer, workqueue, and task_work fields. Fields that need full destruction are left attached to the recycled value and are destroyed by the final cleanup path instead. Switch array and hashtab update/delete/recycle paths to this cancel helper. Keep bpf_obj_free_fields() for final map destruction and for bpf_mem_alloc destructors. Preallocated hashtabs do not have allocator destructors, so teardown continues to walk the normal and extra elements and fully destroy their fields. This deliberately relaxes the eager-free semantics of map update/delete for special fields. Programs that relied on a recycled map slot becoming empty immediately after update/delete were relying on behavior that cannot be implemented safely from every BPF execution context without offloading arbitrary destructors. There is a chance this change breaks programs making assumptions regarding the eager freeing of fields. If so, we can relax semantics to cancellation only when irqs_disabled() is true in the future. However, theoretically, map values that get reused eagerly already have weaker guarantees as parallel users can recreate freed fields before the new element becomes visible again.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 14a324f6a67ef6a53e04362a70160a47eb8afffa, < 9ea734e2cc0143d7429ab7dc0b20c85e5836183c
  • >= 14a324f6a67ef6a53e04362a70160a47eb8afffa, < a3a81d247651218e47153f2d2afd7aee236726fd
  • f0462d38589422bc9e27fd3c6343dfeb6b3db2f9
  • >= 5.18.18, < 5.19

Fixed in 9ea734e2cc0143d7429ab7dc0b20c85e5836183c, a3a81d247651218e47153f2d2afd7aee236726fd, 5.19

Linux Linux
  • 5.19

Fixed in 0, 7.1.5, 7.2

Mitigation

Upgrade Linux to 9ea734e2cc0143d7429ab7dc0b20c85e5836183c or a3a81d247651218e47153f2d2afd7aee236726fd or 5.19 or later.

Upgrade Linux to 0 or 7.1.5 or 7.2 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published15 Aug 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.