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

bpf: Fix stale offload->prog pointer after constant blinding

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 20 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 20 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 20 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.94-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 7 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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-53094 · CSAF 2.0 · revision 10 · interimSUSE Product Security TeamCVE-2026-53094
366 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix stale offload->prog pointer after constant blinding When a dev-bound-only BPF program (BPF_F_XDP_DEV_BOUND_ONLY) undergoes JIT compilation with constant blinding enabled (bpf_jit_harden >= 2), bpf_jit_blind_constants() clones the program. The original prog is then freed in bpf_jit_prog_release_other(), which updates aux->prog to point to the surviving clone, but fails to update offload->prog. This leaves offload->prog pointing to the freed original program. When the network namespace is subsequently destroyed, cleanup_net() triggers bpf_dev_bound_netdev_unregister(), which iterates ondev->progs and calls __bpf_prog_offload_destroy(offload->prog). Accessing the freed prog causes a page fault: BUG: unable to handle page fault for address: ffffc900085f1038 Workqueue: netns cleanup_net RIP: 0010:__bpf_prog_offload_destroy+0xc/0x80 Call Trace: __bpf_offload_dev_netdev_unregister+0x257/0x350 bpf_dev_bound_netdev_unregister+0x4a/0x90 unregister_netdevice_many_notify+0x2a2/0x660 ... cleanup_net+0x21a/0x320 The test sequence that triggers this reliably is: 1. Set net.core.bpf_jit_harden=2 (echo 2 > /proc/sys/net/core/bpf_jit_harden) 2. Run xdp_metadata selftest, which creates a dev-bound-only XDP program on a veth inside a netns (./test_progs -t xdp_metadata) 3. cleanup_net -> page fault in __bpf_prog_offload_destroy Dev-bound-only programs are unique in that they have an offload structure but go through the normal JIT path instead of bpf_prog_offload_compile(). This means they are subject to constant blinding's prog clone-and-replace, while also having offload->prog that must stay in sync. Fix this by updating offload->prog in bpf_jit_prog_release_other(), alongside the existing aux->prog update. Both are back-pointers to the prog that must be kept in sync when the prog is replaced.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-38962

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 20 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: Fix stale offload->prog pointer after constant blinding When a dev-bound-only BPF program (BPF_F_XDP_DEV_BOUND_ONLY) undergoes JIT compilation with constant blinding enabled (bpf_jit_harden >= 2), bpf_jit_blind_constants() clones the program. The original prog is then freed in bpf_jit_prog_release_other(), which updates aux->prog to point to the surviving clone, but fails to update offload->prog. This leaves offload->prog pointing to the freed original program. When the network namespace is subsequently destroyed, cleanup_net() triggers bpf_dev_bound_netdev_unregister(), which iterates ondev->progs and calls __bpf_prog_offload_destroy(offload->prog). Accessing the freed prog causes a page fault: BUG: unable to handle page fault for address: ffffc900085f1038 Workqueue: netns cleanup_net RIP: 0010:__bpf_prog_offload_destroy+0xc/0x80 Call Trace: __bpf_offload_dev_netdev_unregister+0x257/0x350 bpf_dev_bound_netdev_unregister+0x4a/0x90 unregister_netdevice_many_notify+0x2a2/0x660 ... cleanup_net+0x21a/0x320 The test sequence that triggers this reliably is: 1. Set net.core.bpf_jit_harden=2 (echo 2 > /proc/sys/net/core/bpf_jit_harden) 2. Run xdp_metadata selftest, which creates a dev-bound-only XDP program on a veth inside a netns (./test_progs -t xdp_metadata) 3. cleanup_net -> page fault in __bpf_prog_offload_destroy Dev-bound-only programs are unique in that they have an offload structure but go through the normal JIT path instead of bpf_prog_offload_compile(). This means they are subject to constant blinding's prog clone-and-replace, while also having offload->prog that must stay in sync. Fix this by updating offload->prog in bpf_jit_prog_release_other(), alongside the existing aux->prog update. Both are back-pointers to the prog that must be kept in sync when the prog is replaced.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix stale offload->prog pointer after constant blinding When a dev-bound-only BPF program (BPF_F_XDP_DEV_BOUND_ONLY) undergoes JIT compilation with constant blinding enabled (bpf_jit_harden >= 2), bpf_jit_blind_constants() clones the program. The original prog is then freed in bpf_jit_prog_release_other(), which updates aux->prog to point to the surviving clone, but fails to update offload->prog. This leaves offload->prog pointing to the freed original program. When the network namespace is subsequently destroyed, cleanup_net() triggers bpf_dev_bound_netdev_unregister(), which iterates ondev->progs and calls __bpf_prog_offload_destroy(offload->prog). Accessing the freed prog causes a page fault: BUG: unable to handle page fault for address: ffffc900085f1038 Workqueue: netns cleanup_net RIP: 0010:__bpf_prog_offload_destroy+0xc/0x80 Call Trace: __bpf_offload_dev_netdev_unregister+0x257/0x350 bpf_dev_bound_netdev_unregister+0x4a/0x90 unregister_netdevice_many_notify+0x2a2/0x660 ... cleanup_net+0x21a/0x320 The test sequence that triggers this reliably is: 1. Set net.core.bpf_jit_harden=2 (echo 2 > /proc/sys/net/core/bpf_jit_harden) 2. Run xdp_metadata selftest, which creates a dev-bound-only XDP program on a veth inside a netns (./test_progs -t xdp_metadata) 3. cleanup_net -> page fault in __bpf_prog_offload_destroy Dev-bound-only programs are unique in that they have an offload structure but go through the normal JIT path instead of bpf_prog_offload_compile(). This means they are subject to constant blinding's prog clone-and-replace, while also having offload->prog that must stay in sync. Fix this by updating offload->prog in bpf_jit_prog_release_other(), alongside the existing aux->prog update. Both are back-pointers to the prog that must be kept in sync when the prog is replaced.

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: Fix stale offload->prog pointer after constant blinding When a dev-bound-only BPF program (BPF_F_XDP_DEV_BOUND_ONLY) undergoes JIT compilation with constant blinding enabled (bpf_jit_harden >= 2), bpf_jit_blind_constants() clones the program. The original prog is then freed in bpf_jit_prog_release_other(), which updates aux->prog to point to the surviving clone, but fails to update offload->prog. This leaves offload->prog pointing to the freed original program. When the network namespace is subsequently destroyed, cleanup_net() triggers bpf_dev_bound_netdev_unregister(), which iterates ondev->progs and calls __bpf_prog_offload_destroy(offload->prog). Accessing the freed prog causes a page fault: BUG: unable to handle page fault for address: ffffc900085f1038 Workqueue: netns cleanup_net RIP: 0010:__bpf_prog_offload_destroy+0xc/0x80 Call Trace: __bpf_offload_dev_netdev_unregister+0x257/0x350 bpf_dev_bound_netdev_unregister+0x4a/0x90 unregister_netdevice_many_notify+0x2a2/0x660 ... cleanup_net+0x21a/0x320 The test sequence that triggers this reliably is: 1. Set net.core.bpf_jit_harden=2 (echo 2 > /proc/sys/net/core/bpf_jit_harden) 2. Run xdp_metadata selftest, which creates a dev-bound-only XDP program on a veth inside a netns (./test_progs -t xdp_metadata) 3. cleanup_net -> page fault in __bpf_prog_offload_destroy Dev-bound-only programs are unique in that they have an offload structure but go through the normal JIT path instead of bpf_prog_offload_compile(). This means they are subject to constant blinding's prog clone-and-replace, while also having offload->prog that must stay in sync. Fix this by updating offload->prog in bpf_jit_prog_release_other(), alongside the existing aux->prog update. Both are back-pointers to the prog that must be kept in sync when the prog is replaced.

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-2077Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

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

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

d?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 https://www.cve.org/CVERecord?id=CVE-2026-53098 Référence CVE CVE-2026-53099 https://www.cve.org/CVERecord?id=CVE-2026-53099 Référence CVE CVE-2026-53100 https://www.cve.org/CVERecord?id=CVE-2026-53100 Référence CVE CVE-2026-53101 https://www.cve.org/CVERecord?id=CVE-2026-53101 Référence CVE CVE-2026-53102 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53034 Référence CVE CVE-2026-53048 https://www.cve.org/CVERecord?id=CVE-2026-53048 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53061 https://www.cve.org/CVERecord?id=CVE-2026-53061 Référence CVE CVE-2026-53076 https://www.cve.org/CVERecord?id=CVE-2026-53076 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53109 https://www.cve.org/CVERecord?id=CVE-2026-53109 Référence CVE CVE-2026-53110 https://www.cve.org/CVERecord?id=CVE-2026-53110 Référence CVE CVE-2026-53111 https://www.cve.org/CVERecord?id=CVE-2026-53111 Référence CVE CVE-2026-53114 https://www.cve.org/CVERecord?id=CVE-2026-53114 Référence CVE CVE-2026-53126 https://www.cve.org/CVERecord?id=CVE-2026-53126 Référence CVE CVE-2026-53129 https://www.cve.org/CVERecord?id=CVE-2026-53129 Référence CVE CVE-2026-53142 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 https://www.cve.org/CVERecord?id=CVE-2026-53098 Référence CVE CVE-2026-53099 https://www.cve.org/CVERecord?id=CVE-2026-53099 Référence CVE CVE-2026-53100 https://www.cve.org/CVERecord?id=CVE-2026-53100 Référence CVE CVE-2026-53101 https://www.cve.org/CVERecord?id=CVE-2026-53101 Référence CVE CVE-2026-53102 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52994 Référence CVE CVE-2026-53001 https://www.cve.org/CVERecord?id=CVE-2026-53001 Référence CVE CVE-2026-53033 https://www.cve.org/CVERecord?id=CVE-2026-53033 Référence CVE CVE-2026-53034 https://www.cve.org/CVERecord?id=CVE-2026-53034 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53076 https://www.cve.org/CVERecord?id=CVE-2026-53076 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53110 https://www.cve.org/CVERecord?id=CVE-2026-53110 Référence CVE CVE-2026-53111 https://www.cve.org/CVERecord?id=CVE-2026-53111 Référence CVE CVE-2026-53126 https://www.cve.org/CVERecord?id=CVE-2026-53126 Référence CVE CVE-2026-53133 https://www.cve.org/CVERecord?id=CVE-2026-53133 Référence CVE CVE-2026-53142 https://www.cve.org/CVERecord?id=CVE-2026-53142 Référence CVE CVE-2026-53154 https://www.cve.org/CVERecord?id=CVE-2026-53154 Référence CVE CVE-2026-53163 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 https://www.cve.org/CVERecord?id=CVE-2026-53098 Référence CVE CVE-2026-53099 https://www.cve.org/CVERecord?id=CVE-2026-53099 Référence CVE CVE-2026-53100 https://www.cve.org/CVERecord?id=CVE-2026-53100 Référence CVE CVE-2026-53101 https://www.cve.org/CVERecord?id=CVE-2026-53101 Référence CVE CVE-2026-53102 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52994 Référence CVE CVE-2026-53001 https://www.cve.org/CVERecord?id=CVE-2026-53001 Référence CVE CVE-2026-53033 https://www.cve.org/CVERecord?id=CVE-2026-53033 Référence CVE CVE-2026-53034 https://www.cve.org/CVERecord?id=CVE-2026-53034 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53076 https://www.cve.org/CVERecord?id=CVE-2026-53076 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53110 https://www.cve.org/CVERecord?id=CVE-2026-53110 Référence CVE CVE-2026-53111 https://www.cve.org/CVERecord?id=CVE-2026-53111 Référence CVE CVE-2026-53126 https://www.cve.org/CVERecord?id=CVE-2026-53126 Référence CVE CVE-2026-53133 https://www.cve.org/CVERecord?id=CVE-2026-53133 Référence CVE CVE-2026-53142 https://www.cve.org/CVERecord?id=CVE-2026-53142 Référence CVE CVE-2026-53154 https://www.cve.org/CVERecord?id=CVE-2026-53154 Référence CVE CVE-2026-53163 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 https://www.cve.org/CVERecord?id=CVE-2026-53098 Référence CVE CVE-2026-53099 https://www.cve.org/CVERecord?id=CVE-2026-53099 Référence CVE CVE-2026-53100 https://www.cve.org/CVERecord?id=CVE-2026-53100 Référence CVE CVE-2026-53101 https://www.cve.org/CVERecord?id=CVE-2026-53101 Référence CVE CVE-2026-53102 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-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 https://www.cve.org/CVERecord?id=CVE-2026-53098 Référence CVE CVE-2026-53099 https://www.cve.org/CVERecord?id=CVE-2026-53099 Référence CVE CVE-2026-53100 https://www.cve.org/CVERecord?id=CVE-2026-53100 Référence CVE CVE-2026-53101 https://www.cve.org/CVERecord?id=CVE-2026-53101 Référence CVE CVE-2026-53102 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-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 https://www.cve.org/CVERecord?id=CVE-2026-53098 Référence CVE CVE-2026-53099 https://www.cve.org/CVERecord?id=CVE-2026-53099 Référence CVE CVE-2026-53100 https://www.cve.org/CVERecord?id=CVE-2026-53100 Référence CVE CVE-2026-53101 https://www.cve.org/CVERecord?id=CVE-2026-53101 Référence CVE CVE-2026-53102 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0866Multiples vulnérabilités dans Microsoft Azure Linux

u 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53074 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53075 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53076 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53077 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53082 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53086 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53088 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53093 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53094 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53096 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53110 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53111 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53112 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53126 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53128 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53287 du 28 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53289 du 28 juin 2026 Bulletin de sécurité Microsoft Azure Linu

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。bpf: 定数のブラインド処理後に残ったoffload-＞progポインタの問題です。dev-bound-onlyのBPFプログラム（BPF_F_XDP_DEV_BOUND_ONLY）が定数のブラインド処理有効時（bpf_jit_harden ＞= 2）のJITコンパイルを受ける際、bpf_jit_blind_constants()はプログラムをクローンします。元のprogはbpf_jit_prog_release_other()で解放され、この関数はaux-＞progを生存しているクローンを指すように更新しますが、offload-＞progは更新されません。その結果、offload-＞progは解放済みの元のプログラムを指したままとなります。ネットワーク名前空間がその後破棄されると、cleanup_net()はbpf_dev_bound_netdev_unregister()を呼び出し、ondev-＞progsをイテレートして__bpf_prog_offload_destroy(offload-＞prog)を呼び出します。この際、解放済みのprogにアクセスするためページフォルトが発生します。エラーメッセージは以下の通りです。BUG: unable to handle page fault for address: ffffc900085f1038 Workqueue: netns cleanup_net RIP: 0010:__bpf_prog_offload_destroy+0xc/0x80 Call Trace: __bpf_offload_dev_netdev_unregister+0x257/0x350 bpf_dev_bound_netdev_unregister+0x4a/0x90 unregister_netdevice_many_notify+0x2a2/0x660 ... cleanup_net+0x21a/0x320 この問題を確実に再現するテスト手順は以下の通りです。1. net.core.bpf_jit_hardenを2に設定します（echo 2 ＞ /proc/sys/net/core/bpf_jit_harden）。2. ネットワーク名前空間内のvethでdev-bound-onlyのXDPプログラムを作成し、xdp_metadataの自己テストを実行します（./test_progs -t xdp_metadata）。3. cleanup_netが__bpf_prog_offload_destroy内でページフォルトを引き起こします。dev-bound-onlyプログラムはoffload構造体を持ちながら、bpf_prog_offload_compile()経由ではなく通常のJIT経路を通るという特徴があり、定数ブラインド処理によるprogのクローン＆置換の影響を受ける一方で、同期が必要なoffload-＞progも保持しています。この問題は、bpf_jit_prog_release_other()内でaux-＞progの更新に加え、offload-＞progも同時に更新することで修正しました。両者はいずれもprogへのバックポインタであり、progが置き換えられる際には同期を保つ必要があります。

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.3, 6.6.141 ≤ 6.6.*, 6.12.91 ≤ 6.12.*, 6.18.33 ≤ 6.18.*, 7.0.10 ≤ 7.0.*, 7.1 ≤ *
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 24 Jun 2026 · Last source change 5 Aug 2026, 12:33 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-38962
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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-38962↗Vendor CSAF · SUSE Product Security Team↗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-53094 · cve.blacktree.nl