CVE-2026-53036bpf, arm64: Fix off-by-one in check_imm signed range check
- 7.8HighCVSS base score
- 0.14%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Fix off-by-one in check_imm signed range check check_imm(bits, imm) is used in the arm64 BPF JIT to verify that a branch displacement (in arm64 instruction units) fits into the signed N-bit immediate field of a B, B.cond or CBZ/CBNZ encoding before it is handed to the encoder. The macro currently tests for (imm > 0 && imm >> bits) || (imm < 0 && ~imm >> bits) which admits values in [-2^N, 2^N) — effectively a signed (N+1)-bit range. A signed N-bit field only holds [-2^(N-1), 2^(N-1)), so the check admits one extra bit of range on each side. In particular, for check_imm19(), values in [2^18, 2^19) slip past the check but do not fit into the 19-bit signed imm19 field of B.cond. aarch64_insn_encode_immediate() then masks the raw value into the 19-bit field, setting bit 18 (the sign bit) and flipping a forward branch into a backward one. Same class of issue exists for check_imm26() and the B/BL encoding. Shift by (bits - 1) instead of bits so the actual signed N-bit range is enforced.
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 42 days later
· 42 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.14% · top 97% of all CVEs (19 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected e54bcde3d69d40023ae77727213d14f920eb264a – < a5dfeb3b61065039488342d43ae06d4729d955d4
- affected e54bcde3d69d40023ae77727213d14f920eb264a – < 7fd3b41260c6120e7b60164afea5d961af6224f9
- affected e54bcde3d69d40023ae77727213d14f920eb264a – < 6927f0d6794aa73318bbfa929f1ff6065b0620df
- affected e54bcde3d69d40023ae77727213d14f920eb264a – < 1a113b5497297871699cd498b1b83542e0db7f15
- affected e54bcde3d69d40023ae77727213d14f920eb264a – < fb74defa1cca1a73177c0c761e641332e4f979a3
- affected e54bcde3d69d40023ae77727213d14f920eb264a – < 1dd8be4ec722ce54e4cace59f3a4ba658111b3ec
- affected 3.18
- unaffected < 3.18
- unaffected 6.1.175 – ≤ 6.1.*
- unaffected 6.6.141 – ≤ 6.6.*
- unaffected 6.12.91 – ≤ 6.12.*
- unaffected 6.18.33 – ≤ 6.18.*
- unaffected 7.0.10 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References6
- https://git.kernel.org/stable/c/a5dfeb3b61065039488342d43ae06d4729d955d4 (opens in a new tab)
- https://git.kernel.org/stable/c/7fd3b41260c6120e7b60164afea5d961af6224f9 (opens in a new tab)
- https://git.kernel.org/stable/c/6927f0d6794aa73318bbfa929f1ff6065b0620df (opens in a new tab)
- https://git.kernel.org/stable/c/1a113b5497297871699cd498b1b83542e0db7f15 (opens in a new tab)
- https://git.kernel.org/stable/c/fb74defa1cca1a73177c0c761e641332e4f979a3 (opens in a new tab)
- https://git.kernel.org/stable/c/1dd8be4ec722ce54e4cace59f3a4ba658111b3ec (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-38904 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-53036)Record last updated .