CVE-2025-38280
bpf: Avoid __bpf_prog_ret0_warn when jit fails
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).
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ fa9dd599b4dae841924b022768354cfde9affecb; < e7fb4ebee6e900899d2b2e5852c3e2eafcbcad66 (affected, git) ≥ fa9dd599b4dae841924b022768354cfde9affecb; < ef92b96530d1731d9ac167bc7c193c683cd78fff (affected, git) ≥ fa9dd599b4dae841924b022768354cfde9affecb; < 6f639c25bfad17d9fd7379ab91ff9678ea9aac85 (affected, git) ≥ fa9dd599b4dae841924b022768354cfde9affecb; < 2bc6dffb4b72d53d6a6ada510269bf548c3f7ae0 (affected, git) ≥ fa9dd599b4dae841924b022768354cfde9affecb; < 0b9bb52796b239de6792d0d68cdc6eb505ebff96 (affected, git) ≥ fa9dd599b4dae841924b022768354cfde9affecb; < 86bc9c742426a16b52a10ef61f5b721aecca2344 (affected, git) 5124abda3060e2eab506fb14a27acadee3c3e396 (affected, git) 234646dcfc5f531c74ab20595e89eacd62e3611f (affected, git) ≥ 4.9.190; < 4.10 (affected, semver) ≥ 4.14.140; < 4.15 (affected, semver) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
4.16 (affected) ≥ 0; < 4.16 (unaffected, semver) ≥ 5.15.186; ≤ 5.15.* (unaffected, semver) ≥ 6.1.142; ≤ 6.1.* (unaffected, semver) ≥ 6.6.94; ≤ 6.6.* (unaffected, semver) ≥ 6.12.34; ≤ 6.12.* (unaffected, semver) ≥ 6.15.3; ≤ 6.15.* (unaffected, semver) ≥ 6.16; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
| SIMATIC S7-1500 CPU 1518-4 PN/DP MFP Siemens |
≥ V3.1.5; < * (affected, custom)
Other versions: unknown |
ADP: siemens-SADP |
| SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP Siemens |
≥ V3.1.5; < * (affected, custom)
Other versions: unknown |
ADP: siemens-SADP |
| SIPLUS S7-1500 CPU 1518-4 PN/DP MFP Siemens |
≥ V3.1.5; < * (affected, custom)
Other versions: unknown |
ADP: siemens-SADP |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/e7fb4ebee6e900899d2b2e5852c3e2eafcbcad66CNA: Linux
- https://git.kernel.org/stable/c/ef92b96530d1731d9ac167bc7c193c683cd78fffCNA: Linux
- https://git.kernel.org/stable/c/6f639c25bfad17d9fd7379ab91ff9678ea9aac85CNA: Linux
- https://git.kernel.org/stable/c/2bc6dffb4b72d53d6a6ada510269bf548c3f7ae0CNA: Linux
- https://git.kernel.org/stable/c/0b9bb52796b239de6792d0d68cdc6eb505ebff96CNA: Linux
- https://git.kernel.org/stable/c/86bc9c742426a16b52a10ef61f5b721aecca2344CNA: Linux
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlADP: CVE
- https://cert-portal.siemens.com/productcert/html/ssa-082556.htmlADP: siemens-SADP
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.