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

media: rtl2832_sdr: Return queued buffers on start_streaming() failure

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Distribution package intelligence

Release-specific package status

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

25 package states
Package result overrides the generic status

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

Repository candidate not checked

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

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

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2026-68213 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-68213
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: rtl2832_sdr: Return queued buffers on start_streaming() failure The vb2 framework hands buffers to the driver via buf_queue() before calling start_streaming(). If start_streaming() returns an error without first returning those buffers via vb2_buffer_done(), vb2_start_streaming() fires WARN_ON(owned_by_drv_count) and the queued buffers leak. rtl2832_sdr_start_streaming() had multiple error paths that hit this trap: two direct early returns (-ENODEV, -ERESTARTSYS), plus six `goto err` paths covering subdev s_power, tuner setup, ADC setup, stream-buffer allocation, urb allocation, and urb submission failures. None of them returned the queued buffers. The original function had no distinct success exit and fell straight through into the err label, which previously only did mutex_unlock and "return ret". Adding queued-buffer cleanup at err must therefore be paired with an explicit success return; otherwise every successful start would also drain the buffer queue and kill streaming. Add that success return, then add rtl2832_sdr_cleanup_queued_bufs() at the err label and before each early return. The cleanup helper takes a vb2_buffer_state argument so that the start_streaming error paths can pass VB2_BUF_STATE_QUEUED (as expected by userspace on start_streaming failure) while stop_streaming keeps its existing VB2_BUF_STATE_ERROR semantics. This mirrors the uvcvideo fix in commit 4cf3b6fd54eb ("media: uvcvideo: Return queued buffers on start_streaming() failure"). The err label still does not roll back power_ctrl(), frontend_ctrl(), the POWER_ON flag, or stream/URB allocations that may have happened before the failing step. Those are pre-existing leaks of a different class and are not addressed here.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-55314

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: media: rtl2832_sdr: Return queued buffers on start_streaming() failure The vb2 framework hands buffers to the driver via buf_queue() before calling start_streaming(). If start_streaming() returns an error without first returning those buffers via vb2_buffer_done(), vb2_start_streaming() fires WARN_ON(owned_by_drv_count) and the queued buffers leak. rtl2832_sdr_start_streaming() had multiple error paths that hit this trap: two direct early returns (-ENODEV, -ERESTARTSYS), plus six `goto err` paths covering subdev s_power, tuner setup, ADC setup, stream-buffer allocation, urb allocation, and urb submission failures. None of them returned the queued buffers. The original function had no distinct success exit and fell straight through into the err label, which previously only did mutex_unlock and "return ret". Adding queued-buffer cleanup at err must therefore be paired with an explicit success return; otherwise every successful start would also drain the buffer queue and kill streaming. Add that success return, then add rtl2832_sdr_cleanup_queued_bufs() at the err label and before each early return. The cleanup helper takes a vb2_buffer_state argument so that the start_streaming error paths can pass VB2_BUF_STATE_QUEUED (as expected by userspace on start_streaming failure) while stop_streaming keeps its existing VB2_BUF_STATE_ERROR semantics. This mirrors the uvcvideo fix in commit 4cf3b6fd54eb ("media: uvcvideo: Return queued buffers on start_streaming() failure"). The err label still does not roll back power_ctrl(), frontend_ctrl(), the POWER_ON flag, or stream/URB allocations that may have happened before the failing step. Those are pre-existing leaks of a different class and are not addressed here.

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: media: rtl2832_sdr: Return queued buffers on start_streaming() failure The vb2 framework hands buffers to the driver via buf_queue() before calling start_streaming(). If start_streaming() returns an error without first returning those buffers via vb2_buffer_done(), vb2_start_streaming() fires WARN_ON(owned_by_drv_count) and the queued buffers leak. rtl2832_sdr_start_streaming() had multiple error paths that hit this trap: two direct early returns (-ENODEV, -ERESTARTSYS), plus six `goto err` paths covering subdev s_power, tuner setup, ADC setup, stream-buffer allocation, urb allocation, and urb submission failures. None of them returned the queued buffers. The original function had no distinct success exit and fell straight through into the err label, which previously only did mutex_unlock and "return ret". Adding queued-buffer cleanup at err must therefore be paired with an explicit success return; otherwise every successful start would also drain the buffer queue and kill streaming. Add that success return, then add rtl2832_sdr_cleanup_queued_bufs() at the err label and before each early return. The cleanup helper takes a vb2_buffer_state argument so that the start_streaming error paths can pass VB2_BUF_STATE_QUEUED (as expected by userspace on start_streaming failure) while stop_streaming keeps its existing VB2_BUF_STATE_ERROR semantics. This mirrors the uvcvideo fix in commit 4cf3b6fd54eb ("media: uvcvideo: Return queued buffers on start_streaming() failure"). The err label still does not roll back power_ctrl(), frontend_ctrl(), the POWER_ON flag, or stream/URB allocations that may have happened before the failing step. Those are pre-existing leaks of a different class and are not addressed here.

What

In the Linux kernel, the following vulnerability has been resolved: media: rtl2832_sdr: Return queued buffers on start_streaming() failure The vb2 framework hands buffers to the driver via buf_queue() before calling start_streaming(). If start_streaming() returns an error without first returning those buffers via vb2_buffer_done(), vb2_start_streaming() fires WARN_ON(owned_by_drv_count) and the queued buffers leak. rtl2832_sdr_start_streaming() had multiple error paths that hit this trap: two direct early returns (-ENODEV, -ERESTARTSYS), plus six `goto err` paths covering subdev s_power, tuner setup, ADC setup, stream-buffer allocation, urb allocation, and urb submission failures. None of them returned the queued buffers. The original function had no distinct success exit and fell straight through into the err label, which previously only did mutex_unlock and "return ret". Adding queued-buffer cleanup at err must therefore be paired with an explicit success return; otherwise every successful start would also drain the buffer queue and kill streaming. Add that success return, then add rtl2832_sdr_cleanup_queued_bufs() at the err label and before each early return. The cleanup helper takes a vb2_buffer_state argument so that the start_streaming error paths can pass VB2_BUF_STATE_QUEUED (as expected by userspace on start_streaming failure) while stop_streaming keeps its existing VB2_BUF_STATE_ERROR semantics. This mirrors the uvcvideo fix in commit 4cf3b6fd54eb ("media: uvcvideo: Return queued buffers on start_streaming() failure"). The err label still does not roll back power_ctrl(), frontend_ctrl(), the POWER_ON flag, or stream/URB allocations that may have happened before the failing step. Those are pre-existing leaks of a different class and are not addressed here.

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: rtl2832_sdr: Return queued buffers on start_streaming() failure The vb2 framework hands buffers to the driver via buf_queue() before calling start_streaming(). If start_streaming() returns an error without first returning those buffers via vb2_buffer_done(), vb2_start_streaming() fires WARN_ON(owned_by_drv_count) and the queued buffers leak. rtl2832_sdr_start_streaming() had multiple error paths that hit this trap: two direct early returns (-ENODEV, -ERESTARTSYS), plus six `goto err` paths covering subdev s_power, tuner setup, ADC setup, stream-buffer allocation, urb allocation, and urb submission failures. None of them returned the queued buffers. The original function had no distinct success exit and fell straight through into the err label, which previously only did mutex_unlock and "return ret". Adding queued-buffer cleanup at err must therefore be paired with an explicit success return; otherwise every successful start would also drain the buffer queue and kill streaming. Add that success return, then add rtl2832_sdr_cleanup_queued_bufs() at the err label and before each early return. The cleanup helper takes a vb2_buffer_state argument so that the start_streaming error paths can pass VB2_BUF_STATE_QUEUED (as expected by userspace on start_streaming failure) while stop_streaming keeps its existing VB2_BUF_STATE_ERROR semantics. This mirrors the uvcvideo fix in commit 4cf3b6fd54eb ("media: uvcvideo: Return queued buffers on start_streaming() failure"). The err label still does not roll back power_ctrl(), frontend_ctrl(), the POWER_ON flag, or stream/URB allocations that may have happened before the failing step. Those are pre-existing leaks of a different class and are not addressed here.

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

In the Linux kernel, the following vulnerability has been resolved: media: rtl2832_sdr: Return queued buffers on start_streaming() failure The vb2 framework hands buffers to the driver via buf_queue() before calling start_streaming(). If start_streaming() returns an error without first returning those buffers via vb2_buffer_done(), vb2_start_streaming() fires WARN_ON(owned_by_drv_count) and the queued buffers leak. rtl2832_sdr_start_streaming() had multiple error paths that hit this trap: two direct early returns (-ENODEV, -ERESTARTSYS), plus six `goto err` paths covering subdev s_power, tuner setup, ADC setup, stream-buffer allocation, urb allocation, and urb submission failures. None of them returned the queued buffers. The original function had no distinct success exit and fell straight through into the err label, which previously only did mutex_unlock and "return ret". Adding queued-buffer cleanup at err must therefore be paired with an explicit success return; otherwise every successful start would also drain the buffer queue and kill streaming. Add that success return, then add rtl2832_sdr_cleanup_queued_bufs() at the err label and before each early return. The cleanup helper takes a vb2_buffer_state argument so that the start_streaming error paths can pass VB2_BUF_STATE_QUEUED (as expected by userspace on start_streaming failure) while stop_streaming keeps its existing VB2_BUF_STATE_ERROR semantics. This mirrors the uvcvideo fix in commit 4cf3b6fd54eb ("media: uvcvideo: Return queued buffers on start_streaming() failure"). The err label still does not roll back power_ctrl(), frontend_ctrl(), the POWER_ON flag, or stream/URB allocations that may have happened before the failing step. Those are pre-existing leaks of a different class and are not addressed here.

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-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=CVE-2026-68214 Référence CVE CVE-2026-68215 https://www.cve.org/CVERecord?id=CVE-2026-68215 Référence CVE CVE-2026-68216 https://www.cve.org/CVERecord?id=CVE-2026-68216 Référence CVE CVE-2026-68217 https://www.cve.org/CVERecord?id=CVE-2026-68217 Référence CVE CVE-2026-68218 https://www.cve.org/CVERecord?id=CVE-2026-68218 Référence CVE CVE-2026-68219 https://www.cve.org/CVERecord?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-68221 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-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=CVE-2026-68214 Référence CVE CVE-2026-68215 https://www.cve.org/CVERecord?id=CVE-2026-68215 Référence CVE CVE-2026-68216 https://www.cve.org/CVERecord?id=CVE-2026-68216 Référence CVE CVE-2026-68217 https://www.cve.org/CVERecord?id=CVE-2026-68217 Référence CVE CVE-2026-68218 https://www.cve.org/CVERecord?id=CVE-2026-68218 Référence CVE CVE-2026-68219 https://www.cve.org/CVERecord?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=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-68158 Référence CVE CVE-2026-68159 https://www.cve.org/CVERecord?id=CVE-2026-68159 Référence CVE CVE-2026-68160 https://www.cve.org/CVERecord?id=CVE-2026-68160 Référence CVE CVE-2026-68161 https://www.cve.org/CVERecord?id=CVE-2026-68161 Référence CVE CVE-2026-68162 https://www.cve.org/CVERecord?id=CVE-2026-68162 Référence CVE CVE-2026-68198 https://www.cve.org/CVERecord?id=CVE-2026-68198 Référence CVE CVE-2026-68206 https://www.cve.org/CVERecord?id=CVE-2026-68206 Référence CVE CVE-2026-68209 https://www.cve.org/CVERecord?id=CVE-2026-68209 Référence CVE CVE-2026-68210 https://www.cve.org/CVERecord?id=CVE-2026-68210 Référence CVE CVE-2026-68213 https://www.cve.org/CVERecord?id=CVE-2026-68213 Référence CVE CVE-2026-68228 https://www.cve.org/CVERecord?id=CVE-2026-68228 Référence CVE CVE-2026-68229 https://www.cve.org/CVERecord?id=CVE-2026-68229 Référence CVE CVE-2026-68300 https://www.cve.org/CVERecord?id=CVE-2026-68300 Référence CVE CVE-2026-68302 https://www.cve.org/CVERecord?id=CVE-2026-68302 Référence CVE CVE-2026-68343 https://www.cve.org/CVERecord?id=CVE-2026-68343 Référence CVE CVE-2026-68381 https://www.cve.org/CVERecord?id=CVE-2026-68381 Référence CVE CVE-2026-68388 https://www.cve.org/CVERecord?id=CVE-2026-68388 Référence CVE CVE-2026-68426 https://www.cve.org/CVERecord?id=

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

d?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=CVE-2026-68215 Référence CVE CVE-2026-68216 https://www.cve.org/CVERecord?id=CVE-2026-68216 Référence CVE CVE-2026-68217 https://www.cve.org/CVERecord?id=CVE-2026-68217 Référence CVE CVE-2026-68218 https://www.cve.org/CVERecord?id=CVE-2026-68218 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=

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

d?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=CVE-2026-68214 Référence CVE CVE-2026-68215 https://www.cve.org/CVERecord?id=CVE-2026-68215 Référence CVE CVE-2026-68216 https://www.cve.org/CVERecord?id=CVE-2026-68216 Référence CVE CVE-2026-68217 https://www.cve.org/CVERecord?id=CVE-2026-68217 Référence CVE CVE-2026-68218 https://www.cve.org/CVERecord?id=CVE-2026-68218 Référence CVE CVE-2026-68219 https://www.cve.org/CVERecord?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=

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

d?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=CVE-2026-68214 Référence CVE CVE-2026-68215 https://www.cve.org/CVERecord?id=CVE-2026-68215 Référence CVE CVE-2026-68216 https://www.cve.org/CVERecord?id=CVE-2026-68216 Référence CVE CVE-2026-68217 https://www.cve.org/CVERecord?id=CVE-2026-68217 Référence CVE CVE-2026-68218 https://www.cve.org/CVERecord?id=CVE-2026-68218 Référence CVE CVE-2026-68219 https://www.cve.org/CVERecord?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-68221 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.15, 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-55314
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. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/fd1e11fc3849169285e48b2d4ec441614ad2ea74; removed remediation: git.kernel.org/465dc8e71d2db2ed603e749fa71392bcdccf07eb.
    Before
    remediation: git.kernel.org/465dc8e71d2db2ed603e749fa71392bcdccf07eb
    After
    remediation: git.kernel.org/fd1e11fc3849169285e48b2d4ec441614ad2ea74
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    771138920eafa399f68d3492c8a75dfeea23474b < 465dc8e71d2db2ed603e749fa71392bcdccf07eb; 771138920eafa399f68d3492c8a75dfeea23474b < 0b08c0403cf672a121ace4eff647a9b240bd4e1b; 771138920eafa399f68d3492c8a75dfeea23474b < 894e83509c66910112b9eaeaa8cd66cd9806db91; 771138920eafa399f68d3492c8a75dfeea23474b < fc0b18782aab4e35078efe72863df8eab46560a8; 771138920eafa399f68d3492c8a75dfeea23474b < 33ca0aab6f4bd90921fc1395478f38f72c4d19af; 3.15 · Fixed: < 3.15; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    771138920eafa399f68d3492c8a75dfeea23474b < fd1e11fc3849169285e48b2d4ec441614ad2ea74; 771138920eafa399f68d3492c8a75dfeea23474b < 772f2550fe32357557d3b2f88e02f7cf477f0789; 771138920eafa399f68d3492c8a75dfeea23474b < a248273f8af6e630a03e823274385725974009b5; 771138920eafa399f68d3492c8a75dfeea23474b < 465dc8e71d2db2ed603e749fa71392bcdccf07eb; 771138920eafa399f68d3492c8a75dfeea23474b < 0b08c0403cf672a121ace4eff647a9b240bd4e1b; 771138920eafa399f68d3492c8a75dfeea23474b < 894e83509c66910112b9eaeaa8cd66cd9806db91; 771138920eafa399f68d3492c8a75dfeea23474b < fc0b18782aab4e35078efe72863df8eab46560a8; 771138920eafa399f68d3492c8a75dfeea23474b < 33ca0aab6f4bd90921fc1395478f38f72c4d19af · Fixed: < 3.15; 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 ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    771138920eafa399f68d3492c8a75dfeea23474b < 465dc8e71d2db2ed603e749fa71392bcdccf07eb; 771138920eafa399f68d3492c8a75dfeea23474b < 0b08c0403cf672a121ace4eff647a9b240bd4e1b; 771138920eafa399f68d3492c8a75dfeea23474b < 894e83509c66910112b9eaeaa8cd66cd9806db91; 771138920eafa399f68d3492c8a75dfeea23474b < fc0b18782aab4e35078efe72863df8eab46560a8; 771138920eafa399f68d3492c8a75dfeea23474b < 33ca0aab6f4bd90921fc1395478f38f72c4d19af; 3.15 · Fixed: < 3.15; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    771138920eafa399f68d3492c8a75dfeea23474b < 465dc8e71d2db2ed603e749fa71392bcdccf07eb; 771138920eafa399f68d3492c8a75dfeea23474b < 0b08c0403cf672a121ace4eff647a9b240bd4e1b; 771138920eafa399f68d3492c8a75dfeea23474b < 894e83509c66910112b9eaeaa8cd66cd9806db91; 771138920eafa399f68d3492c8a75dfeea23474b < fc0b18782aab4e35078efe72863df8eab46560a8; 771138920eafa399f68d3492c8a75dfeea23474b < 33ca0aab6f4bd90921fc1395478f38f72c4d19af; 3.15 · Fixed: < 3.15; 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-55314↗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-68213 · cve.blacktree.nl