CVE-2025-38280
BaseFortify
Publication date: 2025-07-10
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.16 (inc) to 6.1.142 (inc) |
| debian | debian_linux | 11.0 |
| linux | linux_kernel | 6.15.0-rc4 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's BPF (Berkeley Packet Filter) subsystem. When creating a BPF program, if the configuration option CONFIG_BPF_JIT_ALWAYS_ON is not set but bpf_jit_enable is set to 1, the system attempts to Just-In-Time (JIT) compile the BPF program. However, if the JIT compilation fails due to fault injection, the program is incorrectly treated as valid. When the program runs, it calls a warning function __bpf_prog_ret0_warn, which triggers a warning (WARN_ON_ONCE). This indicates improper handling of JIT failures leading to potential kernel warnings or instability.
How can this vulnerability impact me? :
This vulnerability can cause kernel warnings and potentially instability or unexpected behavior when running BPF programs that fail JIT compilation. Since the program is incorrectly treated as valid despite JIT failure, it may lead to unexpected kernel warnings or errors, which could affect system reliability or performance.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for warnings related to __bpf_prog_ret0_warn. You can check the kernel log messages using the command: dmesg | grep __bpf_prog_ret0_warn. Additionally, monitoring for WARN_ON_ONCE(1) triggers related to BPF JIT failures may help identify the issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include ensuring that the kernel configuration option CONFIG_BPF_JIT_ALWAYS_ON is set, or disabling bpf_jit_enable to prevent the kernel from attempting to JIT compile BPF programs when it may fail. Applying the kernel patch that fixes this issue is also recommended.