CVE-2026-23383bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing
- 7.8HighCVSS base score
- 0.18%Exploitation in 30 daysEPSS · top 92% 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: Force 8-byte alignment for JIT buffer to prevent atomic tearing struct bpf_plt contains a u64 target field. Currently, the BPF JIT allocator requests an alignment of 4 bytes (sizeof(u32)) for the JIT buffer. Because the base address of the JIT buffer can be 4-byte aligned (e.g., ending in 0x4 or 0xc), the relative padding logic in build_plt() fails to ensure that target lands on an 8-byte boundary. This leads to two issues: 1. UBSAN reports misaligned-access warnings when dereferencing the structure. 2. More critically, target is updated concurrently via WRITE_ONCE() in bpf_arch_text_poke() while the JIT'd code executes ldr. On arm64, 64-bit loads/stores are only guaranteed to be single-copy atomic if they are 64-bit aligned. A misaligned target risks a torn read, causing the JIT to jump to a corrupted address. Fix this by increasing the allocation alignment requirement to 8 bytes (sizeof(u64)) in bpf_jit_binary_pack_alloc(). This anchors the base of the JIT buffer to an 8-byte boundary, allowing the relative padding math in build_plt() to correctly align the target field.
Timeline
ID reserved
By Linux
- 2 months later
· 2 months later
Published
- 7 months later
· 7 months 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 · Modified | 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.18% · top 92% of all CVEs (18 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 b2ad54e1533e91449cb2a371e034942bd7882b58 – < fcb9c6275f712860c22c96a472b73d05cabb75cd
- affected b2ad54e1533e91449cb2a371e034942bd7882b58 – < f5a41b61b5faae1965a5a2cb55322fe8f17e3b2d
- affected b2ad54e1533e91449cb2a371e034942bd7882b58 – < 80ad264da02cc4aee718e799c2b79f0f834673dc
- affected b2ad54e1533e91449cb2a371e034942bd7882b58 – < 519b1ad91de5bf7a496f2b858e9212db6328e1de
- affected b2ad54e1533e91449cb2a371e034942bd7882b58 – < 66959ed481a474eaae278c7f6860a2a9b188a4d6
- affected b2ad54e1533e91449cb2a371e034942bd7882b58 – < ef06fd16d48704eac868441d98d4ef083d8f3d07
- affected 6.0
- unaffected < 6.0
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.77 – ≤ 6.12.*
- unaffected 6.18.17 – ≤ 6.18.*
- unaffected 6.19.7 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/fcb9c6275f712860c22c96a472b73d05cabb75cd (opens in a new tab)
- https://git.kernel.org/stable/c/f5a41b61b5faae1965a5a2cb55322fe8f17e3b2d (opens in a new tab)
- https://git.kernel.org/stable/c/80ad264da02cc4aee718e799c2b79f0f834673dc (opens in a new tab)
- https://git.kernel.org/stable/c/519b1ad91de5bf7a496f2b858e9212db6328e1de (opens in a new tab)
- https://git.kernel.org/stable/c/66959ed481a474eaae278c7f6860a2a9b188a4d6 (opens in a new tab)
- https://git.kernel.org/stable/c/ef06fd16d48704eac868441d98d4ef083d8f3d07 (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-15378 (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-23383)Record last updated .