CVE-2025-38607: bpf: handle jset (if a & b ...) as a jump in CFG computation
In the Linux kernel, the following vulnerability has been resolved:
bpf: handle jset (if a & b ...) as a jump in CFG computation
BPF_JSET is a conditional jump and currently verifier.c:can_jump()
does not know about that. This can lead to incorrect live registers
and SCC computation.
E.g. in the following example:
1: r0 = 1;
2: r2 = 2;
3: if r1 & 0x7 goto +1;
4: exit;
5: r0 = r2;
6: exit;
W/o this fix insn_successors(3) will return only (4), a jump to (5)
would be missed and r2 won't be marked as alive at (3).
Security readout for executives and security teams
Plain-English summary
A Linux kernel BPF verifier error can misread a conditional branch, producing an incorrect view of which registers remain live. The supplied CVSS assessment indicates that a local attacker with low privileges could potentially compromise confidentiality, integrity, and availability. Exposure depends on the running kernel and whether the affected BPF verifier path is reachable.
Executive priority
Treat as a high-priority kernel maintenance issue, especially on multi-user, development, hosting, or untrusted-workload systems. It is not evidenced as an internet-scale emergency, but the stated potential impact spans data confidentiality, system integrity, and availability. Schedule prompt tested patching through normal kernel-update procedures.
Technical view
The verifier’s control-flow graph logic did not treat BPF_JSET as a conditional jump. Consequently, successor analysis could omit the taken branch, corrupting live-register and strongly connected component calculations. The Linux kernel project resolved the flaw through the referenced stable commits.
Likely exposure
The bundle identifies Linux versions 6.15, 6.15.10, 6.16.1, and 6.17 as affected; it also contains an ambiguous “0” entry. Confirm exact exposure through distribution advisories and fix backport records rather than version numbers alone. The CVSS vector describes a local, low-privilege attack requiring no user interaction.
Exploitation context
The bundle does not establish active exploitation, and the CVE is not listed as KEV. No public exploit evidence is supplied. The CVSS vector indicates local access and low privileges, so this is primarily a post-access privilege-boundary risk rather than a directly remote entry point.
Researcher notes
The security consequence arises from incomplete CFG successor enumeration for BPF_JSET. Missing the taken edge can distort liveness and SCC computation in the verifier. The supplied material does not demonstrate a reliable exploitation chain, identify a CWE, or map each fix commit to specific release branches; downstream backport verification is therefore essential.
Mitigation direction
Install a vendor kernel update containing the applicable referenced stable fix.
Consult distribution guidance to identify patched package versions and backports.
Reboot affected systems into the updated kernel after deployment.
Prioritize shared or untrusted-workload systems where local users may exercise BPF functionality.
Validation and detection
Inventory active kernel versions, not merely installed kernel packages.
Confirm the running kernel includes the applicable stable fix or vendor backport.
Verify systems restarted successfully into the remediated kernel.
Review vendor advisories for affected-version interpretations and package-specific status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38607 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.