CVE-2026-23383
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| b2ad54e1533e91449cb2a371e034942bd7882b58 | affected | git | f5a41b61b5faae1965a5a2cb55322fe8f17e3b2d | Unavailable | None listed |
| b2ad54e1533e91449cb2a371e034942bd7882b58 | affected | git | 80ad264da02cc4aee718e799c2b79f0f834673dc | Unavailable | None listed |
| b2ad54e1533e91449cb2a371e034942bd7882b58 | affected | git | 519b1ad91de5bf7a496f2b858e9212db6328e1de | Unavailable | None listed |
| b2ad54e1533e91449cb2a371e034942bd7882b58 | affected | git | 66959ed481a474eaae278c7f6860a2a9b188a4d6 | Unavailable | None listed |
| b2ad54e1533e91449cb2a371e034942bd7882b58 | affected | git | ef06fd16d48704eac868441d98d4ef083d8f3d07 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 6.0 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 6.0 | Unavailable | None listed |
| 6.6.160 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.77 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.18.17 | unaffected | semver | Unavailable | 6.18.* | None listed |
| 6.19.7 | unaffected | semver | Unavailable | 6.19.* | None listed |
| 7.0 | unaffected | original_commit_for_fix | Unavailable | * | None listed |