{"api_version":"1","generated_at":"2026-08-22T05:27:49+00:00","cve":"CVE-2026-74314","urls":{"html":"https://cve.report/CVE-2026-74314","api":"https://cve.report/api/cve/CVE-2026-74314.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74314","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74314"},"summary":{"title":"bpf: Cancel special fields on map value recycle","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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:22:31","updated_at":"2026-08-17 06:19:25"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/9ea734e2cc0143d7429ab7dc0b20c85e5836183c","name":"https://git.kernel.org/stable/c/9ea734e2cc0143d7429ab7dc0b20c85e5836183c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a3a81d247651218e47153f2d2afd7aee236726fd","name":"https://git.kernel.org/stable/c/a3a81d247651218e47153f2d2afd7aee236726fd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74314","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74314","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 14a324f6a67ef6a53e04362a70160a47eb8afffa 9ea734e2cc0143d7429ab7dc0b20c85e5836183c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 14a324f6a67ef6a53e04362a70160a47eb8afffa a3a81d247651218e47153f2d2afd7aee236726fd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f0462d38589422bc9e27fd3c6343dfeb6b3db2f9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.18.18 5.19 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.19","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.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":"74314","cve":"CVE-2026-74314","epss":"0.001290000","percentile":"0.029640000","score_date":"2026-08-17","updated_at":"2026-08-18 00:11:46"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["include/linux/bpf.h","kernel/bpf/arraymap.c","kernel/bpf/hashtab.c","kernel/bpf/syscall.c","tools/testing/selftests/bpf/prog_tests/htab_update.c","tools/testing/selftests/bpf/prog_tests/linked_list.c","tools/testing/selftests/bpf/prog_tests/map_kptr.c","tools/testing/selftests/bpf/prog_tests/refcounted_kptr.c","tools/testing/selftests/bpf/progs/htab_update.c","tools/testing/selftests/bpf/progs/linked_list.c","tools/testing/selftests/bpf/progs/refcounted_kptr.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"9ea734e2cc0143d7429ab7dc0b20c85e5836183c","status":"affected","version":"14a324f6a67ef6a53e04362a70160a47eb8afffa","versionType":"git"},{"lessThan":"a3a81d247651218e47153f2d2afd7aee236726fd","status":"affected","version":"14a324f6a67ef6a53e04362a70160a47eb8afffa","versionType":"git"},{"status":"affected","version":"f0462d38589422bc9e27fd3c6343dfeb6b3db2f9","versionType":"git"},{"lessThan":"5.19","status":"affected","version":"5.18.18","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["include/linux/bpf.h","kernel/bpf/arraymap.c","kernel/bpf/hashtab.c","kernel/bpf/syscall.c","tools/testing/selftests/bpf/prog_tests/htab_update.c","tools/testing/selftests/bpf/prog_tests/linked_list.c","tools/testing/selftests/bpf/prog_tests/map_kptr.c","tools/testing/selftests/bpf/prog_tests/refcounted_kptr.c","tools/testing/selftests/bpf/progs/htab_update.c","tools/testing/selftests/bpf/progs/linked_list.c","tools/testing/selftests/bpf/progs/refcounted_kptr.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.19"},{"lessThan":"5.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":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.18.18","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_1":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - The bug is reached via bpf_map_update_elem/delete_elem on BPF array/hash maps, callable from the bpf() syscall and from in-kernel BPF helpers when tracing or perf BPF programs run; per kernel guidance BPF is a Local attack vector, not network-reachable.\nAC:L - An attacker who can load and attach BPF programs controls the map contents, update/delete timing, and trace/perf attach points (including NMI-capable hooks), so the unsafe bpf_obj_free_fields() recycle path is triggerable without luck or victim-specific state.\nPR:L - Exploitation requires loading tracing/perf BPF programs with BTF maps holding kptr/list/uptr fields (CAP_BPF plus CAP_PERFMON), which bpf_token_capable() grants to user-namespace CAP_SYS_ADMIN holders (e.g. unshare -Urn) and delegated BPF token users, not only init-namespace root.\nUI:N - No victim interaction is required; the attacker triggers map recycle from their own loaded BPF program or concurrent bpf() map operations during tracing/perf events they control.\nS:U - Impact stays within kernel memory and privilege boundaries (deadlock, oops, memory corruption, potential local privilege escalation) and does not cross VM, container, or IOMMU security scopes on its own.\nC:H - Recycling map values from NMI/atomic tracing context runs bpf_obj_free_fields() kptr destructors, uptr unpinning, and graph teardown unsafely, enabling use-after-free and inconsistent object lifetimes that can be turned into arbitrary kernel memory disclosure.\nI:H - The same unsafe recycle path performs non-NMI-safe kptr destructor calls, recursive __bpf_obj_drop_impl() graph freeing, and uptr unpinning from wrong context, giving plausible heap corruption and control-flow hijack primitives beyond a simple crash.\nA:H - Calling bpf_obj_free_fields() from NMI/tracing contexts can deadlock on BPF/hash locks (documented IN-NMI lockdep failures in related BPF LRU fixes) or panic/oops via illegal page unpinning and destructor execution, fully denying kernel availability."}]}],"providerMetadata":{"dateUpdated":"2026-08-17T05:45:47.130Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/9ea734e2cc0143d7429ab7dc0b20c85e5836183c"},{"url":"https://git.kernel.org/stable/c/a3a81d247651218e47153f2d2afd7aee236726fd"}],"title":"bpf: Cancel special fields on map value recycle","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74314","datePublished":"2026-08-15T05:58:12.766Z","dateReserved":"2026-08-15T05:44:03.883Z","dateUpdated":"2026-08-17T05:45:47.130Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 06:22:31","lastModifiedDate":"2026-08-17 06:19:25","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74314","Ordinal":"1","Title":"bpf: Cancel special fields on map value recycle","CVE":"CVE-2026-74314","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74314","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"bpf: Cancel special fields on map value recycle"}]}}}