Skip to main content
VulnerabilityPublished Updated

CVE-2025-38280: Linux kernel · bpf: Avoid __bpf_prog_ret0_warn when jit fails

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ef92b96530d1731d9ac167bc7c193c683cd78fff : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:19 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in ef92b96530d1731d9ac167bc7c193c683cd78fff, e7fb4ebee6e900899d2b2e5852c3e2eafcbcad66, 86bc9c742426a16b52a10ef61f5b721aecca2344 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=4.9.190 <4.10
  • >=4.14.140 <4.15
Fixed in
  • ef92b96530d1731d9ac167bc7c193c683cd78fff
  • e7fb4ebee6e900899d2b2e5852c3e2eafcbcad66
  • 86bc9c742426a16b52a10ef61f5b721aecca2344
  • 6f639c25bfad17d9fd7379ab91ff9678ea9aac85
  • 4.15
  • 4.10
  • 2bc6dffb4b72d53d6a6ada510269bf548c3f7ae0
  • 0b9bb52796b239de6792d0d68cdc6eb505ebff96
LinuxLinuxAffected
  • =4.16
Fixed in–

Description

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).

References

Community reviews

Loading reviews…