BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-23383High confidence

bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 205 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 205 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 21 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-23383 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing
184 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's BPF (Berkeley Packet Filter) JIT (Just-In-Time) compiler on arm64 architectures. The BPF JIT allocator incorrectly requests a 4-byte alignment for its buffer, while a critical `target` field within the `bpf_plt` structure requires 8-byte alignment. This misalignment can lead to a "torn read" when the `target` field is updated concurrently, causing the JIT to jump to a corrupted memory address. An attacker could potentially exploit this vulnerability to achieve arbitrary code execution.
Remediation
Fix deferred
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-15378

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 205 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0861Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260401Security Bulletin 01 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 01 Apr 2026, published on 1 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-23369 Référence CVE CVE-2026-23370 https://www.cve.org/CVERecord?id=CVE-2026-23370 Référence CVE CVE-2026-23372 https://www.cve.org/CVERecord?id=CVE-2026-23372 Référence CVE CVE-2026-23374 https://www.cve.org/CVERecord?id=CVE-2026-23374 Référence CVE CVE-2026-23375 https://www.cve.org/CVERecord?id=CVE-2026-23375 Référence CVE CVE-2026-23378 https://www.cve.org/CVERecord?id=CVE-2026-23378 Référence CVE CVE-2026-23379 https://www.cve.org/CVERecord?id=CVE-2026-23379 Référence CVE CVE-2026-23381 https://www.cve.org/CVERecord?id=CVE-2026-23381 Référence CVE CVE-2026-23382 https://www.cve.org/CVERecord?id=CVE-2026-23382 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23386 https://www.cve.org/CVERecord?id=CVE-2026-23386 Référence CVE CVE-2026-23387 https://www.cve.org/CVERecord?id=CVE-2026-23387 Référence CVE CVE-2026-23388 https://www.cve.org/CVERecord?id=CVE-2026-23388 Référence CVE CVE-2026-23389 https://www.cve.org/CVERecord?id=CVE-2026-23389 Référence CVE CVE-2026-23391 https://www.cve.org/CVERecord?id=CVE-2026-23391 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23395 https://www.cve.org/CVERecord?id=CVE-2026-23395 Référence CVE CVE-2026-23396 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-23369 Référence CVE CVE-2026-23370 https://www.cve.org/CVERecord?id=CVE-2026-23370 Référence CVE CVE-2026-23372 https://www.cve.org/CVERecord?id=CVE-2026-23372 Référence CVE CVE-2026-23374 https://www.cve.org/CVERecord?id=CVE-2026-23374 Référence CVE CVE-2026-23375 https://www.cve.org/CVERecord?id=CVE-2026-23375 Référence CVE CVE-2026-23378 https://www.cve.org/CVERecord?id=CVE-2026-23378 Référence CVE CVE-2026-23379 https://www.cve.org/CVERecord?id=CVE-2026-23379 Référence CVE CVE-2026-23381 https://www.cve.org/CVERecord?id=CVE-2026-23381 Référence CVE CVE-2026-23382 https://www.cve.org/CVERecord?id=CVE-2026-23382 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23386 https://www.cve.org/CVERecord?id=CVE-2026-23386 Référence CVE CVE-2026-23387 https://www.cve.org/CVERecord?id=CVE-2026-23387 Référence CVE CVE-2026-23388 https://www.cve.org/CVERecord?id=CVE-2026-23388 Référence CVE CVE-2026-23389 https://www.cve.org/CVERecord?id=CVE-2026-23389 Référence CVE CVE-2026-23391 https://www.cve.org/CVERecord?id=CVE-2026-23391 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23395 https://www.cve.org/CVERecord?id=CVE-2026-23395 Référence CVE CVE-2026-23396 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-23369 Référence CVE CVE-2026-23370 https://www.cve.org/CVERecord?id=CVE-2026-23370 Référence CVE CVE-2026-23372 https://www.cve.org/CVERecord?id=CVE-2026-23372 Référence CVE CVE-2026-23374 https://www.cve.org/CVERecord?id=CVE-2026-23374 Référence CVE CVE-2026-23375 https://www.cve.org/CVERecord?id=CVE-2026-23375 Référence CVE CVE-2026-23378 https://www.cve.org/CVERecord?id=CVE-2026-23378 Référence CVE CVE-2026-23379 https://www.cve.org/CVERecord?id=CVE-2026-23379 Référence CVE CVE-2026-23381 https://www.cve.org/CVERecord?id=CVE-2026-23381 Référence CVE CVE-2026-23382 https://www.cve.org/CVERecord?id=CVE-2026-23382 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23386 https://www.cve.org/CVERecord?id=CVE-2026-23386 Référence CVE CVE-2026-23387 https://www.cve.org/CVERecord?id=CVE-2026-23387 Référence CVE CVE-2026-23388 https://www.cve.org/CVERecord?id=CVE-2026-23388 Référence CVE CVE-2026-23389 https://www.cve.org/CVERecord?id=CVE-2026-23389 Référence CVE CVE-2026-23391 https://www.cve.org/CVERecord?id=CVE-2026-23391 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23395 https://www.cve.org/CVERecord?id=CVE-2026-23395 Référence CVE CVE-2026-23396 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0697Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-23368 Référence CVE CVE-2026-23369 https://www.cve.org/CVERecord?id=CVE-2026-23369 Référence CVE CVE-2026-23370 https://www.cve.org/CVERecord?id=CVE-2026-23370 Référence CVE CVE-2026-23372 https://www.cve.org/CVERecord?id=CVE-2026-23372 Référence CVE CVE-2026-23373 https://www.cve.org/CVERecord?id=CVE-2026-23373 Référence CVE CVE-2026-23374 https://www.cve.org/CVERecord?id=CVE-2026-23374 Référence CVE CVE-2026-23375 https://www.cve.org/CVERecord?id=CVE-2026-23375 Référence CVE CVE-2026-23378 https://www.cve.org/CVERecord?id=CVE-2026-23378 Référence CVE CVE-2026-23382 https://www.cve.org/CVERecord?id=CVE-2026-23382 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23387 https://www.cve.org/CVERecord?id=CVE-2026-23387 Référence CVE CVE-2026-23391 https://www.cve.org/CVERecord?id=CVE-2026-23391 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23393 https://www.cve.org/CVERecord?id=CVE-2026-23393 Référence CVE CVE-2026-23395 https://www.cve.org/CVERecord?id=CVE-2026-23395 Référence CVE CVE-2026-23396 https://www.cve.org/CVERecord?id=CVE-2026-23396 Référence CVE CVE-2026-23397 https://www.cve.org/CVERecord?id=CVE-2026-23397 Référence CVE CVE-2026-23399 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0548Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2026-23372 Référence CVE CVE-2026-23373 https://www.cve.org/CVERecord?id=CVE-2026-23373 Référence CVE CVE-2026-23374 https://www.cve.org/CVERecord?id=CVE-2026-23374 Référence CVE CVE-2026-23375 https://www.cve.org/CVERecord?id=CVE-2026-23375 Référence CVE CVE-2026-23378 https://www.cve.org/CVERecord?id=CVE-2026-23378 Référence CVE CVE-2026-23379 https://www.cve.org/CVERecord?id=CVE-2026-23379 Référence CVE CVE-2026-23380 https://www.cve.org/CVERecord?id=CVE-2026-23380 Référence CVE CVE-2026-23381 https://www.cve.org/CVERecord?id=CVE-2026-23381 Référence CVE CVE-2026-23382 https://www.cve.org/CVERecord?id=CVE-2026-23382 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23386 https://www.cve.org/CVERecord?id=CVE-2026-23386 Référence CVE CVE-2026-23387 https://www.cve.org/CVERecord?id=CVE-2026-23387 Référence CVE CVE-2026-23388 https://www.cve.org/CVERecord?id=CVE-2026-23388 Référence CVE CVE-2026-23389 https://www.cve.org/CVERecord?id=CVE-2026-23389 Référence CVE CVE-2026-23391 https://www.cve.org/CVERecord?id=CVE-2026-23391 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23393 https://www.cve.org/CVERecord?id=CVE-2026-23393 Référence CVE CVE-2026-23395 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0497Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-23304 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23319 https://www.cve.org/CVERecord?id=CVE-2026-23319 Référence CVE CVE-2026-23326 https://www.cve.org/CVERecord?id=CVE-2026-23326 Référence CVE CVE-2026-23335 https://www.cve.org/CVERecord?id=CVE-2026-23335 Référence CVE CVE-2026-23343 https://www.cve.org/CVERecord?id=CVE-2026-23343 Référence CVE CVE-2026-23361 https://www.cve.org/CVERecord?id=CVE-2026-23361 Référence CVE CVE-2026-23379 https://www.cve.org/CVERecord?id=CVE-2026-23379 Référence CVE CVE-2026-23381 https://www.cve.org/CVERecord?id=CVE-2026-23381 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23386 https://www.cve.org/CVERecord?id=CVE-2026-23386 Référence CVE CVE-2026-23393 https://www.cve.org/CVERecord?id=CVE-2026-23393 Référence CVE CVE-2026-23395 https://www.cve.org/CVERecord?id=CVE-2026-23395 Référence CVE CVE-2026-23398 https://www.cve.org/CVERecord?id=CVE-2026-23398 Référence CVE CVE-2026-23412 https://www.cve.org/CVERecord?id=CVE-2026-23412 Référence CVE CVE-2026-23413 https://www.cve.org/CVERecord?id=CVE-2026-23413 Référence CVE CVE-2026-23414 https://www.cve.org/CVERecord?id=CVE-2026-23414 Référence CVE CVE-2026-23419 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-012715LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。bpf、arm64では、アトミックな破綻を防ぐためにJITバッファの8バイトアラインメントを強制します。struct bpf_pltにはu64型のtargetフィールドが含まれています。現在、BPF JITアロケータはJITバッファに対して4バイト（sizeof(u32)）のアラインメントを要求しています。JITバッファの基底アドレスは4バイトアラインメント（例：0x4または0xcで終わる）となることがあり、これによりbuild_plt()内の相対パディングロジックがtargetを8バイト境界に配置できない場合があります。これにより、以下の2つの問題が発生します。1. 構造体を参照するときにUBSANがアライメント違反の警告を報告します。2. より重大な問題として、bpf_arch_text_poke()内でWRITE_ONCE()を介してtargetが同時に更新される一方で、JITされたコードがldr命令を実行します。arm64では64ビットのロード/ストアは64ビット境界にアラインされている場合のみ単一コピーのアトミック性が保証されます。アラインメントがずれたtargetは破損した読み込み（トーン読み込み）を引き起こし、JITが破損したアドレスにジャンプする恐れがあります。この問題はbpf_jit_binary_pack_alloc()における割り当てアラインメント要件を8バイト（sizeof(u64)）に引き上げることで修正しました。これによりJITバッファの基底が8バイト境界に固定され、build_plt()内の相対パディング計算によってtargetフィールドを正しくアラインできます。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.0, 6.12.77 ≤ 6.12.*, 6.18.17 ≤ 6.18.*, 6.19.7 ≤ 6.19.*, 7.0 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 25 Mar 2026 · Last source change 5 Aug 2026, 12:21 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-15378
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-15378↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-23383 · cve.blacktree.nl