CVE-2025-39748 Details
Description
In the Linux kernel, the following vulnerability has been resolved: bpf: Forget ranges when refining tnum after JSET Syzbot reported a kernel warning due to a range invariant violation on the following BPF program. 0: call bpf_get_netns_cookie 1: if r0 == 0 goto <exit> 2: if r0 & Oxffffffff goto <exit> The issue is on the path where we fall through both jumps. That path is unreachable at runtime: after insn 1, we know r0 != 0, but with the sign extension on the jset, we would only fallthrough insn 2 if r0 == 0. Unfortunately, is_branch_taken() isn't currently able to figure this out, so the verifier walks all branches. The verifier then refines the register bounds using the second condition and we end up with inconsistent bounds on this unreachable path: 1: if r0 == 0 goto <exit> r0: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0xffffffffffffffff) 2: if r0 & 0xffffffff goto <exit> r0 before reg_bounds_sync: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0) r0 after reg_bounds_sync: u64=[0x1, 0] var_off=(0, 0) Improving the range refinement for JSET to cover all cases is tricky. We also don't expect many users to rely on JSET given LLVM doesn't generate those instructions. So instead of improving the range refinement for JSETs, Eduard suggested we forget the ranges whenever we're narrowing tnums after a JSET. This patch implements that approach.
A vulnerability in the Linux kernel's BPF verifier has been addressed. This issue arose from an incorrect range refinement after processing JSET instructions, leading to a violation of range invariants. The vulnerability was triggered by a specific BPF program that, due to the sign extension of a JSET, created an unreachable path. The verifier, unable to accurately assess branch conditions, walked through all branches, resulting in inconsistent register bounds. The vulnerability has been resolved by modifying the verifier to disregard certain range refinements after JSETs, preventing the introduction of invariant violations on dead branches.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | < 6.12.43 >= 6.13, < 6.15.11 >= 6.16, < 6.16.2 |
CPE
Remediation
| |
Change History
11 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 10, 2026 | CVE Modified | siemens-SADP |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Oct 19, 2026 | CVE Translated | [email protected] |
| Oct 15, 2026 | CVE Modified | kernel.org |
| Oct 15, 2026 | CVE Modified | siemens-SADP |
| Jul 14, 2026 | CVE Modified | siemens-SADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Apr 18, 2026 | CVE Modified | kernel.org |
| Mar 25, 2026 | CVE Modified | kernel.org |
| Nov 25, 2025 | Initial Analysis | [email protected] |
| Sep 11, 2025 | New CVE Received | kernel.org |