CVE-2026-23383: 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.
Security readout for executives and security teams
Plain-English summary
A Linux arm64 BPF JIT alignment flaw can make the kernel read a partially updated jump address during concurrent execution. The resulting corrupted jump could compromise system confidentiality, integrity, or availability. Exploitation requires local, low-privileged access according to the supplied CVSS assessment.
Executive priority
Treat this as a high-priority kernel update for arm64 fleets, especially shared systems or environments granting local access to untrusted users. It is serious but not supported as an emergency internet-wide exploitation event. Use vendor kernel mappings because the supplied affected-version information is not sufficiently precise for direct fleet decisions.
Technical view
The BPF JIT allocator may align its buffer to four bytes although bpf_plt.target is a 64-bit field. On arm64, the resulting misalignment can permit tearing when WRITE_ONCE updates the target while JIT-compiled code loads it. The fix requests eight-byte allocation alignment, ensuring atomic access to the target.
Likely exposure
Potential exposure is limited to arm64 Linux kernels containing the vulnerable BPF JIT allocation behavior. Systems permitting low-privileged local access warrant particular attention. The supplied affected-version data is ambiguous, so organizations should map distribution kernels and backports against the referenced fixes rather than rely only on version numbers.
Exploitation context
The supplied record assigns CVSS 7.8 with local access, low complexity, low privileges, and no user interaction. It is not listed as KEV, and the source bundle provides no evidence of active exploitation or a public exploit. Practical exploitability is not established by these sources.
Researcher notes
The security impact arises from possible non-atomic access to a misaligned 64-bit PLT target, not merely the UBSAN warning. A torn load could redirect JIT execution to a corrupted address. The sources identify the corrective alignment change but do not establish reliable exploitation, affected configuration prerequisites beyond arm64 BPF JIT behavior, or exact distribution package boundaries.
Mitigation direction
Apply a vendor-supported kernel update containing the referenced eight-byte JIT buffer alignment fix.
Consult the Linux distribution or appliance vendor for affected-build and backport guidance.
Prioritize arm64 systems accessible to untrusted or low-privileged local users.
Reboot into the corrected kernel after updating, following vendor operational guidance.
Validation and detection
Confirm each system's architecture, running kernel build, and distribution package revision.
Compare vendor kernel backports with the four referenced stable-kernel commits.
Verify the corrected kernel is running after maintenance and reboot.
Review kernel diagnostics for BPF JIT misaligned-access or UBSAN warnings.
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-2026-23383 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
5Source 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.