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

ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps()

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 281 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.77% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 3 daysRemediation target: Within 90 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 281 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.101-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 5 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-68160 · CSAF 2.0 · revision 14 · interimSUSE Product Security TeamCVE-2026-68160
308 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: ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() ceph_handle_caps() reads snap_trace_len from the wire-format ceph_mds_caps header and uses it unconditionally to build a fake end pointer (snaptrace + snaptrace_len) that is later handed to ceph_update_snap_trace() in the CEPH_CAP_OP_IMPORT case: snaptrace = h + 1; snaptrace_len = le32_to_cpu(h->snap_trace_len); p = snaptrace + snaptrace_len; ... case CEPH_CAP_OP_IMPORT: if (snaptrace_len) { ... if (ceph_update_snap_trace(mdsc, snaptrace, snaptrace + snaptrace_len, false, &realm)) { ... } ceph_update_snap_trace() then decodes a struct ceph_mds_snap_realm from snaptrace using ceph_decode_need(&p, e, sizeof(*ri), bad) with the attacker-supplied fake end e == snaptrace + snaptrace_len. With snaptrace_len == 0xFFFFFFFF the bound check is trivially satisfied, ri = p reads sizeof(struct ceph_mds_snap_realm) past the legitimate msg->front buffer, and ri->num_snaps / ri->num_prior_parent_snaps then drive further out-of-bounds reads of the encoded snap arrays. The eleven msg_version >= 2 .. msg_version >= 12 decoder blocks above the op switch each catch this OOB through their ceph_decode_*_safe() / ceph_decode_need() helpers, but they sit behind a hdr.version-gated if, so a malicious or compromised MDS that sets msg->hdr.version = 1 reaches the IMPORT path with no version-gated decoder having validated snap_trace_len. The shape has been present since ceph_handle_caps() was introduced. Validate snap_trace_len against the message front buffer before consuming it, using the canonical ceph_decode_need() / ceph_has_room() helper. The helper bounds the length with subtraction (n = p) rather than pointer addition, so it is wrap-safe for the attacker-controlled u32 length on 32-bit builds where p + snap_trace_len could overflow the address space. This matches the rest of the ceph decode path (e.g. the pool_ns_len check a few lines below), and the existing goto bad cleanup already covers this exit path.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-68160 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps()
261 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's Ceph component. A remote attacker could exploit this by sending a specially crafted message with a manipulated snap_trace_len value. This pre-authentication vulnerability allows for an out-of-bounds read, potentially leading to information disclosure or a denial of service.
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-55546

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() ceph_handle_caps() reads snap_trace_len from the wire-format ceph_mds_caps header and uses it unconditionally to build a fake end pointer (snaptrace + snaptrace_len) that is later handed to ceph_update_snap_trace() in the CEPH_CAP_OP_IMPORT case: snaptrace = h + 1; snaptrace_len = le32_to_cpu(h->snap_trace_len); p = snaptrace + snaptrace_len; ... case CEPH_CAP_OP_IMPORT: if (snaptrace_len) { ... if (ceph_update_snap_trace(mdsc, snaptrace, snaptrace + snaptrace_len, false, &realm)) { ... } ceph_update_snap_trace() then decodes a struct ceph_mds_snap_realm from snaptrace using ceph_decode_need(&p, e, sizeof(*ri), bad) with the attacker-supplied fake end e == snaptrace + snaptrace_len. With snaptrace_len == 0xFFFFFFFF the bound check is trivially satisfied, ri = p reads sizeof(struct ceph_mds_snap_realm) past the legitimate msg->front buffer, and ri->num_snaps / ri->num_prior_parent_snaps then drive further out-of-bounds reads of the encoded snap arrays. The eleven msg_version >= 2 .. msg_version >= 12 decoder blocks above the op switch each catch this OOB through their ceph_decode_*_safe() / ceph_decode_need() helpers, but they sit behind a hdr.version-gated if, so a malicious or compromised MDS that sets msg->hdr.version = 1 reaches the IMPORT path with no version-gated decoder having validated snap_trace_len. The shape has been present since ceph_handle_caps() was introduced. Validate snap_trace_len against the message front buffer before consuming it, using the canonical ceph_decode_need() / ceph_has_room() helper. The helper bounds the length with subtraction (n <= end - p, guarded by end >= p) rather than pointer addition, so it is wrap-safe for the attacker-controlled u32 length on 32-bit builds where p + snap_trace_len could overflow the address space. This matches the rest of the ceph decode path (e.g. the pool_ns_len check a few lines below), and the existing goto bad cleanup already covers this exit path.

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

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 281 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: ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() ceph_handle_caps() reads snap_trace_len from the wire-format ceph_mds_caps header and uses it unconditionally to build a fake end pointer (snaptrace + snaptrace_len) that is later handed to ceph_update_snap_trace() in the CEPH_CAP_OP_IMPORT case: snaptrace = h + 1; snaptrace_len = le32_to_cpu(h->snap_trace_len); p = snaptrace + snaptrace_len; ... case CEPH_CAP_OP_IMPORT: if (snaptrace_len) { ... if (ceph_update_snap_trace(mdsc, snaptrace, snaptrace + snaptrace_len, false, &realm)) { ... } ceph_update_snap_trace() then decodes a struct ceph_mds_snap_realm from snaptrace using ceph_decode_need(&p, e, sizeof(*ri), bad) with the attacker-supplied fake end e == snaptrace + snaptrace_len. With snaptrace_len == 0xFFFFFFFF the bound check is trivially satisfied, ri = p reads sizeof(struct ceph_mds_snap_realm) past the legitimate msg->front buffer, and ri->num_snaps / ri->num_prior_parent_snaps then drive further out-of-bounds reads of the encoded snap arrays. The eleven msg_version >= 2 .. msg_version >= 12 decoder blocks above the op switch each catch this OOB through their ceph_decode_*_safe() / ceph_decode_need() helpers, but they sit behind a hdr.version-gated if, so a malicious or compromised MDS that sets msg->hdr.version = 1 reaches the IMPORT path with no version-gated decoder having validated snap_trace_len. The shape has been present since ceph_handle_caps() was introduced. Validate snap_trace_len against the message front buffer before consuming it, using the canonical ceph_decode_need() / ceph_has_room() helper. The helper bounds the length with subtraction (n <= end - p, guarded by end >= p) rather than pointer addition, so it is wrap-safe for the attacker-controlled u32 length on 32-bit builds where p + snap_trace_len could overflow the address space. This matches the rest of the ceph decode path (e.g. the pool_ns_len check a few lines below), and the existing goto bad cleanup already covers this exit path.

What

In the Linux kernel, the following vulnerability has been resolved: ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() ceph_handle_caps() reads snap_trace_len from the wire-format ceph_mds_caps header and uses it unconditionally to build a fake end pointer (snaptrace + snaptrace_len) that is later handed to ceph_update_snap_trace() in the CEPH_CAP_OP_IMPORT case: snaptrace = h + 1; snaptrace_len = le32_to_cpu(h->snap_trace_len); p = snaptrace + snaptrace_len; ... case CEPH_CAP_OP_IMPORT: if (snaptrace_len) { ... if (ceph_update_snap_trace(mdsc, snaptrace, snaptrace + snaptrace_len, false, &realm)) { ... } ceph_update_snap_trace() then decodes a struct ceph_mds_snap_realm from snaptrace using ceph_decode_need(&p, e, sizeof(*ri), bad) with the attacker-supplied fake end e == snaptrace + snaptrace_len. With snaptrace_len == 0xFFFFFFFF the bound check is trivially satisfied, ri = p reads sizeof(struct ceph_mds_snap_realm) past the legitimate msg->front buffer, and ri->num_snaps / ri->num_prior_parent_snaps then drive further out-of-bounds reads of the encoded snap arrays. The eleven msg_version >= 2 .. msg_version >= 12 decoder blocks above the op switch each catch this OOB through their ceph_decode_*_safe() / ceph_decode_need() helpers, but they sit behind a hdr.version-gated if, so a malicious or compromised MDS that sets msg->hdr.version = 1 reaches the IMPORT path with no version-gated decoder having validated snap_trace_len. The shape has been present since ceph_handle_caps() was introduced. Validate snap_trace_len against the message front buffer before consuming it, using the canonical ceph_decode_need() / ceph_has_room() helper. The helper bounds the length with subtraction (n <= end - p, guarded by end >= p) rather than pointer addition, so it is wrap-safe for the attacker-controlled u32 length on 32-bit builds where p + snap_trace_len could overflow the address space. This matches the rest of the ceph decode path (e.g. the pool_ns_len check a few lines below), and the existing goto bad cleanup already covers this exit path.

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 a network path may attempt exploitation without authentication or user interaction. 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: ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() ceph_handle_caps() reads snap_trace_len from the wire-format ceph_mds_caps header and uses it unconditionally to build a fake end pointer (snaptrace + snaptrace_len) that is later handed to ceph_update_snap_trace() in the CEPH_CAP_OP_IMPORT case: snaptrace = h + 1; snaptrace_len = le32_to_cpu(h->snap_trace_len); p = snaptrace + snaptrace_len; ... case CEPH_CAP_OP_IMPORT: if (snaptrace_len) { ... if (ceph_update_snap_trace(mdsc, snaptrace, snaptrace + snaptrace_len, false, &realm)) { ... } ceph_update_snap_trace() then decodes a struct ceph_mds_snap_realm from snaptrace using ceph_decode_need(&p, e, sizeof(*ri), bad) with the attacker-supplied fake end e == snaptrace + snaptrace_len. With snaptrace_len == 0xFFFFFFFF the bound check is trivially satisfied, ri = p reads sizeof(struct ceph_mds_snap_realm) past the legitimate msg->front buffer, and ri->num_snaps / ri->num_prior_parent_snaps then drive further out-of-bounds reads of the encoded snap arrays. The eleven msg_version >= 2 .. msg_version >= 12 decoder blocks above the op switch each catch this OOB through their ceph_decode_*_safe() / ceph_decode_need() helpers, but they sit behind a hdr.version-gated if, so a malicious or compromised MDS that sets msg->hdr.version = 1 reaches the IMPORT path with no version-gated decoder having validated snap_trace_len. The shape has been present since ceph_handle_caps() was introduced. Validate snap_trace_len against the message front buffer before consuming it, using the canonical ceph_decode_need() / ceph_has_room() helper. The helper bounds the length with subtraction (n <= end - p, guarded by end >= p) rather than pointer addition, so it is wrap-safe for the attacker-controlled u32 length on 32-bit builds where p + snap_trace_len could overflow the address space. This matches the rest of the ceph decode path (e.g. the pool_ns_len check a few lines below), and the existing goto bad cleanup already covers this exit path.

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 a network path may attempt exploitation without authentication or user interaction. 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
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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:N/AC:L/PR:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-55546Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() ceph_handle_caps() reads snap_trace_len from the wire-format ceph_mds_caps header and uses it unconditionally to build a fake end pointer (snaptrace + snaptrace_len) that is later handed to ceph_update_snap_trace() in the CEPH_CAP_OP_IMPORT case: snaptrace = h + 1; snaptrace_len = le32_to_cpu(h->snap_trace_len); p = snaptrace + snaptrace_len; ... case CEPH_CAP_OP_IMPORT: if (snaptrace_len) { ... if (ceph_update_snap_trace(mdsc, snaptrace, snaptrace + snaptrace_len, false, &realm)) { ... } ceph_update_snap_trace() then decodes a struct ceph_mds_snap_realm from snaptrace using ceph_decode_need(&p, e, sizeof(*ri), bad) with the attacker-supplied fake end e == snaptrace + snaptrace_len. With snaptrace_len == 0xFFFFFFFF the bound check is trivially satisfied, ri = p reads sizeof(struct ceph_mds_snap_realm) past the legitimate msg->front buffer, and ri->num_snaps / ri->num_prior_parent_snaps then drive further out-of-bounds reads of the encoded snap arrays. The eleven msg_version >= 2 .. msg_version >= 12 decoder blocks above the op switch each catch this OOB through their ceph_decode_*_safe() / ceph_decode_need() helpers, but they sit behind a hdr.version-gated if, so a malicious or compromised MDS that sets msg->hdr.version = 1 reaches the IMPORT path with no version-gated decoder having validated snap_trace_len. The shape has been present since ceph_handle_caps() was introduced. Validate snap_trace_len against the message front buffer before consuming it, using the canonical ceph_decode_need() / ceph_has_room() helper. The helper bounds the length with subtraction (n <= end - p, guarded by end >= p) rather than pointer addition, so it is wrap-safe for the attacker-controlled u32 length on 32-bit builds where p + snap_trace_len could overflow the address space. This matches the rest of the ceph decode path (e.g. the pool_ns_len check a few lines below), and the existing goto bad cleanup already covers this exit path.

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

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

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

d?id=CVE-2026-68138 Référence CVE CVE-2026-68141 https://www.cve.org/CVERecord?id=CVE-2026-68141 Référence CVE CVE-2026-68143 https://www.cve.org/CVERecord?id=CVE-2026-68143 Référence CVE CVE-2026-68153 https://www.cve.org/CVERecord?id=CVE-2026-68153 Référence CVE CVE-2026-68154 https://www.cve.org/CVERecord?id=CVE-2026-68154 Référence CVE CVE-2026-68155 https://www.cve.org/CVERecord?id=CVE-2026-68155 Référence CVE CVE-2026-68156 https://www.cve.org/CVERecord?id=CVE-2026-68156 Référence CVE CVE-2026-68158 https://www.cve.org/CVERecord?id=CVE-2026-68158 Référence CVE CVE-2026-68159 https://www.cve.org/CVERecord?id=CVE-2026-68159 Référence CVE CVE-2026-68160 https://www.cve.org/CVERecord?id=CVE-2026-68160 Référence CVE CVE-2026-68188 https://www.cve.org/CVERecord?id=CVE-2026-68188 Référence CVE CVE-2026-68197 https://www.cve.org/CVERecord?id=CVE-2026-68197 Référence CVE CVE-2026-68198 https://www.cve.org/CVERecord?id=CVE-2026-68198 Référence CVE CVE-2026-68202 https://www.cve.org/CVERecord?id=CVE-2026-68202 Référence CVE CVE-2026-68234 https://www.cve.org/CVERecord?id=CVE-2026-68234 Référence CVE CVE-2026-68238 https://www.cve.org/CVERecord?id=CVE-2026-68238 Référence CVE CVE-2026-68277 https://www.cve.org/CVERecord?id=CVE-2026-68277 Référence CVE CVE-2026-68278 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-68149 Référence CVE CVE-2026-68152 https://www.cve.org/CVERecord?id=CVE-2026-68152 Référence CVE CVE-2026-68153 https://www.cve.org/CVERecord?id=CVE-2026-68153 Référence CVE CVE-2026-68154 https://www.cve.org/CVERecord?id=CVE-2026-68154 Référence CVE CVE-2026-68155 https://www.cve.org/CVERecord?id=CVE-2026-68155 Référence CVE CVE-2026-68156 https://www.cve.org/CVERecord?id=CVE-2026-68156 Référence CVE CVE-2026-68157 https://www.cve.org/CVERecord?id=CVE-2026-68157 Référence CVE CVE-2026-68158 https://www.cve.org/CVERecord?id=CVE-2026-68158 Référence CVE CVE-2026-68159 https://www.cve.org/CVERecord?id=CVE-2026-68159 Référence CVE CVE-2026-68160 https://www.cve.org/CVERecord?id=CVE-2026-68160 Référence CVE CVE-2026-68161 https://www.cve.org/CVERecord?id=CVE-2026-68161 Référence CVE CVE-2026-68162 https://www.cve.org/CVERecord?id=CVE-2026-68162 Référence CVE CVE-2026-68166 https://www.cve.org/CVERecord?id=CVE-2026-68166 Référence CVE CVE-2026-68180 https://www.cve.org/CVERecord?id=CVE-2026-68180 Référence CVE CVE-2026-68181 https://www.cve.org/CVERecord?id=CVE-2026-68181 Référence CVE CVE-2026-68182 https://www.cve.org/CVERecord?id=CVE-2026-68182 Référence CVE CVE-2026-68184 https://www.cve.org/CVERecord?id=CVE-2026-68184 Référence CVE CVE-2026-68188 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-68137 Référence CVE CVE-2026-68138 https://www.cve.org/CVERecord?id=CVE-2026-68138 Référence CVE CVE-2026-68144 https://www.cve.org/CVERecord?id=CVE-2026-68144 Référence CVE CVE-2026-68147 https://www.cve.org/CVERecord?id=CVE-2026-68147 Référence CVE CVE-2026-68152 https://www.cve.org/CVERecord?id=CVE-2026-68152 Référence CVE CVE-2026-68154 https://www.cve.org/CVERecord?id=CVE-2026-68154 Référence CVE CVE-2026-68156 https://www.cve.org/CVERecord?id=CVE-2026-68156 Référence CVE CVE-2026-68158 https://www.cve.org/CVERecord?id=CVE-2026-68158 Référence CVE CVE-2026-68159 https://www.cve.org/CVERecord?id=CVE-2026-68159 Référence CVE CVE-2026-68160 https://www.cve.org/CVERecord?id=CVE-2026-68160 Référence CVE CVE-2026-68161 https://www.cve.org/CVERecord?id=CVE-2026-68161 Référence CVE CVE-2026-68162 https://www.cve.org/CVERecord?id=CVE-2026-68162 Référence CVE CVE-2026-68198 https://www.cve.org/CVERecord?id=CVE-2026-68198 Référence CVE CVE-2026-68206 https://www.cve.org/CVERecord?id=CVE-2026-68206 Référence CVE CVE-2026-68209 https://www.cve.org/CVERecord?id=CVE-2026-68209 Référence CVE CVE-2026-68210 https://www.cve.org/CVERecord?id=CVE-2026-68210 Référence CVE CVE-2026-68213 https://www.cve.org/CVERecord?id=CVE-2026-68213 Référence CVE CVE-2026-68228 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-68148 Référence CVE CVE-2026-68151 https://www.cve.org/CVERecord?id=CVE-2026-68151 Référence CVE CVE-2026-68153 https://www.cve.org/CVERecord?id=CVE-2026-68153 Référence CVE CVE-2026-68154 https://www.cve.org/CVERecord?id=CVE-2026-68154 Référence CVE CVE-2026-68155 https://www.cve.org/CVERecord?id=CVE-2026-68155 Référence CVE CVE-2026-68156 https://www.cve.org/CVERecord?id=CVE-2026-68156 Référence CVE CVE-2026-68157 https://www.cve.org/CVERecord?id=CVE-2026-68157 Référence CVE CVE-2026-68158 https://www.cve.org/CVERecord?id=CVE-2026-68158 Référence CVE CVE-2026-68159 https://www.cve.org/CVERecord?id=CVE-2026-68159 Référence CVE CVE-2026-68160 https://www.cve.org/CVERecord?id=CVE-2026-68160 Référence CVE CVE-2026-68162 https://www.cve.org/CVERecord?id=CVE-2026-68162 Référence CVE CVE-2026-68164 https://www.cve.org/CVERecord?id=CVE-2026-68164 Référence CVE CVE-2026-68165 https://www.cve.org/CVERecord?id=CVE-2026-68165 Référence CVE CVE-2026-68169 https://www.cve.org/CVERecord?id=CVE-2026-68169 Référence CVE CVE-2026-68175 https://www.cve.org/CVERecord?id=CVE-2026-68175 Référence CVE CVE-2026-68176 https://www.cve.org/CVERecord?id=CVE-2026-68176 Référence CVE CVE-2026-68180 https://www.cve.org/CVERecord?id=CVE-2026-68180 Référence CVE CVE-2026-68181 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-68149 Référence CVE CVE-2026-68152 https://www.cve.org/CVERecord?id=CVE-2026-68152 Référence CVE CVE-2026-68153 https://www.cve.org/CVERecord?id=CVE-2026-68153 Référence CVE CVE-2026-68154 https://www.cve.org/CVERecord?id=CVE-2026-68154 Référence CVE CVE-2026-68155 https://www.cve.org/CVERecord?id=CVE-2026-68155 Référence CVE CVE-2026-68156 https://www.cve.org/CVERecord?id=CVE-2026-68156 Référence CVE CVE-2026-68157 https://www.cve.org/CVERecord?id=CVE-2026-68157 Référence CVE CVE-2026-68158 https://www.cve.org/CVERecord?id=CVE-2026-68158 Référence CVE CVE-2026-68159 https://www.cve.org/CVERecord?id=CVE-2026-68159 Référence CVE CVE-2026-68160 https://www.cve.org/CVERecord?id=CVE-2026-68160 Référence CVE CVE-2026-68161 https://www.cve.org/CVERecord?id=CVE-2026-68161 Référence CVE CVE-2026-68162 https://www.cve.org/CVERecord?id=CVE-2026-68162 Référence CVE CVE-2026-68166 https://www.cve.org/CVERecord?id=CVE-2026-68166 Référence CVE CVE-2026-68180 https://www.cve.org/CVERecord?id=CVE-2026-68180 Référence CVE CVE-2026-68181 https://www.cve.org/CVERecord?id=CVE-2026-68181 Référence CVE CVE-2026-68182 https://www.cve.org/CVERecord?id=CVE-2026-68182 Référence CVE CVE-2026-68184 https://www.cve.org/CVERecord?id=CVE-2026-68184 Référence CVE CVE-2026-68188 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68149 Référence CVE CVE-2026-68151 https://www.cve.org/CVERecord?id=CVE-2026-68151 Référence CVE CVE-2026-68152 https://www.cve.org/CVERecord?id=CVE-2026-68152 Référence CVE CVE-2026-68153 https://www.cve.org/CVERecord?id=CVE-2026-68153 Référence CVE CVE-2026-68154 https://www.cve.org/CVERecord?id=CVE-2026-68154 Référence CVE CVE-2026-68155 https://www.cve.org/CVERecord?id=CVE-2026-68155 Référence CVE CVE-2026-68156 https://www.cve.org/CVERecord?id=CVE-2026-68156 Référence CVE CVE-2026-68157 https://www.cve.org/CVERecord?id=CVE-2026-68157 Référence CVE CVE-2026-68158 https://www.cve.org/CVERecord?id=CVE-2026-68158 Référence CVE CVE-2026-68160 https://www.cve.org/CVERecord?id=CVE-2026-68160 Référence CVE CVE-2026-68161 https://www.cve.org/CVERecord?id=CVE-2026-68161 Référence CVE CVE-2026-68162 https://www.cve.org/CVERecord?id=CVE-2026-68162 Référence CVE CVE-2026-68164 https://www.cve.org/CVERecord?id=CVE-2026-68164 Référence CVE CVE-2026-68165 https://www.cve.org/CVERecord?id=CVE-2026-68165 Référence CVE CVE-2026-68175 https://www.cve.org/CVERecord?id=CVE-2026-68175 Référence CVE CVE-2026-68176 https://www.cve.org/CVERecord?id=CVE-2026-68176 Référence CVE CVE-2026-68178 https://www.cve.org/CVERecord?id=CVE-2026-68178 Référence CVE CVE-2026-68179 https://www.cve.org/CVERecord?id=

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
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 10 Aug 2026 · Last source change 19 Aug 2026, 16:30 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-55546
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    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; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1; cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5; dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5; gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5; ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1; and 280 more · Fixed: cluster-md-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; dlm-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; gfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-64kb-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-64kb-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-base-5.14.21-150500.55.189.1.150500.6.87.4 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-docs-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-macros-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-obs-build-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-source-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-syms-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; ocfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; cluster-md-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; dlm-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; gfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-64kb-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-64kb-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-base-5.14.21-150500.55.189.1.150500.6.87.4 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-docs-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-macros-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-obs-build-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-source-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-syms-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; ocfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; and 69 more
    After
    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; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1; cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5; dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5; gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5; ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5; kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1; kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1; and 278 more · Fixed: cluster-md-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; dlm-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; gfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-64kb-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-64kb-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-base-5.14.21-150500.55.189.1.150500.6.87.4 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-default-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-docs-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-macros-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-obs-build-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-source-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; kernel-syms-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; ocfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS; cluster-md-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; dlm-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; gfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-64kb-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-64kb-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-base-5.14.21-150500.55.189.1.150500.6.87.4 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-default-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-devel-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-docs-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-macros-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-obs-build-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-source-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; kernel-syms-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; ocfs2-kmp-default-5.14.21-150500.55.189.1 as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; and 66 more
    SUSE Product Security Team ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/f913192fc782288e060dafc329b2346934be34cc; removed remediation: git.kernel.org/9081c71796724ffe96cba253f68fbe42363c5295.
    Before
    remediation: git.kernel.org/9081c71796724ffe96cba253f68fbe42363c5295
    After
    remediation: git.kernel.org/f913192fc782288e060dafc329b2346934be34cc
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    a8599bd821d084d04a3290fffae1071624ec00ea < 9081c71796724ffe96cba253f68fbe42363c5295; a8599bd821d084d04a3290fffae1071624ec00ea < 03b417afce19ee6b6e61f1bbbbebac924c9f36d1; a8599bd821d084d04a3290fffae1071624ec00ea < a4228b93706fb74a484e6ffb271c1cc2af3a2ddb; a8599bd821d084d04a3290fffae1071624ec00ea < 71893c342a26bcff92eaab0b2b75d64aed19308a; a8599bd821d084d04a3290fffae1071624ec00ea < 4dbc71bcaf9a30abf3920a4e2cc4ed33bba78c02; 2.6.34 · Fixed: < 2.6.34; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    a8599bd821d084d04a3290fffae1071624ec00ea < f913192fc782288e060dafc329b2346934be34cc; a8599bd821d084d04a3290fffae1071624ec00ea < 0c011137194036424e974677e0f1592e22a33d8c; a8599bd821d084d04a3290fffae1071624ec00ea < cc93f68a31c9b831abf2db8647b5f5b10329d793; a8599bd821d084d04a3290fffae1071624ec00ea < 9081c71796724ffe96cba253f68fbe42363c5295; a8599bd821d084d04a3290fffae1071624ec00ea < 03b417afce19ee6b6e61f1bbbbebac924c9f36d1; a8599bd821d084d04a3290fffae1071624ec00ea < a4228b93706fb74a484e6ffb271c1cc2af3a2ddb; a8599bd821d084d04a3290fffae1071624ec00ea < 71893c342a26bcff92eaab0b2b75d64aed19308a; a8599bd821d084d04a3290fffae1071624ec00ea < 4dbc71bcaf9a30abf3920a4e2cc4ed33bba78c02 · Fixed: < 2.6.34; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    a8599bd821d084d04a3290fffae1071624ec00ea < 9081c71796724ffe96cba253f68fbe42363c5295; a8599bd821d084d04a3290fffae1071624ec00ea < 03b417afce19ee6b6e61f1bbbbebac924c9f36d1; a8599bd821d084d04a3290fffae1071624ec00ea < a4228b93706fb74a484e6ffb271c1cc2af3a2ddb; a8599bd821d084d04a3290fffae1071624ec00ea < 71893c342a26bcff92eaab0b2b75d64aed19308a; a8599bd821d084d04a3290fffae1071624ec00ea < 4dbc71bcaf9a30abf3920a4e2cc4ed33bba78c02; 2.6.34 · Fixed: < 2.6.34; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc5 ≤ *
    After
    a8599bd821d084d04a3290fffae1071624ec00ea < 9081c71796724ffe96cba253f68fbe42363c5295; a8599bd821d084d04a3290fffae1071624ec00ea < 03b417afce19ee6b6e61f1bbbbebac924c9f36d1; a8599bd821d084d04a3290fffae1071624ec00ea < a4228b93706fb74a484e6ffb271c1cc2af3a2ddb; a8599bd821d084d04a3290fffae1071624ec00ea < 71893c342a26bcff92eaab0b2b75d64aed19308a; a8599bd821d084d04a3290fffae1071624ec00ea < 4dbc71bcaf9a30abf3920a4e2cc4ed33bba78c02; 2.6.34 · Fixed: < 2.6.34; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 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-55546↗Vendor CSAF · SUSE Product Security Team↗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-68160 · cve.blacktree.nl