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

bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 252 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 23 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.12% 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: No default targetRemediation target: Normal maintenance

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 252 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.

25 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.100-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.100-1~deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.4-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.

2 current
CVE-2026-64192 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-64192
209 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 Availability Extension 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized When CONFIG_BPF_LSM=y is set, BPF inode storage maps (BPF_MAP_TYPE_INODE_STORAGE) are compiled into the kernel. However, if the BPF LSM is not explicitly enabled at boot time (e.g. omitted from the "lsm=" boot parameter), lsm_prepare() is never executed for the BPF LSM. Consequently, the BPF inode security blob offset (bpf_lsm_blob_sizes.lbs_inode) is never initialized and remains at its default compiled size of 8 bytes instead of being updated to a valid offset past the reserved struct rcu_head (typically 16 bytes or more). When a privileged user creates and updates a BPF_MAP_TYPE_INODE_STORAGE map, bpf_inode() evaluates inode->i_security + 8. This erroneously aliases the struct rcu_head.func callback pointer at the beginning of the inode->i_security blob. During subsequent map element cleanup or inode destruction, writing NULL to owner_storage clears the queued RCU callback pointer. When rcu_do_batch() later executes the queued callback, it attempts an instruction fetch at address 0x0, triggering an immediate kernel panic. Fix this by introducing a global bpf_lsm_initialized boolean flag marked with __ro_after_init. Set this flag to true inside bpf_lsm_init() when the LSM framework successfully registers the BPF LSM. Gate map allocation in inode_storage_map_alloc() on this flag, returning -EOPNOTSUPP if the BPF LSM is in turn uninitialized. This fail-fast approach prevents userspace from allocating inode storage maps when the supporting BPF LSM infrastructure is absent, avoiding zombie map states.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64192 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized
232 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. When the BPF (Berkeley Packet Filter) Linux Security Module (LSM) is compiled into the kernel but not explicitly enabled at boot, a privileged user can create and update a BPF inode storage map. This improper initialization leads to an incorrect memory offset calculation, which can corrupt internal kernel structures. Consequently, this can trigger a kernel panic, resulting in a Denial of Service (DoS) for the system.
Remediation
Affected
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-46012

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized When CONFIG_BPF_LSM=y is set, BPF inode storage maps (BPF_MAP_TYPE_INODE_STORAGE) are compiled into the kernel. However, if the BPF LSM is not explicitly enabled at boot time (e.g. omitted from the "lsm=" boot parameter), lsm_prepare() is never executed for the BPF LSM. Consequently, the BPF inode security blob offset (bpf_lsm_blob_sizes.lbs_inode) is never initialized and remains at its default compiled size of 8 bytes instead of being updated to a valid offset past the reserved struct rcu_head (typically 16 bytes or more). When a privileged user creates and updates a BPF_MAP_TYPE_INODE_STORAGE map, bpf_inode() evaluates inode->i_security + 8. This erroneously aliases the struct rcu_head.func callback pointer at the beginning of the inode->i_security blob. During subsequent map element cleanup or inode destruction, writing NULL to owner_storage clears the queued RCU callback pointer. When rcu_do_batch() later executes the queued callback, it attempts an instruction fetch at address 0x0, triggering an immediate kernel panic. Fix this by introducing a global bpf_lsm_initialized boolean flag marked with __ro_after_init. Set this flag to true inside bpf_lsm_init() when the LSM framework successfully registers the BPF LSM. Gate map allocation in inode_storage_map_alloc() on this flag, returning -EOPNOTSUPP if the BPF LSM is in turn uninitialized. This fail-fast approach prevents userspace from allocating inode storage maps when the supporting BPF LSM infrastructure is absent, avoiding zombie map states.

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 252 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: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized When CONFIG_BPF_LSM=y is set, BPF inode storage maps (BPF_MAP_TYPE_INODE_STORAGE) are compiled into the kernel. However, if the BPF LSM is not explicitly enabled at boot time (e.g. omitted from the "lsm=" boot parameter), lsm_prepare() is never executed for the BPF LSM. Consequently, the BPF inode security blob offset (bpf_lsm_blob_sizes.lbs_inode) is never initialized and remains at its default compiled size of 8 bytes instead of being updated to a valid offset past the reserved struct rcu_head (typically 16 bytes or more). When a privileged user creates and updates a BPF_MAP_TYPE_INODE_STORAGE map, bpf_inode() evaluates inode->i_security + 8. This erroneously aliases the struct rcu_head.func callback pointer at the beginning of the inode->i_security blob. During subsequent map element cleanup or inode destruction, writing NULL to owner_storage clears the queued RCU callback pointer. When rcu_do_batch() later executes the queued callback, it attempts an instruction fetch at address 0x0, triggering an immediate kernel panic. Fix this by introducing a global bpf_lsm_initialized boolean flag marked with __ro_after_init. Set this flag to true inside bpf_lsm_init() when the LSM framework successfully registers the BPF LSM. Gate map allocation in inode_storage_map_alloc() on this flag, returning -EOPNOTSUPP if the BPF LSM is in turn uninitialized. This fail-fast approach prevents userspace from allocating inode storage maps when the supporting BPF LSM infrastructure is absent, avoiding zombie map states.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized When CONFIG_BPF_LSM=y is set, BPF inode storage maps (BPF_MAP_TYPE_INODE_STORAGE) are compiled into the kernel. However, if the BPF LSM is not explicitly enabled at boot time (e.g. omitted from the "lsm=" boot parameter), lsm_prepare() is never executed for the BPF LSM. Consequently, the BPF inode security blob offset (bpf_lsm_blob_sizes.lbs_inode) is never initialized and remains at its default compiled size of 8 bytes instead of being updated to a valid offset past the reserved struct rcu_head (typically 16 bytes or more). When a privileged user creates and updates a BPF_MAP_TYPE_INODE_STORAGE map, bpf_inode() evaluates inode->i_security + 8. This erroneously aliases the struct rcu_head.func callback pointer at the beginning of the inode->i_security blob. During subsequent map element cleanup or inode destruction, writing NULL to owner_storage clears the queued RCU callback pointer. When rcu_do_batch() later executes the queued callback, it attempts an instruction fetch at address 0x0, triggering an immediate kernel panic. Fix this by introducing a global bpf_lsm_initialized boolean flag marked with __ro_after_init. Set this flag to true inside bpf_lsm_init() when the LSM framework successfully registers the BPF LSM. Gate map allocation in inode_storage_map_alloc() on this flag, returning -EOPNOTSUPP if the BPF LSM is in turn uninitialized. This fail-fast approach prevents userspace from allocating inode storage maps when the supporting BPF LSM infrastructure is absent, avoiding zombie map states.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized When CONFIG_BPF_LSM=y is set, BPF inode storage maps (BPF_MAP_TYPE_INODE_STORAGE) are compiled into the kernel. However, if the BPF LSM is not explicitly enabled at boot time (e.g. omitted from the "lsm=" boot parameter), lsm_prepare() is never executed for the BPF LSM. Consequently, the BPF inode security blob offset (bpf_lsm_blob_sizes.lbs_inode) is never initialized and remains at its default compiled size of 8 bytes instead of being updated to a valid offset past the reserved struct rcu_head (typically 16 bytes or more). When a privileged user creates and updates a BPF_MAP_TYPE_INODE_STORAGE map, bpf_inode() evaluates inode->i_security + 8. This erroneously aliases the struct rcu_head.func callback pointer at the beginning of the inode->i_security blob. During subsequent map element cleanup or inode destruction, writing NULL to owner_storage clears the queued RCU callback pointer. When rcu_do_batch() later executes the queued callback, it attempts an instruction fetch at address 0x0, triggering an immediate kernel panic. Fix this by introducing a global bpf_lsm_initialized boolean flag marked with __ro_after_init. Set this flag to true inside bpf_lsm_init() when the LSM framework successfully registers the BPF LSM. Gate map allocation in inode_storage_map_alloc() on this flag, returning -EOPNOTSUPP if the BPF LSM is in turn uninitialized. This fail-fast approach prevents userspace from allocating inode storage maps when the supporting BPF LSM infrastructure is absent, avoiding zombie map states.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → 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: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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.
CWE-476
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-46012Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized When CONFIG_BPF_LSM=y is set, BPF inode storage maps (BPF_MAP_TYPE_INODE_STORAGE) are compiled into the kernel. However, if the BPF LSM is not explicitly enabled at boot time (e.g. omitted from the "lsm=" boot parameter), lsm_prepare() is never executed for the BPF LSM. Consequently, the BPF inode security blob offset (bpf_lsm_blob_sizes.lbs_inode) is never initialized and remains at its default compiled size of 8 bytes instead of being updated to a valid offset past the reserved struct rcu_head (typically 16 bytes or more). When a privileged user creates and updates a BPF_MAP_TYPE_INODE_STORAGE map, bpf_inode() evaluates inode->i_security + 8. This erroneously aliases the struct rcu_head.func callback pointer at the beginning of the inode->i_security blob. During subsequent map element cleanup or inode destruction, writing NULL to owner_storage clears the queued RCU callback pointer. When rcu_do_batch() later executes the queued callback, it attempts an instruction fetch at address 0x0, triggering an immediate kernel panic. Fix this by introducing a global bpf_lsm_initialized boolean flag marked with __ro_after_init. Set this flag to true inside bpf_lsm_init() when the LSM framework successfully registers the BPF LSM. Gate map allocation in inode_storage_map_alloc() on this flag, returning -EOPNOTSUPP if the BPF LSM is in turn uninitialized. This fail-fast approach prevents userspace from allocating inode storage maps when the supporting BPF LSM infrastructure is absent, avoiding zombie map states.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2427Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise um Daten zu manipulieren oder offenzulegen, Sicherheitsmaßnahmen zu umgehen oder einen Denial-of-Service-Zustand zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 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-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64186 https://www.cve.org/CVERecord?id=CVE-2026-64186 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64205 https://www.cve.org/CVERecord?id=CVE-2026-64205 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64207 https://www.cve.org/CVERecord?id=CVE-2026-64207 Référence CVE CVE-2026-64208 https://www.cve.org/CVERecord?id=CVE-2026-64208 Référence CVE CVE-2026-64209 https://www.cve.org/CVERecord?id=CVE-2026-64209 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 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-64169 Référence CVE CVE-2026-64170 https://www.cve.org/CVERecord?id=CVE-2026-64170 Référence CVE CVE-2026-64177 https://www.cve.org/CVERecord?id=CVE-2026-64177 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64190 https://www.cve.org/CVERecord?id=CVE-2026-64190 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64232 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-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64186 https://www.cve.org/CVERecord?id=CVE-2026-64186 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64205 https://www.cve.org/CVERecord?id=CVE-2026-64205 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64207 https://www.cve.org/CVERecord?id=CVE-2026-64207 Référence CVE CVE-2026-64208 https://www.cve.org/CVERecord?id=CVE-2026-64208 Référence CVE CVE-2026-64209 https://www.cve.org/CVERecord?id=CVE-2026-64209 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 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-64155 Référence CVE CVE-2026-64164 https://www.cve.org/CVERecord?id=CVE-2026-64164 Référence CVE CVE-2026-64166 https://www.cve.org/CVERecord?id=CVE-2026-64166 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64190 https://www.cve.org/CVERecord?id=CVE-2026-64190 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64180 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64205 https://www.cve.org/CVERecord?id=CVE-2026-64205 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64207 https://www.cve.org/CVERecord?id=CVE-2026-64207 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64220 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-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64184 https://www.cve.org/CVERecord?id=CVE-2026-64184 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64186 https://www.cve.org/CVERecord?id=CVE-2026-64186 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64191 https://www.cve.org/CVERecord?id=CVE-2026-64191 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64205 https://www.cve.org/CVERecord?id=CVE-2026-64205 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64207 https://www.cve.org/CVERecord?id=CVE-2026-64207 Référence CVE CVE-2026-64208 https://www.cve.org/CVERecord?id=CVE-2026-64208 Référence CVE CVE-2026-64209 https://www.cve.org/CVERecord?id=CVE-2026-64209 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64211 https://www.cve.org/CVERecord?id=CVE-2026-64211 Référence CVE CVE-2026-64212 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46111 Référence CVE CVE-2026-46158 https://www.cve.org/CVERecord?id=CVE-2026-46158 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 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-53361 https://www.cve.org/CVERecord?id=CVE-2026-53361 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64139 https://www.cve.org/CVERecord?id=CVE-2026-64139 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64270 https://www.cve.org/CVERecord?id=CVE-2026-64270 Référence CVE CVE-2026-64272 https://www.cve.org/CVERecord?id=CVE-2026-64272 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=CVE-2026-64294 Référence CVE CVE-2026-64434 https://www.cve.org/CVERecord?id=CVE-2026-64434 Référence CVE CVE-2026-64507 https://www.cve.org/CVERecord?id=CVE-2026-64507 Référence CVE CVE-2026-64508 https://www.cve.org/CVERecord?id=CVE-2026-64508 Référence CVE CVE-2026-64542 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-64155 Référence CVE CVE-2026-64164 https://www.cve.org/CVERecord?id=CVE-2026-64164 Référence CVE CVE-2026-64166 https://www.cve.org/CVERecord?id=CVE-2026-64166 Référence CVE CVE-2026-64168 https://www.cve.org/CVERecord?id=CVE-2026-64168 Référence CVE CVE-2026-64178 https://www.cve.org/CVERecord?id=CVE-2026-64178 Référence CVE CVE-2026-64180 https://www.cve.org/CVERecord?id=CVE-2026-64180 Référence CVE CVE-2026-64185 https://www.cve.org/CVERecord?id=CVE-2026-64185 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64190 https://www.cve.org/CVERecord?id=CVE-2026-64190 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64218 https://www.cve.org/CVERecord?id=CVE-2026-64218 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-63806 Référence CVE CVE-2026-63810 https://www.cve.org/CVERecord?id=CVE-2026-63810 Référence CVE CVE-2026-63815 https://www.cve.org/CVERecord?id=CVE-2026-63815 Référence CVE CVE-2026-63816 https://www.cve.org/CVERecord?id=CVE-2026-63816 Référence CVE CVE-2026-63818 https://www.cve.org/CVERecord?id=CVE-2026-63818 Référence CVE CVE-2026-63829 https://www.cve.org/CVERecord?id=CVE-2026-63829 Référence CVE CVE-2026-63970 https://www.cve.org/CVERecord?id=CVE-2026-63970 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64241 https://www.cve.org/CVERecord?id=CVE-2026-64241 Référence CVE CVE-2026-64248 https://www.cve.org/CVERecord?id=CVE-2026-64248 Référence CVE CVE-2026-64250 https://www.cve.org/CVERecord?id=CVE-2026-64250 Référence CVE CVE-2026-64256 https://www.cve.org/CVERecord?id=CVE-2026-64256 Référence CVE CVE-2026-64265 https://www.cve.org/CVERecord?id=CVE-2026-64265 Référence CVE CVE-2026-64266 https://www.cve.org/CVERecord?id=

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

ns Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian msg00316 du 31 juillet 2026 https://lists.debian.org/debian-security-announce/2026/msg00316.html Référence CVE CVE-2026-45944 https://www.cve.org/CVERecord?id=CVE-2026-45944 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-63970 https://www.cve.org/CVERecord?id=CVE-2026-63970 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64307 https://www.cve.org/CVERecord?id=CVE-2026-64307 Référence CVE CVE-2026-64341 https://www.cve.org/CVERecord?id=CVE-2026-64341 Référence CVE CVE-2026-64352 https://www.cve.org/CVERecord?id=CVE-2026-64352 Référence CVE CVE-2026-64361 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-027869LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。bpf: BPF LSMが初期化されていない場合にBPF_MAP_TYPE_INODE_STORAGEの作成を拒否する対策です。CONFIG_BPF_LSM=yが設定されている場合、BPF inodeストレージマップ（BPF_MAP_TYPE_INODE_STORAGE）がカーネルにコンパイルされます。しかし、BPF LSMが起動時に明示的に有効化されていない場合（例えば、「lsm=」ブートパラメータから省略された場合）、lsm_prepare()はBPF LSMに対して一度も実行されません。結果として、BPF inodeセキュリティblobのオフセット（bpf_lsm_blob_sizes.lbs_inode）が初期化されず、予約されたstruct rcu_headの後の有効なオフセット（通常16バイト以上）に更新される代わりに、コンパイル時のデフォルトサイズである8バイトのままとなります。特権ユーザーがBPF_MAP_TYPE_INODE_STORAGEマップを作成および更新すると、bpf_inode()はinode-＞i_security + 8を評価します。これは誤ってinode-＞i_security blobの先頭にあるstruct rcu_head.funcコールバックポインタと衝突します。その後のマップ要素のクリーンアップやinodeの破棄時に、owner_storageをNULLに書き込むことでキューに入っているRCUコールバックポインタがクリアされます。rcu_do_batch()が後でキューに入ったコールバックを実行する際、アドレス0x0で命令フェッチを試みるため、即座にカーネルパニックが発生します。これを修正するために、__ro_after_init属性付きのグローバルなbpf_lsm_initializedブールフラグを導入しました。LSMフレームワークがBPF LSMの登録に成功した場合、bpf_lsm_init()内でこのフラグをtrueに設定します。inode_storage_map_alloc()内のマップ割り当てはこのフラグを条件として判定し、BPF LSMが初期化されていない場合は-EOPNOTSUPPを返します。このフェイルファスト方式により、BPF LSMのサポートインフラが存在しない場合にユーザースペースからinodeストレージマップの割り当てを防ぎ、ゾンビマップ状態の発生を回避します。

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: < 5.10, 5.10.266 ≤ 5.10.*, 5.15.217 ≤ 5.15.*, 6.1.184 ≤ 6.1.*, 6.6.148 ≤ 6.6.*, 6.12.97 ≤ 6.12.*, 6.18.40 ≤ 6.18.*, 7.1.4 ≤ 7.1.*, 7.2 ≤ *
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 20 Jul 2026 · Last source change 23 Aug 2026, 12:45 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-46012
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < 5337eebdf8c5d4810b1913047f078d2815d5645f; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < de984ea883405420fdc416ae8964b752df586970; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < 267fdd9b6530c399dfd996e1a0a7628b45baf9f0; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < c76b8abce575e0c6e4096957220b4515ed847d89; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < a6f0643e4f63cfaa0d5d4a69de4f132eac4b8fe4; 5.10 · Fixed: < 5.10; 6.6.148 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2 ≤ *
    After
    8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < 413b14b9623a2e6ee131c2b2152b304aeb04e378; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < a6d634f794c808a261eac7d5af023a7e06b9ecd8; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < 721f669853bdbf46b475a81bb5d05d610f8c19de; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < 5337eebdf8c5d4810b1913047f078d2815d5645f; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < de984ea883405420fdc416ae8964b752df586970; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < 267fdd9b6530c399dfd996e1a0a7628b45baf9f0; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < c76b8abce575e0c6e4096957220b4515ed847d89; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < a6f0643e4f63cfaa0d5d4a69de4f132eac4b8fe4 · Fixed: < 5.10; 5.10.266 ≤ 5.10.*; 5.15.217 ≤ 5.15.*; 6.1.184 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.4 ≤ 7.1.*
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < 5337eebdf8c5d4810b1913047f078d2815d5645f; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < de984ea883405420fdc416ae8964b752df586970; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < 267fdd9b6530c399dfd996e1a0a7628b45baf9f0; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < c76b8abce575e0c6e4096957220b4515ed847d89; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < a6f0643e4f63cfaa0d5d4a69de4f132eac4b8fe4; 5.10 · Fixed: < 5.10; 6.6.148 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2-rc2 ≤ *
    After
    8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < 5337eebdf8c5d4810b1913047f078d2815d5645f; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < de984ea883405420fdc416ae8964b752df586970; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < 267fdd9b6530c399dfd996e1a0a7628b45baf9f0; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < c76b8abce575e0c6e4096957220b4515ed847d89; 8ea636848aca35b9f97c5b5dee30225cf2dd0fe6 < a6f0643e4f63cfaa0d5d4a69de4f132eac4b8fe4; 5.10 · Fixed: < 5.10; 6.6.148 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.4 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
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-46012↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor 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-64192 · cve.blacktree.nl