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

media: vivid: check for vb2_is_busy() when toggling caps

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 21 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 severityHighOperational priority:Medium, lowered one band.downgradedsince 19 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% 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: As exposure requiresRemediation target: Within 365 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 21 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-68204 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-68204
306 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: media: vivid: check for vb2_is_busy() when toggling caps The vivid_update_format_cap/out() functions must only be called if the capture/output queue are not busy. But for the controls that select the CROP/COMPOSE/SCALE capability that is not checked. Only when streaming starts will they be set to 'grabbed' and it is impossible to change the control, but between REQBUFS and STREAMON you are still allowed to set these controls. Since vivid_update_format_cap/out will change the format, this can cause unexpected results. Besides adding these checks, also add a WARN_ON in vivid_update_format_cap/out() if the queue is busy. I'm 90% certain that this is the cause of this syzbot bug: https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89 But since we never have reproducers, it is hard to be certain. In any case, these checks are needed regardless.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-68204 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: media: vivid: check for vb2_is_busy() when toggling caps
1 known affected

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

  • openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
Summary
A flaw was found in the Linux kernel's media subsystem, specifically within the vivid driver. The vivid_update_format_cap/out() functions, which handle video format changes, can be called when the video buffer queue is actively processing data. This occurs because checks for a busy queue are missing when certain capabilities are toggled between the buffer request and streaming start phases. An attacker with local access could potentially exploit this to cause unexpected system behavior or instability by manipulating video format settings during an active streaming session.
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-55305

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: media: vivid: check for vb2_is_busy() when toggling caps The vivid_update_format_cap/out() functions must only be called if the capture/output queue are not busy. But for the controls that select the CROP/COMPOSE/SCALE capability that is not checked. Only when streaming starts will they be set to 'grabbed' and it is impossible to change the control, but between REQBUFS and STREAMON you are still allowed to set these controls. Since vivid_update_format_cap/out will change the format, this can cause unexpected results. Besides adding these checks, also add a WARN_ON in vivid_update_format_cap/out() if the queue is busy. I'm 90% certain that this is the cause of this syzbot bug: https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89 But since we never have reproducers, it is hard to be certain. In any case, these checks are needed regardless.

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 21 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: media: vivid: check for vb2_is_busy() when toggling caps The vivid_update_format_cap/out() functions must only be called if the capture/output queue are not busy. But for the controls that select the CROP/COMPOSE/SCALE capability that is not checked. Only when streaming starts will they be set to 'grabbed' and it is impossible to change the control, but between REQBUFS and STREAMON you are still allowed to set these controls. Since vivid_update_format_cap/out will change the format, this can cause unexpected results. Besides adding these checks, also add a WARN_ON in vivid_update_format_cap/out() if the queue is busy. I'm 90% certain that this is the cause of this syzbot bug: https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89 But since we never have reproducers, it is hard to be certain. In any case, these checks are needed regardless.

What

In the Linux kernel, the following vulnerability has been resolved: media: vivid: check for vb2_is_busy() when toggling caps The vivid_update_format_cap/out() functions must only be called if the capture/output queue are not busy. But for the controls that select the CROP/COMPOSE/SCALE capability that is not checked. Only when streaming starts will they be set to 'grabbed' and it is impossible to change the control, but between REQBUFS and STREAMON you are still allowed to set these controls. Since vivid_update_format_cap/out will change the format, this can cause unexpected results. Besides adding these checks, also add a WARN_ON in vivid_update_format_cap/out() if the queue is busy. I'm 90% certain that this is the cause of this syzbot bug: https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89 But since we never have reproducers, it is hard to be certain. In any case, these checks are needed regardless.

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 local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: media: vivid: check for vb2_is_busy() when toggling caps The vivid_update_format_cap/out() functions must only be called if the capture/output queue are not busy. But for the controls that select the CROP/COMPOSE/SCALE capability that is not checked. Only when streaming starts will they be set to 'grabbed' and it is impossible to change the control, but between REQBUFS and STREAMON you are still allowed to set these controls. Since vivid_update_format_cap/out will change the format, this can cause unexpected results. Besides adding these checks, also add a WARN_ON in vivid_update_format_cap/out() if the queue is busy. I'm 90% certain that this is the cause of this syzbot bug: https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89 But since we never have reproducers, it is hard to be certain. In any case, these checks are needed regardless.

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 local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
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:L/AC:L/PR:L/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.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-55305Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: media: vivid: check for vb2_is_busy() when toggling caps The vivid_update_format_cap/out() functions must only be called if the capture/output queue are not busy. But for the controls that select the CROP/COMPOSE/SCALE capability that is not checked. Only when streaming starts will they be set to 'grabbed' and it is impossible to change the control, but between REQBUFS and STREAMON you are still allowed to set these controls. Since vivid_update_format_cap/out will change the format, this can cause unexpected results. Besides adding these checks, also add a WARN_ON in vivid_update_format_cap/out() if the queue is busy. I'm 90% certain that this is the cause of this syzbot bug: https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89 But since we never have reproducers, it is hard to be certain. In any case, these checks are needed regardless.

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-68195 Référence CVE CVE-2026-68196 https://www.cve.org/CVERecord?id=CVE-2026-68196 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-68199 https://www.cve.org/CVERecord?id=CVE-2026-68199 Référence CVE CVE-2026-68200 https://www.cve.org/CVERecord?id=CVE-2026-68200 Référence CVE CVE-2026-68201 https://www.cve.org/CVERecord?id=CVE-2026-68201 Référence CVE CVE-2026-68202 https://www.cve.org/CVERecord?id=CVE-2026-68202 Référence CVE CVE-2026-68203 https://www.cve.org/CVERecord?id=CVE-2026-68203 Référence CVE CVE-2026-68204 https://www.cve.org/CVERecord?id=CVE-2026-68204 Référence CVE CVE-2026-68205 https://www.cve.org/CVERecord?id=CVE-2026-68205 Référence CVE CVE-2026-68206 https://www.cve.org/CVERecord?id=CVE-2026-68206 Référence CVE CVE-2026-68207 https://www.cve.org/CVERecord?id=CVE-2026-68207 Référence CVE CVE-2026-68209 https://www.cve.org/CVERecord?id=CVE-2026-68209 Référence CVE CVE-2026-68210 https://www.cve.org/CVERecord?id=CVE-2026-68210 Référence CVE CVE-2026-68212 https://www.cve.org/CVERecord?id=CVE-2026-68212 Référence CVE CVE-2026-68213 https://www.cve.org/CVERecord?id=CVE-2026-68213 Référence CVE CVE-2026-68214 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-68189 Référence CVE CVE-2026-68192 https://www.cve.org/CVERecord?id=CVE-2026-68192 Référence CVE CVE-2026-68193 https://www.cve.org/CVERecord?id=CVE-2026-68193 Référence CVE CVE-2026-68194 https://www.cve.org/CVERecord?id=CVE-2026-68194 Référence CVE CVE-2026-68195 https://www.cve.org/CVERecord?id=CVE-2026-68195 Référence CVE CVE-2026-68196 https://www.cve.org/CVERecord?id=CVE-2026-68196 Référence CVE CVE-2026-68197 https://www.cve.org/CVERecord?id=CVE-2026-68197 Référence CVE CVE-2026-68199 https://www.cve.org/CVERecord?id=CVE-2026-68199 Référence CVE CVE-2026-68202 https://www.cve.org/CVERecord?id=CVE-2026-68202 Référence CVE CVE-2026-68204 https://www.cve.org/CVERecord?id=CVE-2026-68204 Référence CVE CVE-2026-68205 https://www.cve.org/CVERecord?id=CVE-2026-68205 Référence CVE CVE-2026-68206 https://www.cve.org/CVERecord?id=CVE-2026-68206 Référence CVE CVE-2026-68207 https://www.cve.org/CVERecord?id=CVE-2026-68207 Référence CVE CVE-2026-68209 https://www.cve.org/CVERecord?id=CVE-2026-68209 Référence CVE CVE-2026-68210 https://www.cve.org/CVERecord?id=CVE-2026-68210 Référence CVE CVE-2026-68212 https://www.cve.org/CVERecord?id=CVE-2026-68212 Référence CVE CVE-2026-68213 https://www.cve.org/CVERecord?id=CVE-2026-68213 Référence CVE CVE-2026-68214 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-68190 Référence CVE CVE-2026-68192 https://www.cve.org/CVERecord?id=CVE-2026-68192 Référence CVE CVE-2026-68194 https://www.cve.org/CVERecord?id=CVE-2026-68194 Référence CVE CVE-2026-68195 https://www.cve.org/CVERecord?id=CVE-2026-68195 Référence CVE CVE-2026-68196 https://www.cve.org/CVERecord?id=CVE-2026-68196 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-68199 https://www.cve.org/CVERecord?id=CVE-2026-68199 Référence CVE CVE-2026-68202 https://www.cve.org/CVERecord?id=CVE-2026-68202 Référence CVE CVE-2026-68204 https://www.cve.org/CVERecord?id=CVE-2026-68204 Référence CVE CVE-2026-68206 https://www.cve.org/CVERecord?id=CVE-2026-68206 Référence CVE CVE-2026-68207 https://www.cve.org/CVERecord?id=CVE-2026-68207 Référence CVE CVE-2026-68209 https://www.cve.org/CVERecord?id=CVE-2026-68209 Référence CVE CVE-2026-68210 https://www.cve.org/CVERecord?id=CVE-2026-68210 Référence CVE CVE-2026-68212 https://www.cve.org/CVERecord?id=CVE-2026-68212 Référence CVE CVE-2026-68213 https://www.cve.org/CVERecord?id=CVE-2026-68213 Référence CVE CVE-2026-68214 https://www.cve.org/CVERecord?id=CVE-2026-68214 Référence CVE CVE-2026-68215 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-68189 Référence CVE CVE-2026-68192 https://www.cve.org/CVERecord?id=CVE-2026-68192 Référence CVE CVE-2026-68193 https://www.cve.org/CVERecord?id=CVE-2026-68193 Référence CVE CVE-2026-68194 https://www.cve.org/CVERecord?id=CVE-2026-68194 Référence CVE CVE-2026-68195 https://www.cve.org/CVERecord?id=CVE-2026-68195 Référence CVE CVE-2026-68196 https://www.cve.org/CVERecord?id=CVE-2026-68196 Référence CVE CVE-2026-68197 https://www.cve.org/CVERecord?id=CVE-2026-68197 Référence CVE CVE-2026-68199 https://www.cve.org/CVERecord?id=CVE-2026-68199 Référence CVE CVE-2026-68202 https://www.cve.org/CVERecord?id=CVE-2026-68202 Référence CVE CVE-2026-68204 https://www.cve.org/CVERecord?id=CVE-2026-68204 Référence CVE CVE-2026-68205 https://www.cve.org/CVERecord?id=CVE-2026-68205 Référence CVE CVE-2026-68206 https://www.cve.org/CVERecord?id=CVE-2026-68206 Référence CVE CVE-2026-68207 https://www.cve.org/CVERecord?id=CVE-2026-68207 Référence CVE CVE-2026-68209 https://www.cve.org/CVERecord?id=CVE-2026-68209 Référence CVE CVE-2026-68210 https://www.cve.org/CVERecord?id=CVE-2026-68210 Référence CVE CVE-2026-68212 https://www.cve.org/CVERecord?id=CVE-2026-68212 Référence CVE CVE-2026-68213 https://www.cve.org/CVERecord?id=CVE-2026-68213 Référence CVE CVE-2026-68214 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-68194 Référence CVE CVE-2026-68195 https://www.cve.org/CVERecord?id=CVE-2026-68195 Référence CVE CVE-2026-68196 https://www.cve.org/CVERecord?id=CVE-2026-68196 Référence CVE CVE-2026-68197 https://www.cve.org/CVERecord?id=CVE-2026-68197 Référence CVE CVE-2026-68199 https://www.cve.org/CVERecord?id=CVE-2026-68199 Référence CVE CVE-2026-68200 https://www.cve.org/CVERecord?id=CVE-2026-68200 Référence CVE CVE-2026-68201 https://www.cve.org/CVERecord?id=CVE-2026-68201 Référence CVE CVE-2026-68202 https://www.cve.org/CVERecord?id=CVE-2026-68202 Référence CVE CVE-2026-68203 https://www.cve.org/CVERecord?id=CVE-2026-68203 Référence CVE CVE-2026-68204 https://www.cve.org/CVERecord?id=CVE-2026-68204 Référence CVE CVE-2026-68205 https://www.cve.org/CVERecord?id=CVE-2026-68205 Référence CVE CVE-2026-68206 https://www.cve.org/CVERecord?id=CVE-2026-68206 Référence CVE CVE-2026-68207 https://www.cve.org/CVERecord?id=CVE-2026-68207 Référence CVE CVE-2026-68209 https://www.cve.org/CVERecord?id=CVE-2026-68209 Référence CVE CVE-2026-68210 https://www.cve.org/CVERecord?id=CVE-2026-68210 Référence CVE CVE-2026-68212 https://www.cve.org/CVERecord?id=CVE-2026-68212 Référence CVE CVE-2026-68213 https://www.cve.org/CVERecord?id=CVE-2026-68213 Référence CVE CVE-2026-68214 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.18, 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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 10 Aug 2026 · Last source change 19 Aug 2026, 16:31 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-55305
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
    rhcos as a component of Red Hat OpenShift Container Platform 4
    After
    openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/0a820f03727b509b887f3216a574062948761f34; removed remediation: git.kernel.org/a9cd0e8fb0b21faaa71199d9d3feb305c18ff576.
    Before
    remediation: git.kernel.org/a9cd0e8fb0b21faaa71199d9d3feb305c18ff576
    After
    remediation: git.kernel.org/0a820f03727b509b887f3216a574062948761f34
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    73c3f48230cda01402ae189b05d56f1f7e0d53c9 < a9cd0e8fb0b21faaa71199d9d3feb305c18ff576; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < abaec6747304581f8d4a9936352fa10e13325f07; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < daf2d92669b4a659d805d88d811161c70cd325ee; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < c2d1a2130c93f6d758af58590b86b2254c7a1dec; 3.18 · Fixed: < 3.18; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    73c3f48230cda01402ae189b05d56f1f7e0d53c9 < 0a820f03727b509b887f3216a574062948761f34; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < bbc96bc75de0fcd9bb6ac48798b206e3b09ec865; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < 6a5bc8aea111ccbca71ef2b9c868d5c81f2e89de; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < a9cd0e8fb0b21faaa71199d9d3feb305c18ff576; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < abaec6747304581f8d4a9936352fa10e13325f07; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < daf2d92669b4a659d805d88d811161c70cd325ee; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < c2d1a2130c93f6d758af58590b86b2254c7a1dec · Fixed: < 3.18; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    73c3f48230cda01402ae189b05d56f1f7e0d53c9 < a9cd0e8fb0b21faaa71199d9d3feb305c18ff576; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < abaec6747304581f8d4a9936352fa10e13325f07; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < daf2d92669b4a659d805d88d811161c70cd325ee; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < c2d1a2130c93f6d758af58590b86b2254c7a1dec; 3.18 · Fixed: < 3.18; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    73c3f48230cda01402ae189b05d56f1f7e0d53c9 < a9cd0e8fb0b21faaa71199d9d3feb305c18ff576; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < abaec6747304581f8d4a9936352fa10e13325f07; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < daf2d92669b4a659d805d88d811161c70cd325ee; 73c3f48230cda01402ae189b05d56f1f7e0d53c9 < c2d1a2130c93f6d758af58590b86b2254c7a1dec; 3.18 · Fixed: < 3.18; 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-55305↗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-68204 · cve.blacktree.nl