bpf: Fix overflow of jump offset in constant blinding
Summary
| CVE | CVE-2026-98816 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-18 16:17:35 UTC |
| Updated | 2026-10-19 10:19:45 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix overflow of jump offset in constant blinding
bpf_jit_blind_insn() rewrites 'if rX op imm goto off' into:
AX = imm ^ rnd
AX ^= rnd
if rX op AX goto off
and subtracts 2 from off when the jump is backward. off is s16, so
-32767 and -32768 wrap and the jump goes 32767 insns forward, past the
end of the prog. The jump is inside the patch, hence bpf_adj_branches()
doesn't check it. The kernel crashes when such prog runs with
bpf_jit_harden=2.
Return -ERANGE in such case. bpf_jit_blind_constants() fails the same
way when blinding of other insns moves a jump out of range. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 4f3446bb809f20ad56cadf712e6006815ae7a8f9 443328237113ee0ea515e506497334d871dbc2aa git |
Not specified |
| CNA |
Linux |
Linux |
affected 4f3446bb809f20ad56cadf712e6006815ae7a8f9 ad139384ecddb6f3e7e3c3c12765aafae0e39670 git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.7 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.7 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.10 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/443328237113ee0ea515e506497334d871dbc2aa |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ad139384ecddb6f3e7e3c3c12765aafae0e39670 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.