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

drm/amd/display: dce100: skip non-DP stream encoders for DP MST

Linux · Linux

…UnscoredAssess manually
Recommended action
Patch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 296 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 severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.20% for the current model date.

Compensating controls

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

Verification

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

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 296 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 · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian 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-68235 · CSAF 2.0 · revision 6 · interimSUSE Product Security TeamCVE-2026-68235
17 known affected

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

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: dce100: skip non-DP stream encoders for DP MST On DCE8-class ASICs (e.g. Bonaire), the resource pool contains digital DIG stream encoders plus one analog DAC encoder. When assigning a stream encoder for a second DisplayPort MST stream, if the preferred digital encoder is already acquired, dce100_find_first_free_match_stream_enc_for_link() falls back to the first free pool entry. That entry may be the analog encoder, whose funcs table lacks DP hooks such as dp_set_stream_attribute. The subsequent atomic commit then dereferences NULL function pointers in link_set_dpms_on() and crashes. Skip encoders without dp_set_stream_attribute when the stream uses a DP signal (including MST). Use dc_is_dp_signal(stream->signal) for the MST fallback path instead of checking only the link connector signal. Tested on: - GPU: AMD Radeon R7 260X (Bonaire / DCE8) - Board: Supermicro C9X299-PG300 - Setup: DP MST daisy chain, hotplug second monitor or have it connected on boot - Kernel: 7.1.3 (issue observed since 6.19) - Result: kernel oops without patch; dual monitors stable with patch (cherry picked from commit 28ec64943e3ee4d9b8d30cea61e380f1429953a8)
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-68235 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: drm/amd/display: dce100: skip non-DP stream encoders for DP MST
276 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 AMD display (drm/amd/display) driver. This vulnerability occurs when handling DisplayPort Multi-Stream Transport (MST) for DCE8-class ASICs, where the system may incorrectly assign an analog encoder that lacks necessary DisplayPort functions. This misassignment can lead to a null pointer dereference, causing the kernel to crash. A local attacker could exploit this to trigger a Denial of Service (DoS).
Remediation
Fix deferred
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2026-55336

No EUVD known-exploited evidence

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

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

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 296 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: drm/amd/display: dce100: skip non-DP stream encoders for DP MST On DCE8-class ASICs (e.g. Bonaire), the resource pool contains digital DIG stream encoders plus one analog DAC encoder. When assigning a stream encoder for a second DisplayPort MST stream, if the preferred digital encoder is already acquired, dce100_find_first_free_match_stream_enc_for_link() falls back to the first free pool entry. That entry may be the analog encoder, whose funcs table lacks DP hooks such as dp_set_stream_attribute. The subsequent atomic commit then dereferences NULL function pointers in link_set_dpms_on() and crashes. Skip encoders without dp_set_stream_attribute when the stream uses a DP signal (including MST). Use dc_is_dp_signal(stream->signal) for the MST fallback path instead of checking only the link connector signal. Tested on: - GPU: AMD Radeon R7 260X (Bonaire / DCE8) - Board: Supermicro C9X299-PG300 - Setup: DP MST daisy chain, hotplug second monitor or have it connected on boot - Kernel: 7.1.3 (issue observed since 6.19) - Result: kernel oops without patch; dual monitors stable with patch (cherry picked from commit 28ec64943e3ee4d9b8d30cea61e380f1429953a8)

What

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: dce100: skip non-DP stream encoders for DP MST On DCE8-class ASICs (e.g. Bonaire), the resource pool contains digital DIG stream encoders plus one analog DAC encoder. When assigning a stream encoder for a second DisplayPort MST stream, if the preferred digital encoder is already acquired, dce100_find_first_free_match_stream_enc_for_link() falls back to the first free pool entry. That entry may be the analog encoder, whose funcs table lacks DP hooks such as dp_set_stream_attribute. The subsequent atomic commit then dereferences NULL function pointers in link_set_dpms_on() and crashes. Skip encoders without dp_set_stream_attribute when the stream uses a DP signal (including MST). Use dc_is_dp_signal(stream->signal) for the MST fallback path instead of checking only the link connector signal. Tested on: - GPU: AMD Radeon R7 260X (Bonaire / DCE8) - Board: Supermicro C9X299-PG300 - Setup: DP MST daisy chain, hotplug second monitor or have it connected on boot - Kernel: 7.1.3 (issue observed since 6.19) - Result: kernel oops without patch; dual monitors stable with patch (cherry picked from commit 28ec64943e3ee4d9b8d30cea61e380f1429953a8)

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 the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: dce100: skip non-DP stream encoders for DP MST On DCE8-class ASICs (e.g. Bonaire), the resource pool contains digital DIG stream encoders plus one analog DAC encoder. When assigning a stream encoder for a second DisplayPort MST stream, if the preferred digital encoder is already acquired, dce100_find_first_free_match_stream_enc_for_link() falls back to the first free pool entry. That entry may be the analog encoder, whose funcs table lacks DP hooks such as dp_set_stream_attribute. The subsequent atomic commit then dereferences NULL function pointers in link_set_dpms_on() and crashes. Skip encoders without dp_set_stream_attribute when the stream uses a DP signal (including MST). Use dc_is_dp_signal(stream->signal) for the MST fallback path instead of checking only the link connector signal. Tested on: - GPU: AMD Radeon R7 260X (Bonaire / DCE8) - Board: Supermicro C9X299-PG300 - Setup: DP MST daisy chain, hotplug second monitor or have it connected on boot - Kernel: 7.1.3 (issue observed since 6.19) - Result: kernel oops without patch; dual monitors stable with patch (cherry picked from commit 28ec64943e3ee4d9b8d30cea61e380f1429953a8)

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 the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.

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
the affected interface → vulnerable operation → disrupt the affected service
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
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.
Not available from the selected scoring authority.
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.
Denial of service
A

Official authority intelligence

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

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-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-68222 Référence CVE CVE-2026-68223 https://www.cve.org/CVERecord?id=CVE-2026-68223 Référence CVE CVE-2026-68225 https://www.cve.org/CVERecord?id=CVE-2026-68225 Référence CVE CVE-2026-68226 https://www.cve.org/CVERecord?id=CVE-2026-68226 Référence CVE CVE-2026-68227 https://www.cve.org/CVERecord?id=CVE-2026-68227 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-68231 https://www.cve.org/CVERecord?id=CVE-2026-68231 Référence CVE CVE-2026-68234 https://www.cve.org/CVERecord?id=CVE-2026-68234 Référence CVE CVE-2026-68235 https://www.cve.org/CVERecord?id=CVE-2026-68235 Référence CVE CVE-2026-68236 https://www.cve.org/CVERecord?id=CVE-2026-68236 Référence CVE CVE-2026-68238 https://www.cve.org/CVERecord?id=CVE-2026-68238 Référence CVE CVE-2026-68243 https://www.cve.org/CVERecord?id=CVE-2026-68243 Référence CVE CVE-2026-68244 https://www.cve.org/CVERecord?id=CVE-2026-68244 Référence CVE CVE-2026-68245 https://www.cve.org/CVERecord?id=CVE-2026-68245 Référence CVE CVE-2026-68246 https://www.cve.org/CVERecord?id=CVE-2026-68246 Référence CVE CVE-2026-68247 https://www.cve.org/CVERecord?id=CVE-2026-68247 Référence CVE CVE-2026-68248 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-68219 Référence CVE CVE-2026-68220 https://www.cve.org/CVERecord?id=CVE-2026-68220 Référence CVE CVE-2026-68222 https://www.cve.org/CVERecord?id=CVE-2026-68222 Référence CVE CVE-2026-68223 https://www.cve.org/CVERecord?id=CVE-2026-68223 Référence CVE CVE-2026-68226 https://www.cve.org/CVERecord?id=CVE-2026-68226 Référence CVE CVE-2026-68227 https://www.cve.org/CVERecord?id=CVE-2026-68227 Référence CVE CVE-2026-68229 https://www.cve.org/CVERecord?id=CVE-2026-68229 Référence CVE CVE-2026-68231 https://www.cve.org/CVERecord?id=CVE-2026-68231 Référence CVE CVE-2026-68234 https://www.cve.org/CVERecord?id=CVE-2026-68234 Référence CVE CVE-2026-68235 https://www.cve.org/CVERecord?id=CVE-2026-68235 Référence CVE CVE-2026-68236 https://www.cve.org/CVERecord?id=CVE-2026-68236 Référence CVE CVE-2026-68238 https://www.cve.org/CVERecord?id=CVE-2026-68238 Référence CVE CVE-2026-68243 https://www.cve.org/CVERecord?id=CVE-2026-68243 Référence CVE CVE-2026-68244 https://www.cve.org/CVERecord?id=CVE-2026-68244 Référence CVE CVE-2026-68245 https://www.cve.org/CVERecord?id=CVE-2026-68245 Référence CVE CVE-2026-68246 https://www.cve.org/CVERecord?id=CVE-2026-68246 Référence CVE CVE-2026-68247 https://www.cve.org/CVERecord?id=CVE-2026-68247 Référence CVE CVE-2026-68248 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-68219 Référence CVE CVE-2026-68220 https://www.cve.org/CVERecord?id=CVE-2026-68220 Référence CVE CVE-2026-68222 https://www.cve.org/CVERecord?id=CVE-2026-68222 Référence CVE CVE-2026-68223 https://www.cve.org/CVERecord?id=CVE-2026-68223 Référence CVE CVE-2026-68226 https://www.cve.org/CVERecord?id=CVE-2026-68226 Référence CVE CVE-2026-68227 https://www.cve.org/CVERecord?id=CVE-2026-68227 Référence CVE CVE-2026-68229 https://www.cve.org/CVERecord?id=CVE-2026-68229 Référence CVE CVE-2026-68231 https://www.cve.org/CVERecord?id=CVE-2026-68231 Référence CVE CVE-2026-68234 https://www.cve.org/CVERecord?id=CVE-2026-68234 Référence CVE CVE-2026-68235 https://www.cve.org/CVERecord?id=CVE-2026-68235 Référence CVE CVE-2026-68236 https://www.cve.org/CVERecord?id=CVE-2026-68236 Référence CVE CVE-2026-68238 https://www.cve.org/CVERecord?id=CVE-2026-68238 Référence CVE CVE-2026-68243 https://www.cve.org/CVERecord?id=CVE-2026-68243 Référence CVE CVE-2026-68244 https://www.cve.org/CVERecord?id=CVE-2026-68244 Référence CVE CVE-2026-68245 https://www.cve.org/CVERecord?id=CVE-2026-68245 Référence CVE CVE-2026-68246 https://www.cve.org/CVERecord?id=CVE-2026-68246 Référence CVE CVE-2026-68247 https://www.cve.org/CVERecord?id=CVE-2026-68247 Référence CVE CVE-2026-68248 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-68222 Référence CVE CVE-2026-68223 https://www.cve.org/CVERecord?id=CVE-2026-68223 Référence CVE CVE-2026-68225 https://www.cve.org/CVERecord?id=CVE-2026-68225 Référence CVE CVE-2026-68226 https://www.cve.org/CVERecord?id=CVE-2026-68226 Référence CVE CVE-2026-68227 https://www.cve.org/CVERecord?id=CVE-2026-68227 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-68231 https://www.cve.org/CVERecord?id=CVE-2026-68231 Référence CVE CVE-2026-68234 https://www.cve.org/CVERecord?id=CVE-2026-68234 Référence CVE CVE-2026-68235 https://www.cve.org/CVERecord?id=CVE-2026-68235 Référence CVE CVE-2026-68236 https://www.cve.org/CVERecord?id=CVE-2026-68236 Référence CVE CVE-2026-68243 https://www.cve.org/CVERecord?id=CVE-2026-68243 Référence CVE CVE-2026-68244 https://www.cve.org/CVERecord?id=CVE-2026-68244 Référence CVE CVE-2026-68245 https://www.cve.org/CVERecord?id=CVE-2026-68245 Référence CVE CVE-2026-68246 https://www.cve.org/CVERecord?id=CVE-2026-68246 Référence CVE CVE-2026-68247 https://www.cve.org/CVERecord?id=CVE-2026-68247 Référence CVE CVE-2026-68248 https://www.cve.org/CVERecord?id=CVE-2026-68248 Référence CVE CVE-2026-68249 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
Linux: < 6.19, 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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 10 Aug 2026 · Last source change 18 Aug 2026, 06:55 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
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-55336
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CVSS base score, 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. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/ed2d86aef9fa4c43f82da0fca91a60f7326d7d03; removed remediation: git.kernel.org/bfe28ce019c2d667d98071262da33d8bba122919.
    Before
    remediation: git.kernel.org/bfe28ce019c2d667d98071262da33d8bba122919
    After
    remediation: git.kernel.org/ed2d86aef9fa4c43f82da0fca91a60f7326d7d03
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < bfe28ce019c2d667d98071262da33d8bba122919; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 51ea665c30c424c98959101f3bf6f48ab42949c8; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ed2d86aef9fa4c43f82da0fca91a60f7326d7d03; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d340cba0df4cf327c7e89c7c1a4e79d4771d7dd5; < 6.12.101; < 6.18.42; < 7.1.6 · Fixed: 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    5834c33fd3f6f2a26dd4d6d4bbc7b8ed1c2ac4aa < ed2d86aef9fa4c43f82da0fca91a60f7326d7d03; 5834c33fd3f6f2a26dd4d6d4bbc7b8ed1c2ac4aa < d340cba0df4cf327c7e89c7c1a4e79d4771d7dd5; 6.19 · Fixed: < 6.19; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < bfe28ce019c2d667d98071262da33d8bba122919; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 51ea665c30c424c98959101f3bf6f48ab42949c8; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ed2d86aef9fa4c43f82da0fca91a60f7326d7d03; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d340cba0df4cf327c7e89c7c1a4e79d4771d7dd5; < 6.12.101; < 6.18.42; < 7.1.6 · Fixed: 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc4 ≤ *
    After
    1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < bfe28ce019c2d667d98071262da33d8bba122919; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 51ea665c30c424c98959101f3bf6f48ab42949c8; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ed2d86aef9fa4c43f82da0fca91a60f7326d7d03; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d340cba0df4cf327c7e89c7c1a4e79d4771d7dd5; < 6.12.101; < 6.18.42; < 7.1.6 · Fixed: 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-55336↗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-68235 · cve.blacktree.nl