{"id":"CVE-2025-68742","summary":"bpf: Fix invalid prog-\u003estats access when update_effective_progs fails","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix invalid prog-\u003estats access when update_effective_progs fails\n\nSyzkaller triggers an invalid memory access issue following fault\ninjection in update_effective_progs. The issue can be described as\nfollows:\n\n__cgroup_bpf_detach\n  update_effective_progs\n    compute_effective_progs\n      bpf_prog_array_alloc \u003c-- fault inject\n  purge_effective_progs\n    /* change to dummy_bpf_prog */\n    array-\u003eitems[index] = &dummy_bpf_prog.prog\n\n---softirq start---\n__do_softirq\n  ...\n    __cgroup_bpf_run_filter_skb\n      __bpf_prog_run_save_cb\n        bpf_prog_run\n          stats = this_cpu_ptr(prog-\u003estats)\n          /* invalid memory access */\n          flags = u64_stats_update_begin_irqsave(&stats-\u003esyncp)\n---softirq end---\n\n  static_branch_dec(&cgroup_bpf_enabled_key[atype])\n\nThe reason is that fault injection caused update_effective_progs to fail\nand then changed the original prog into dummy_bpf_prog.prog in\npurge_effective_progs. Then a softirq came, and accessing the members of\ndummy_bpf_prog.prog in the softirq triggers invalid mem access.\n\nTo fix it, skip updating stats when stats is NULL.","modified":"2026-04-02T13:03:44.914345Z","published":"2025-12-24T12:09:39.341Z","related":["SUSE-SU-2026:0278-1","SUSE-SU-2026:0281-1","SUSE-SU-2026:0315-1","SUSE-SU-2026:20207-1","SUSE-SU-2026:20220-1","SUSE-SU-2026:20228-1","SUSE-SU-2026:20477-1","SUSE-SU-2026:20498-1","SUSE-SU-2026:20845-1","SUSE-SU-2026:20876-1","openSUSE-SU-2026:10039-1","openSUSE-SU-2026:10301-1","openSUSE-SU-2026:20145-1"],"database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68742.json"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/2579c356ccd35d06238b176e4b460978186d804b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/539137e3038ce6f953efd72110110f03c14c7d97"},{"type":"WEB","url":"https://git.kernel.org/stable/c/56905bb70c8b88421709bb4e32fcba617aa37d41"},{"type":"WEB","url":"https://git.kernel.org/stable/c/7dc211c1159d991db609bdf4b0fb9033c04adcbc"},{"type":"WEB","url":"https://git.kernel.org/stable/c/93d1964773ff513c9bd530f7686d3e48b786fa6b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/bf2c990b012100610c0f1ec5c4ea434da2d080c2"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68742.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68742"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"492ecee892c2a4ba6a14903d5d586ff750b7e805"},{"fixed":"93d1964773ff513c9bd530f7686d3e48b786fa6b"},{"fixed":"bf2c990b012100610c0f1ec5c4ea434da2d080c2"},{"fixed":"539137e3038ce6f953efd72110110f03c14c7d97"},{"fixed":"56905bb70c8b88421709bb4e32fcba617aa37d41"},{"fixed":"2579c356ccd35d06238b176e4b460978186d804b"},{"fixed":"7dc211c1159d991db609bdf4b0fb9033c04adcbc"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-68742.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.1.0"},{"fixed":"6.1.160"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.120"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.63"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.17.13"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.18.0"},{"fixed":"6.18.2"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-68742.json"}}],"schema_version":"1.7.5"}