CVE-2025-38280None▾ SunlitIn the Linux kernel, the following vulnerability has been resolved: bpf: Avoid __bpf_prog_ret0_warn when jit fails syzkaller reported an issue: WARNING: CPU: 3 PID: 217 at kernel/bpf/core.c:2357 __bpf_prog_ret0_warn+0xa/0x20 kernel/bp…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Oct 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
In the Linux kernel, the following vulnerability has been resolved:
bpf: Avoid __bpf_prog_ret0_warn when jit fails
syzkaller reported an issue:
WARNING: CPU: 3 PID: 217 at kernel/bpf/core.c:2357 __bpf_prog_ret0_warn+0xa/0x20 kernel/bpf/core.c:2357 Modules linked in: CPU: 3 UID: 0 PID: 217 Comm: kworker/u32:6 Not tainted 6.15.0-rc4-syzkaller-00040-g8bac8898fe39 RIP: 0010:__bpf_prog_ret0_warn+0xa/0x20 kernel/bpf/core.c:2357 Call Trace: <TASK> bpf_dispatcher_nop_func include/linux/bpf.h:1316 [inline] __bpf_prog_run include/linux/filter.h:718 [inline] bpf_prog_run include/linux/filter.h:725 [inline] cls_bpf_classify+0x74a/0x1110 net/sched/cls_bpf.c:105 ...
When creating bpf program, 'fp->jit_requested' depends on bpf_jit_enable.
This issue is triggered because of CONFIG_BPF_JIT_ALWAYS_ON is not set
and bpf_jit_enable is set to 1, causing the arch to attempt JIT the prog,
but jit failed due to FAULT_INJECTION. As a result, incorrectly
treats the program as valid, when the program runs it calls
__bpf_prog_ret0_warn and triggers the WARN_ON_ONCE(1).
Linux >= fa9dd599b4dae841924b022768354cfde9affecb < e7fb4ebee6e900899d2b2e5852c3e2eafcbcad66Linux >= fa9dd599b4dae841924b022768354cfde9affecb < ef92b96530d1731d9ac167bc7c193c683cd78fffLinux >= fa9dd599b4dae841924b022768354cfde9affecb < 6f639c25bfad17d9fd7379ab91ff9678ea9aac85Linux >= fa9dd599b4dae841924b022768354cfde9affecb < 2bc6dffb4b72d53d6a6ada510269bf548c3f7ae0Linux >= fa9dd599b4dae841924b022768354cfde9affecb < 0b9bb52796b239de6792d0d68cdc6eb505ebff96Linux >= fa9dd599b4dae841924b022768354cfde9affecb < 86bc9c742426a16b52a10ef61f5b721aecca2344Linux 5124abda3060e2eab506fb14a27acadee3c3e396Linux 234646dcfc5f531c74ab20595e89eacd62e3611fLinux >= 4.9.190 < 4.10Linux >= 4.14.140 < 4.15Linux 4.16Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets