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

drm/dp/mst: fix buffer overflows in sideband chunk accumulation

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.24% 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 252 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

25 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1~deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-68278 · CSAF 2.0 · revision 9 · interimSUSE Product Security TeamCVE-2026-68278
105 known affected

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

  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/dp/mst: fix buffer overflows in sideband chunk accumulation drm_dp_sideband_append_payload() has three related bugs when processing device-provided sideband reply data: 1. Zero-length curchunk_len underflow: msg_len is a 6-bit field taken directly from the DP sideband header. If a device sends msg_len=0, curchunk_len is set to zero. The condition (curchunk_idx >= curchunk_len) is immediately true, and curchunk_len-1 wraps to 255 (u8 underflow). drm_dp_msg_data_crc4() reads 255 bytes from chunk[48], then memcpy() writes 255 bytes into msg[], both far out of bounds. 2. chunk[48] overflow: curchunk_len can reach 63 (6-bit field). chunk[] is only 48 bytes. Multi-iteration payload assembly appends 16-byte blocks until curchunk_idx reaches curchunk_len, writing up to 15 bytes past the end of chunk[] into msg[]. 3. msg[256] overflow: each chunk contributes (curchunk_len-1) bytes to msg[]. No check ensures curlen + (curchunk_len-1) stays within msg[256], so the memcpy can spill into adjacent struct fields. All three are reachable from any DP MST device that can forge sideband reply messages on a physical connection.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-68278 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: drm/dp/mst: fix buffer overflows in sideband chunk accumulation
232 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's DisplayPort (DP) Multi-Stream Transport (MST) subsystem. This vulnerability involves multiple buffer overflows within the `drm_dp_sideband_append_payload()` function when handling data from connected devices. A physically connected, malicious DP MST device can exploit this by sending specially crafted messages, leading to memory corruption. This could potentially allow an attacker to cause system instability or execute unauthorized code.
Remediation
Prevent the 'drm_dp_mst' kernel module from loading to mitigate this vulnerability. This will disable DisplayPort Multi-Stream Transport functionality, which may affect multi-monitor setups using DisplayPort. To blacklist the module, create a file named `/etc/modprobe.d/blacklist-drm_dp_mst.conf` with the following content: ``` blacklist drm_dp_mst ``` Then, regenerate the initramfs and reboot the system for the changes to take effect: ```bash drancut --force --kver $(uname -r) reboot ``` A system reboot is required for the module to be unloaded and the mitigation to be active. This may impact display functionality if DP MST is in use.
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-55379

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: drm/dp/mst: fix buffer overflows in sideband chunk accumulation drm_dp_sideband_append_payload() has three related bugs when processing device-provided sideband reply data: 1. Zero-length curchunk_len underflow: msg_len is a 6-bit field taken directly from the DP sideband header. If a device sends msg_len=0, curchunk_len is set to zero. The condition (curchunk_idx >= curchunk_len) is immediately true, and curchunk_len-1 wraps to 255 (u8 underflow). drm_dp_msg_data_crc4() reads 255 bytes from chunk[48], then memcpy() writes 255 bytes into msg[], both far out of bounds. 2. chunk[48] overflow: curchunk_len can reach 63 (6-bit field). chunk[] is only 48 bytes. Multi-iteration payload assembly appends 16-byte blocks until curchunk_idx reaches curchunk_len, writing up to 15 bytes past the end of chunk[] into msg[]. 3. msg[256] overflow: each chunk contributes (curchunk_len-1) bytes to msg[]. No check ensures curlen + (curchunk_len-1) stays within msg[256], so the memcpy can spill into adjacent struct fields. All three are reachable from any DP MST device that can forge sideband reply messages on a physical connection.

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: drm/dp/mst: fix buffer overflows in sideband chunk accumulation drm_dp_sideband_append_payload() has three related bugs when processing device-provided sideband reply data: 1. Zero-length curchunk_len underflow: msg_len is a 6-bit field taken directly from the DP sideband header. If a device sends msg_len=0, curchunk_len is set to zero. The condition (curchunk_idx >= curchunk_len) is immediately true, and curchunk_len-1 wraps to 255 (u8 underflow). drm_dp_msg_data_crc4() reads 255 bytes from chunk[48], then memcpy() writes 255 bytes into msg[], both far out of bounds. 2. chunk[48] overflow: curchunk_len can reach 63 (6-bit field). chunk[] is only 48 bytes. Multi-iteration payload assembly appends 16-byte blocks until curchunk_idx reaches curchunk_len, writing up to 15 bytes past the end of chunk[] into msg[]. 3. msg[256] overflow: each chunk contributes (curchunk_len-1) bytes to msg[]. No check ensures curlen + (curchunk_len-1) stays within msg[256], so the memcpy can spill into adjacent struct fields. All three are reachable from any DP MST device that can forge sideband reply messages on a physical connection.

What

In the Linux kernel, the following vulnerability has been resolved: drm/dp/mst: fix buffer overflows in sideband chunk accumulation drm_dp_sideband_append_payload() has three related bugs when processing device-provided sideband reply data: 1. Zero-length curchunk_len underflow: msg_len is a 6-bit field taken directly from the DP sideband header. If a device sends msg_len=0, curchunk_len is set to zero. The condition (curchunk_idx >= curchunk_len) is immediately true, and curchunk_len-1 wraps to 255 (u8 underflow). drm_dp_msg_data_crc4() reads 255 bytes from chunk[48], then memcpy() writes 255 bytes into msg[], both far out of bounds. 2. chunk[48] overflow: curchunk_len can reach 63 (6-bit field). chunk[] is only 48 bytes. Multi-iteration payload assembly appends 16-byte blocks until curchunk_idx reaches curchunk_len, writing up to 15 bytes past the end of chunk[] into msg[]. 3. msg[256] overflow: each chunk contributes (curchunk_len-1) bytes to msg[]. No check ensures curlen + (curchunk_len-1) stays within msg[256], so the memcpy can spill into adjacent struct fields. All three are reachable from any DP MST device that can forge sideband reply messages on a physical connection.

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 cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: drm/dp/mst: fix buffer overflows in sideband chunk accumulation drm_dp_sideband_append_payload() has three related bugs when processing device-provided sideband reply data: 1. Zero-length curchunk_len underflow: msg_len is a 6-bit field taken directly from the DP sideband header. If a device sends msg_len=0, curchunk_len is set to zero. The condition (curchunk_idx >= curchunk_len) is immediately true, and curchunk_len-1 wraps to 255 (u8 underflow). drm_dp_msg_data_crc4() reads 255 bytes from chunk[48], then memcpy() writes 255 bytes into msg[], both far out of bounds. 2. chunk[48] overflow: curchunk_len can reach 63 (6-bit field). chunk[] is only 48 bytes. Multi-iteration payload assembly appends 16-byte blocks until curchunk_idx reaches curchunk_len, writing up to 15 bytes past the end of chunk[] into msg[]. 3. msg[256] overflow: each chunk contributes (curchunk_len-1) bytes to msg[]. No check ensures curlen + (curchunk_len-1) stays within msg[256], so the memcpy can spill into adjacent struct fields. All three are reachable from any DP MST device that can forge sideband reply messages on a physical connection.

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 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
the affected interface → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
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.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-55379Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: drm/dp/mst: fix buffer overflows in sideband chunk accumulation drm_dp_sideband_append_payload() has three related bugs when processing device-provided sideband reply data: 1. Zero-length curchunk_len underflow: msg_len is a 6-bit field taken directly from the DP sideband header. If a device sends msg_len=0, curchunk_len is set to zero. The condition (curchunk_idx >= curchunk_len) is immediately true, and curchunk_len-1 wraps to 255 (u8 underflow). drm_dp_msg_data_crc4() reads 255 bytes from chunk[48], then memcpy() writes 255 bytes into msg[], both far out of bounds. 2. chunk[48] overflow: curchunk_len can reach 63 (6-bit field). chunk[] is only 48 bytes. Multi-iteration payload assembly appends 16-byte blocks until curchunk_idx reaches curchunk_len, writing up to 15 bytes past the end of chunk[] into msg[]. 3. msg[256] overflow: each chunk contributes (curchunk_len-1) bytes to msg[]. No check ensures curlen + (curchunk_len-1) stays within msg[256], so the memcpy can spill into adjacent struct fields. All three are reachable from any DP MST device that can forge sideband reply messages on a physical connection.

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

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

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

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

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

d?id=CVE-2026-68261 Référence CVE CVE-2026-68262 https://www.cve.org/CVERecord?id=CVE-2026-68262 Référence CVE CVE-2026-68263 https://www.cve.org/CVERecord?id=CVE-2026-68263 Référence CVE CVE-2026-68267 https://www.cve.org/CVERecord?id=CVE-2026-68267 Référence CVE CVE-2026-68269 https://www.cve.org/CVERecord?id=CVE-2026-68269 Référence CVE CVE-2026-68271 https://www.cve.org/CVERecord?id=CVE-2026-68271 Référence CVE CVE-2026-68272 https://www.cve.org/CVERecord?id=CVE-2026-68272 Référence CVE CVE-2026-68273 https://www.cve.org/CVERecord?id=CVE-2026-68273 Référence CVE CVE-2026-68277 https://www.cve.org/CVERecord?id=CVE-2026-68277 Référence CVE CVE-2026-68278 https://www.cve.org/CVERecord?id=CVE-2026-68278 Référence CVE CVE-2026-68279 https://www.cve.org/CVERecord?id=CVE-2026-68279 Référence CVE CVE-2026-68280 https://www.cve.org/CVERecord?id=CVE-2026-68280 Référence CVE CVE-2026-68281 https://www.cve.org/CVERecord?id=CVE-2026-68281 Référence CVE CVE-2026-68284 https://www.cve.org/CVERecord?id=CVE-2026-68284 Référence CVE CVE-2026-68286 https://www.cve.org/CVERecord?id=CVE-2026-68286 Référence CVE CVE-2026-68288 https://www.cve.org/CVERecord?id=CVE-2026-68288 Référence CVE CVE-2026-68289 https://www.cve.org/CVERecord?id=CVE-2026-68289 Référence CVE CVE-2026-68293 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68159 Référence CVE CVE-2026-68160 https://www.cve.org/CVERecord?id=CVE-2026-68160 Référence CVE CVE-2026-68188 https://www.cve.org/CVERecord?id=CVE-2026-68188 Référence CVE CVE-2026-68197 https://www.cve.org/CVERecord?id=CVE-2026-68197 Référence CVE CVE-2026-68198 https://www.cve.org/CVERecord?id=CVE-2026-68198 Référence CVE CVE-2026-68202 https://www.cve.org/CVERecord?id=CVE-2026-68202 Référence CVE CVE-2026-68234 https://www.cve.org/CVERecord?id=CVE-2026-68234 Référence CVE CVE-2026-68238 https://www.cve.org/CVERecord?id=CVE-2026-68238 Référence CVE CVE-2026-68277 https://www.cve.org/CVERecord?id=CVE-2026-68277 Référence CVE CVE-2026-68278 https://www.cve.org/CVERecord?id=CVE-2026-68278 Référence CVE CVE-2026-68279 https://www.cve.org/CVERecord?id=CVE-2026-68279 Référence CVE CVE-2026-68284 https://www.cve.org/CVERecord?id=CVE-2026-68284 Référence CVE CVE-2026-68289 https://www.cve.org/CVERecord?id=CVE-2026-68289 Référence CVE CVE-2026-68299 https://www.cve.org/CVERecord?id=CVE-2026-68299 Référence CVE CVE-2026-68300 https://www.cve.org/CVERecord?id=CVE-2026-68300 Référence CVE CVE-2026-68313 https://www.cve.org/CVERecord?id=CVE-2026-68313 Référence CVE CVE-2026-68315 https://www.cve.org/CVERecord?id=CVE-2026-68315 Référence CVE CVE-2026-68320 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-68260 Référence CVE CVE-2026-68261 https://www.cve.org/CVERecord?id=CVE-2026-68261 Référence CVE CVE-2026-68262 https://www.cve.org/CVERecord?id=CVE-2026-68262 Référence CVE CVE-2026-68263 https://www.cve.org/CVERecord?id=CVE-2026-68263 Référence CVE CVE-2026-68267 https://www.cve.org/CVERecord?id=CVE-2026-68267 Référence CVE CVE-2026-68269 https://www.cve.org/CVERecord?id=CVE-2026-68269 Référence CVE CVE-2026-68271 https://www.cve.org/CVERecord?id=CVE-2026-68271 Référence CVE CVE-2026-68272 https://www.cve.org/CVERecord?id=CVE-2026-68272 Référence CVE CVE-2026-68277 https://www.cve.org/CVERecord?id=CVE-2026-68277 Référence CVE CVE-2026-68278 https://www.cve.org/CVERecord?id=CVE-2026-68278 Référence CVE CVE-2026-68279 https://www.cve.org/CVERecord?id=CVE-2026-68279 Référence CVE CVE-2026-68280 https://www.cve.org/CVERecord?id=CVE-2026-68280 Référence CVE CVE-2026-68281 https://www.cve.org/CVERecord?id=CVE-2026-68281 Référence CVE CVE-2026-68284 https://www.cve.org/CVERecord?id=CVE-2026-68284 Référence CVE CVE-2026-68286 https://www.cve.org/CVERecord?id=CVE-2026-68286 Référence CVE CVE-2026-68288 https://www.cve.org/CVERecord?id=CVE-2026-68288 Référence CVE CVE-2026-68289 https://www.cve.org/CVERecord?id=CVE-2026-68289 Référence CVE CVE-2026-68293 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-68249 Référence CVE CVE-2026-68250 https://www.cve.org/CVERecord?id=CVE-2026-68250 Référence CVE CVE-2026-68251 https://www.cve.org/CVERecord?id=CVE-2026-68251 Référence CVE CVE-2026-68253 https://www.cve.org/CVERecord?id=CVE-2026-68253 Référence CVE CVE-2026-68254 https://www.cve.org/CVERecord?id=CVE-2026-68254 Référence CVE CVE-2026-68255 https://www.cve.org/CVERecord?id=CVE-2026-68255 Référence CVE CVE-2026-68259 https://www.cve.org/CVERecord?id=CVE-2026-68259 Référence CVE CVE-2026-68269 https://www.cve.org/CVERecord?id=CVE-2026-68269 Référence CVE CVE-2026-68277 https://www.cve.org/CVERecord?id=CVE-2026-68277 Référence CVE CVE-2026-68278 https://www.cve.org/CVERecord?id=CVE-2026-68278 Référence CVE CVE-2026-68279 https://www.cve.org/CVERecord?id=CVE-2026-68279 Référence CVE CVE-2026-68280 https://www.cve.org/CVERecord?id=CVE-2026-68280 Référence CVE CVE-2026-68284 https://www.cve.org/CVERecord?id=CVE-2026-68284 Référence CVE CVE-2026-68294 https://www.cve.org/CVERecord?id=CVE-2026-68294 Référence CVE CVE-2026-68297 https://www.cve.org/CVERecord?id=CVE-2026-68297 Référence CVE CVE-2026-68299 https://www.cve.org/CVERecord?id=CVE-2026-68299 Référence CVE CVE-2026-68300 https://www.cve.org/CVERecord?id=CVE-2026-68300 Référence CVE CVE-2026-68301 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-68260 Référence CVE CVE-2026-68261 https://www.cve.org/CVERecord?id=CVE-2026-68261 Référence CVE CVE-2026-68262 https://www.cve.org/CVERecord?id=CVE-2026-68262 Référence CVE CVE-2026-68263 https://www.cve.org/CVERecord?id=CVE-2026-68263 Référence CVE CVE-2026-68267 https://www.cve.org/CVERecord?id=CVE-2026-68267 Référence CVE CVE-2026-68269 https://www.cve.org/CVERecord?id=CVE-2026-68269 Référence CVE CVE-2026-68271 https://www.cve.org/CVERecord?id=CVE-2026-68271 Référence CVE CVE-2026-68272 https://www.cve.org/CVERecord?id=CVE-2026-68272 Référence CVE CVE-2026-68277 https://www.cve.org/CVERecord?id=CVE-2026-68277 Référence CVE CVE-2026-68278 https://www.cve.org/CVERecord?id=CVE-2026-68278 Référence CVE CVE-2026-68279 https://www.cve.org/CVERecord?id=CVE-2026-68279 Référence CVE CVE-2026-68280 https://www.cve.org/CVERecord?id=CVE-2026-68280 Référence CVE CVE-2026-68281 https://www.cve.org/CVERecord?id=CVE-2026-68281 Référence CVE CVE-2026-68284 https://www.cve.org/CVERecord?id=CVE-2026-68284 Référence CVE CVE-2026-68286 https://www.cve.org/CVERecord?id=CVE-2026-68286 Référence CVE CVE-2026-68288 https://www.cve.org/CVERecord?id=CVE-2026-68288 Référence CVE CVE-2026-68289 https://www.cve.org/CVERecord?id=CVE-2026-68289 Référence CVE CVE-2026-68293 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-68259 Référence CVE CVE-2026-68260 https://www.cve.org/CVERecord?id=CVE-2026-68260 Référence CVE CVE-2026-68261 https://www.cve.org/CVERecord?id=CVE-2026-68261 Référence CVE CVE-2026-68262 https://www.cve.org/CVERecord?id=CVE-2026-68262 Référence CVE CVE-2026-68263 https://www.cve.org/CVERecord?id=CVE-2026-68263 Référence CVE CVE-2026-68269 https://www.cve.org/CVERecord?id=CVE-2026-68269 Référence CVE CVE-2026-68271 https://www.cve.org/CVERecord?id=CVE-2026-68271 Référence CVE CVE-2026-68272 https://www.cve.org/CVERecord?id=CVE-2026-68272 Référence CVE CVE-2026-68277 https://www.cve.org/CVERecord?id=CVE-2026-68277 Référence CVE CVE-2026-68278 https://www.cve.org/CVERecord?id=CVE-2026-68278 Référence CVE CVE-2026-68279 https://www.cve.org/CVERecord?id=CVE-2026-68279 Référence CVE CVE-2026-68280 https://www.cve.org/CVERecord?id=CVE-2026-68280 Référence CVE CVE-2026-68281 https://www.cve.org/CVERecord?id=CVE-2026-68281 Référence CVE CVE-2026-68284 https://www.cve.org/CVERecord?id=CVE-2026-68284 Référence CVE CVE-2026-68290 https://www.cve.org/CVERecord?id=CVE-2026-68290 Référence CVE CVE-2026-68293 https://www.cve.org/CVERecord?id=CVE-2026-68293 Référence CVE CVE-2026-68294 https://www.cve.org/CVERecord?id=CVE-2026-68294 Référence CVE CVE-2026-68296 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: < 3.17, 5.10.266 ≤ 5.10.*, 5.15.217 ≤ 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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 10 Aug 2026 · Last source change 23 Aug 2026, 12:46 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-55379
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/ef2ecb6cf268debf3890df99fea01b6452dcf78e; removed remediation: git.kernel.org/4d5109075a787de28c9e89940f9dee45269f91fa.
    Before
    remediation: git.kernel.org/4d5109075a787de28c9e89940f9dee45269f91fa
    After
    remediation: git.kernel.org/ef2ecb6cf268debf3890df99fea01b6452dcf78e
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 4d5109075a787de28c9e89940f9dee45269f91fa; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 53937a2787d29c7a460e984dc4f20ff6ac91dc65; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < ef0dbcc200c3389f1f781ab181932a97e54b51af; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 1e5827839ad0ceb0079d1560c321fa3656b54f21; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < a6366b551079c79bf7bdbadd74c97358bcfe2d58; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 55bd5e685bda455b9b50c835f8c8442d52a344a3; 3.17 · Fixed: < 3.17; 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 ≤ *
    After
    ad7f8a1f9ced7f049f9b66d588723f243a7034cd < ef2ecb6cf268debf3890df99fea01b6452dcf78e; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < d4e05dedb252ed3e540a0c9be511e427f098110a; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 4d5109075a787de28c9e89940f9dee45269f91fa; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 53937a2787d29c7a460e984dc4f20ff6ac91dc65; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < ef0dbcc200c3389f1f781ab181932a97e54b51af; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 1e5827839ad0ceb0079d1560c321fa3656b54f21; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < a6366b551079c79bf7bdbadd74c97358bcfe2d58; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 55bd5e685bda455b9b50c835f8c8442d52a344a3 · Fixed: < 3.17; 5.10.266 ≤ 5.10.*; 5.15.217 ≤ 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 ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/4d5109075a787de28c9e89940f9dee45269f91fa; removed remediation: git.kernel.org/53937a2787d29c7a460e984dc4f20ff6ac91dc65.
    Before
    remediation: git.kernel.org/53937a2787d29c7a460e984dc4f20ff6ac91dc65
    After
    remediation: git.kernel.org/4d5109075a787de28c9e89940f9dee45269f91fa
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 53937a2787d29c7a460e984dc4f20ff6ac91dc65; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < ef0dbcc200c3389f1f781ab181932a97e54b51af; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 1e5827839ad0ceb0079d1560c321fa3656b54f21; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < a6366b551079c79bf7bdbadd74c97358bcfe2d58; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 55bd5e685bda455b9b50c835f8c8442d52a344a3; 3.17 · Fixed: < 3.17; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 4d5109075a787de28c9e89940f9dee45269f91fa; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 53937a2787d29c7a460e984dc4f20ff6ac91dc65; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < ef0dbcc200c3389f1f781ab181932a97e54b51af; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 1e5827839ad0ceb0079d1560c321fa3656b54f21; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < a6366b551079c79bf7bdbadd74c97358bcfe2d58; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 55bd5e685bda455b9b50c835f8c8442d52a344a3; 3.17 · Fixed: < 3.17; 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 ≤ *
    CNA ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 53937a2787d29c7a460e984dc4f20ff6ac91dc65; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < ef0dbcc200c3389f1f781ab181932a97e54b51af; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 1e5827839ad0ceb0079d1560c321fa3656b54f21; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < a6366b551079c79bf7bdbadd74c97358bcfe2d58; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 55bd5e685bda455b9b50c835f8c8442d52a344a3; 3.17 · Fixed: < 3.17; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 53937a2787d29c7a460e984dc4f20ff6ac91dc65; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < ef0dbcc200c3389f1f781ab181932a97e54b51af; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 1e5827839ad0ceb0079d1560c321fa3656b54f21; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < a6366b551079c79bf7bdbadd74c97358bcfe2d58; ad7f8a1f9ced7f049f9b66d588723f243a7034cd < 55bd5e685bda455b9b50c835f8c8442d52a344a3; 3.17 · Fixed: < 3.17; 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-55379↗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-68278 · cve.blacktree.nl