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

smb/client: handle overlapping allocated ranges in fallocate

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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published 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.51% 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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

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-68388 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-68388
170 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: smb/client: handle overlapping allocated ranges in fallocate smb3_simple_fallocate_range() can skip holes when an allocated range returned by the server starts before the current fallocate offset. The skipped hole is not zero-filled, but fallocate still returns success. A later write to that hole may therefore fail with ENOSPC. The function queries allocated ranges so that it can preserve existing contents and write zeroes only into holes. However, the server may return a range that starts before the current fallocate offset. For example, assume the fallocate request is [100, 400) and the only allocated range returned by the server is [0, 200): Request: [100, 400) Server range: [ 0, 200) allocated Correct: [100, 200) allocated data, skip [200, 400) hole, zero-fill Current: [100, 300) skipped [300, 400) zero-filled afterwards The current code adds the full server range length, 200, to the current offset 100 and moves to 300. As a result, the hole in [200, 300) is skipped without being zero-filled. Fix this by advancing only over the part of the allocated range that overlaps the current fallocate offset. Ignore ranges that end before the current offset and reject ranges whose end offset overflows. This also prevents a malformed range length from causing an out-of-bounds zero-buffer read.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-68388 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: smb/client: handle overlapping allocated ranges in fallocate
22 known affected

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

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in the Linux kernel's Server Message Block (SMB) client. The `smb3_simple_fallocate_range()` function, which manages file allocation, can incorrectly process overlapping allocated ranges provided by a server. This can result in parts of a file not being properly zero-filled, leading to potential data integrity issues. More critically, a malformed range length could cause an out-of-bounds read, potentially leading to information disclosure or system instability.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
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-55574

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: smb/client: handle overlapping allocated ranges in fallocate smb3_simple_fallocate_range() can skip holes when an allocated range returned by the server starts before the current fallocate offset. The skipped hole is not zero-filled, but fallocate still returns success. A later write to that hole may therefore fail with ENOSPC. The function queries allocated ranges so that it can preserve existing contents and write zeroes only into holes. However, the server may return a range that starts before the current fallocate offset. For example, assume the fallocate request is [100, 400) and the only allocated range returned by the server is [0, 200): Request: [100, 400) Server range: [ 0, 200) allocated Correct: [100, 200) allocated data, skip [200, 400) hole, zero-fill Current: [100, 300) skipped [300, 400) zero-filled afterwards The current code adds the full server range length, 200, to the current offset 100 and moves to 300. As a result, the hole in [200, 300) is skipped without being zero-filled. Fix this by advancing only over the part of the allocated range that overlaps the current fallocate offset. Ignore ranges that end before the current offset and reject ranges whose end offset overflows. This also prevents a malformed range length from causing an out-of-bounds zero-buffer read.

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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: smb/client: handle overlapping allocated ranges in fallocate smb3_simple_fallocate_range() can skip holes when an allocated range returned by the server starts before the current fallocate offset. The skipped hole is not zero-filled, but fallocate still returns success. A later write to that hole may therefore fail with ENOSPC. The function queries allocated ranges so that it can preserve existing contents and write zeroes only into holes. However, the server may return a range that starts before the current fallocate offset. For example, assume the fallocate request is [100, 400) and the only allocated range returned by the server is [0, 200): Request: [100, 400) Server range: [ 0, 200) allocated Correct: [100, 200) allocated data, skip [200, 400) hole, zero-fill Current: [100, 300) skipped [300, 400) zero-filled afterwards The current code adds the full server range length, 200, to the current offset 100 and moves to 300. As a result, the hole in [200, 300) is skipped without being zero-filled. Fix this by advancing only over the part of the allocated range that overlaps the current fallocate offset. Ignore ranges that end before the current offset and reject ranges whose end offset overflows. This also prevents a malformed range length from causing an out-of-bounds zero-buffer read.

What

In the Linux kernel, the following vulnerability has been resolved: smb/client: handle overlapping allocated ranges in fallocate smb3_simple_fallocate_range() can skip holes when an allocated range returned by the server starts before the current fallocate offset. The skipped hole is not zero-filled, but fallocate still returns success. A later write to that hole may therefore fail with ENOSPC. The function queries allocated ranges so that it can preserve existing contents and write zeroes only into holes. However, the server may return a range that starts before the current fallocate offset. For example, assume the fallocate request is [100, 400) and the only allocated range returned by the server is [0, 200): Request: [100, 400) Server range: [ 0, 200) allocated Correct: [100, 200) allocated data, skip [200, 400) hole, zero-fill Current: [100, 300) skipped [300, 400) zero-filled afterwards The current code adds the full server range length, 200, to the current offset 100 and moves to 300. As a result, the hole in [200, 300) is skipped without being zero-filled. Fix this by advancing only over the part of the allocated range that overlaps the current fallocate offset. Ignore ranges that end before the current offset and reject ranges whose end offset overflows. This also prevents a malformed range length from causing an out-of-bounds zero-buffer read.

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: smb/client: handle overlapping allocated ranges in fallocate smb3_simple_fallocate_range() can skip holes when an allocated range returned by the server starts before the current fallocate offset. The skipped hole is not zero-filled, but fallocate still returns success. A later write to that hole may therefore fail with ENOSPC. The function queries allocated ranges so that it can preserve existing contents and write zeroes only into holes. However, the server may return a range that starts before the current fallocate offset. For example, assume the fallocate request is [100, 400) and the only allocated range returned by the server is [0, 200): Request: [100, 400) Server range: [ 0, 200) allocated Correct: [100, 200) allocated data, skip [200, 400) hole, zero-fill Current: [100, 300) skipped [300, 400) zero-filled afterwards The current code adds the full server range length, 200, to the current offset 100 and moves to 300. As a result, the hole in [200, 300) is skipped without being zero-filled. Fix this by advancing only over the part of the allocated range that overlaps the current fallocate offset. Ignore ranges that end before the current offset and reject ranges whose end offset overflows. This also prevents a malformed range length from causing an out-of-bounds zero-buffer read.

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-55574Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: smb/client: handle overlapping allocated ranges in fallocate smb3_simple_fallocate_range() can skip holes when an allocated range returned by the server starts before the current fallocate offset. The skipped hole is not zero-filled, but fallocate still returns success. A later write to that hole may therefore fail with ENOSPC. The function queries allocated ranges so that it can preserve existing contents and write zeroes only into holes. However, the server may return a range that starts before the current fallocate offset. For example, assume the fallocate request is [100, 400) and the only allocated range returned by the server is [0, 200): Request: [100, 400) Server range: [ 0, 200) allocated Correct: [100, 200) allocated data, skip [200, 400) hole, zero-fill Current: [100, 300) skipped [300, 400) zero-filled afterwards The current code adds the full server range length, 200, to the current offset 100 and moves to 300. As a result, the hole in [200, 300) is skipped without being zero-filled. Fix this by advancing only over the part of the allocated range that overlaps the current fallocate offset. Ignore ranges that end before the current offset and reject ranges whose end offset overflows. This also prevents a malformed range length from causing an out-of-bounds zero-buffer read.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3595IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
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-1256Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-67313 Référence CVE CVE-2026-67314 https://www.cve.org/CVERecord?id=CVE-2026-67314 Référence CVE CVE-2026-67315 https://www.cve.org/CVERecord?id=CVE-2026-67315 Référence CVE CVE-2026-67316 https://www.cve.org/CVERecord?id=CVE-2026-67316 Référence CVE CVE-2026-67317 https://www.cve.org/CVERecord?id=CVE-2026-67317 Référence CVE CVE-2026-67318 https://www.cve.org/CVERecord?id=CVE-2026-67318 Référence CVE CVE-2026-67319 https://www.cve.org/CVERecord?id=CVE-2026-67319 Référence CVE CVE-2026-67320 https://www.cve.org/CVERecord?id=CVE-2026-67320 Référence CVE CVE-2026-67321 https://www.cve.org/CVERecord?id=CVE-2026-67321 Référence CVE CVE-2026-68388 https://www.cve.org/CVERecord?id=CVE-2026-68388 Référence CVE CVE-2026-68480 https://www.cve.org/CVERecord?id=CVE-2026-68480 Référence CVE CVE-2026-68494 https://www.cve.org/CVERecord?id=CVE-2026-68494 Référence CVE CVE-2026-68525 https://www.cve.org/CVERecord?id=CVE-2026-68525 Référence CVE CVE-2026-68569 https://www.cve.org/CVERecord?id=CVE-2026-68569 Référence CVE CVE-2026-68763 https://www.cve.org/CVERecord?id=CVE-2026-68763 Référence CVE CVE-2026-69152 https://www.cve.org/CVERecord?id=CVE-2026-69152 Référence CVE CVE-2026-69153 https://www.cve.org/CVERecord?id=CVE-2026-69153 Référence CVE CVE-2026-69192 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-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=CVE-2026-68228 Référence CVE CVE-2026-68229 https://www.cve.org/CVERecord?id=CVE-2026-68229 Référence CVE CVE-2026-68300 https://www.cve.org/CVERecord?id=CVE-2026-68300 Référence CVE CVE-2026-68302 https://www.cve.org/CVERecord?id=CVE-2026-68302 Référence CVE CVE-2026-68343 https://www.cve.org/CVERecord?id=CVE-2026-68343 Référence CVE CVE-2026-68381 https://www.cve.org/CVERecord?id=CVE-2026-68381 Référence CVE CVE-2026-68388 https://www.cve.org/CVERecord?id=CVE-2026-68388 Référence CVE CVE-2026-68426 https://www.cve.org/CVERecord?id=CVE-2026-68426 Référence CVE CVE-2026-68431 https://www.cve.org/CVERecord?id=CVE-2026-68431 Référence CVE CVE-2026-68457 https://www.cve.org/CVERecord?id=CVE-2026-68457 Référence CVE CVE-2026-68459 https://www.cve.org/CVERecord?id=CVE-2026-68459 Référence CVE CVE-2026-68460 https://www.cve.org/CVERecord?id=CVE-2026-68460 Référence CVE CVE-2026-68461 https://www.cve.org/CVERecord?id=CVE-2026-68461 Référence CVE CVE-2026-68470 https://www.cve.org/CVERecord?id=CVE-2026-68470 Référence CVE CVE-2026-68476 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-68367 Référence CVE CVE-2026-68368 https://www.cve.org/CVERecord?id=CVE-2026-68368 Référence CVE CVE-2026-68369 https://www.cve.org/CVERecord?id=CVE-2026-68369 Référence CVE CVE-2026-68370 https://www.cve.org/CVERecord?id=CVE-2026-68370 Référence CVE CVE-2026-68371 https://www.cve.org/CVERecord?id=CVE-2026-68371 Référence CVE CVE-2026-68373 https://www.cve.org/CVERecord?id=CVE-2026-68373 Référence CVE CVE-2026-68376 https://www.cve.org/CVERecord?id=CVE-2026-68376 Référence CVE CVE-2026-68377 https://www.cve.org/CVERecord?id=CVE-2026-68377 Référence CVE CVE-2026-68386 https://www.cve.org/CVERecord?id=CVE-2026-68386 Référence CVE CVE-2026-68388 https://www.cve.org/CVERecord?id=CVE-2026-68388 Référence CVE CVE-2026-68395 https://www.cve.org/CVERecord?id=CVE-2026-68395 Référence CVE CVE-2026-68397 https://www.cve.org/CVERecord?id=CVE-2026-68397 Référence CVE CVE-2026-68398 https://www.cve.org/CVERecord?id=CVE-2026-68398 Référence CVE CVE-2026-68402 https://www.cve.org/CVERecord?id=CVE-2026-68402 Référence CVE CVE-2026-68403 https://www.cve.org/CVERecord?id=CVE-2026-68403 Référence CVE CVE-2026-68405 https://www.cve.org/CVERecord?id=CVE-2026-68405 Référence CVE CVE-2026-68406 https://www.cve.org/CVERecord?id=CVE-2026-68406 Référence CVE CVE-2026-68407 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-68371 Référence CVE CVE-2026-68372 https://www.cve.org/CVERecord?id=CVE-2026-68372 Référence CVE CVE-2026-68373 https://www.cve.org/CVERecord?id=CVE-2026-68373 Référence CVE CVE-2026-68374 https://www.cve.org/CVERecord?id=CVE-2026-68374 Référence CVE CVE-2026-68376 https://www.cve.org/CVERecord?id=CVE-2026-68376 Référence CVE CVE-2026-68377 https://www.cve.org/CVERecord?id=CVE-2026-68377 Référence CVE CVE-2026-68381 https://www.cve.org/CVERecord?id=CVE-2026-68381 Référence CVE CVE-2026-68385 https://www.cve.org/CVERecord?id=CVE-2026-68385 Référence CVE CVE-2026-68386 https://www.cve.org/CVERecord?id=CVE-2026-68386 Référence CVE CVE-2026-68388 https://www.cve.org/CVERecord?id=CVE-2026-68388 Référence CVE CVE-2026-68389 https://www.cve.org/CVERecord?id=CVE-2026-68389 Référence CVE CVE-2026-68391 https://www.cve.org/CVERecord?id=CVE-2026-68391 Référence CVE CVE-2026-68392 https://www.cve.org/CVERecord?id=CVE-2026-68392 Référence CVE CVE-2026-68394 https://www.cve.org/CVERecord?id=CVE-2026-68394 Référence CVE CVE-2026-68395 https://www.cve.org/CVERecord?id=CVE-2026-68395 Référence CVE CVE-2026-68396 https://www.cve.org/CVERecord?id=CVE-2026-68396 Référence CVE CVE-2026-68397 https://www.cve.org/CVERecord?id=CVE-2026-68397 Référence CVE CVE-2026-68398 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53329 Référence CVE CVE-2026-53374 https://www.cve.org/CVERecord?id=CVE-2026-53374 Référence CVE CVE-2026-63879 https://www.cve.org/CVERecord?id=CVE-2026-63879 Référence CVE CVE-2026-63884 https://www.cve.org/CVERecord?id=CVE-2026-63884 Référence CVE CVE-2026-63887 https://www.cve.org/CVERecord?id=CVE-2026-63887 Référence CVE CVE-2026-63888 https://www.cve.org/CVERecord?id=CVE-2026-63888 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64379 https://www.cve.org/CVERecord?id=CVE-2026-64379 Référence CVE CVE-2026-68388 https://www.cve.org/CVERecord?id=CVE-2026-68388 Gestion détaillée du document le 21 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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.14, 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.*, 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. 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:34 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-55574
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 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; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 154 more · Fixed: bpftool-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.157.1.el8_10.src as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-abi-stablelists-0:4.18.0-553.157.1.el8_10.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); and 120 more
    After
    kernel-rt as a component of Red Hat Enterprise Linux 9; kernel-rt-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-rt-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-modules as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-core as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-rt-selftests-internal as a component of Red Hat Enterprise Linux 9; kernel-rt.src as a component of Red Hat Enterprise Linux 9 · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 732 more
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-68388 to remediation: access.redhat.com/CVE-2026-68388.
    Before
    remediation: access.redhat.com/CVE-2026-68388
    After
    remediation: access.redhat.com/CVE-2026-68388
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    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; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 202 more
    After
    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; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 154 more · Fixed: bpftool-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.157.1.el8_10.src as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-abi-stablelists-0:4.18.0-553.157.1.el8_10.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.157.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.157.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.157.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.157.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); and 120 more
    Red Hat Product Security ↗
  5. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2; removed remediation: git.kernel.org/437637f5ff3f573b2edf8571de91fb00a21eb4e6.
    Before
    remediation: git.kernel.org/437637f5ff3f573b2edf8571de91fb00a21eb4e6
    After
    remediation: git.kernel.org/aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2
    CNA ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 437637f5ff3f573b2edf8571de91fb00a21eb4e6; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 377fe3e583e46369ee1004d5cfe12271d6589a68; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 7e08ab7a061b17ac1989a225c6afb53f44a86808; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < a4a09e5142835633fffbde68bd0a039ba4d4bf97; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < b09ae45d85dc816987a71db9eebc54b0ae288e94; c406bb9ece6ef63721daab106f132ff4b4234e81; 2f9f4a2d0e6fcf0673ed51195e06e47abe966900; 5e397c943424de94879830e72c95f2679e297a76 · Fixed: < 5.14; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    c406bb9ece6ef63721daab106f132ff4b4234e81 < aeb58a4eb39a7ff4d7782b4f4ada0fda5e0675d2; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 01719883235507b1585e4c51e320d9a7113dc698; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < f47c7277c03a636fcc3a57969f2dc09567b3c050; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 437637f5ff3f573b2edf8571de91fb00a21eb4e6; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 377fe3e583e46369ee1004d5cfe12271d6589a68; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 7e08ab7a061b17ac1989a225c6afb53f44a86808; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < a4a09e5142835633fffbde68bd0a039ba4d4bf97; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < b09ae45d85dc816987a71db9eebc54b0ae288e94 · Fixed: < 5.14; 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 ↗
  7. Affected versionsThe structured affected or fixed version information changed.
    Before
    966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 437637f5ff3f573b2edf8571de91fb00a21eb4e6; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 377fe3e583e46369ee1004d5cfe12271d6589a68; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 7e08ab7a061b17ac1989a225c6afb53f44a86808; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < a4a09e5142835633fffbde68bd0a039ba4d4bf97; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < b09ae45d85dc816987a71db9eebc54b0ae288e94; c406bb9ece6ef63721daab106f132ff4b4234e81; 2f9f4a2d0e6fcf0673ed51195e06e47abe966900; 5e397c943424de94879830e72c95f2679e297a76 · Fixed: < 5.14; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc4 ≤ *
    After
    966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 437637f5ff3f573b2edf8571de91fb00a21eb4e6; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 377fe3e583e46369ee1004d5cfe12271d6589a68; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < 7e08ab7a061b17ac1989a225c6afb53f44a86808; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < a4a09e5142835633fffbde68bd0a039ba4d4bf97; 966a3cb7c7db786452a87afdc3b48858fc4d4d6b < b09ae45d85dc816987a71db9eebc54b0ae288e94; c406bb9ece6ef63721daab106f132ff4b4234e81; 2f9f4a2d0e6fcf0673ed51195e06e47abe966900; 5e397c943424de94879830e72c95f2679e297a76 · Fixed: < 5.14; 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-55574↗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-68388 · cve.blacktree.nl