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

media: rtl2832: fix use-after-free in rtl2832_remove()

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 69 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.22% 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 69 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-68214 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-68214
304 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: fix use-after-free in rtl2832_remove() cancel_delayed_work_sync() is called before i2c_mux_del_adapters() in rtl2832_remove(). While the cancel waits for any running instance of i2c_gate_work to finish, it does not prevent the timer from being rescheduled by a concurrent thread. During probe, the r820t_attach() call attempts I2C transfers through the mux adapter. These transfers go through i2c_mux_master_xfer(), which calls rtl2832_deselect() after the transfer completes, rescheduling i2c_gate_work via schedule_delayed_work(). If this transfer is still in flight when rtl2832_remove() runs, rtl2832_deselect() can reschedule i2c_gate_work after it has been cancelled, causing a use-after-free when kfree(dev) is called. Fix this by calling i2c_mux_del_adapters() before cancel_delayed_work_sync(). Once the mux adapter is unregistered, no new I2C transfers can go through it, so rtl2832_deselect() can no longer reschedule i2c_gate_work. The subsequent cancel_delayed_work_sync() is then guaranteed to be final.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-68214 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: media: rtl2832: fix use-after-free in rtl2832_remove()
49 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 8
  • kernel as a component of Red Hat Enterprise Linux 8
  • kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8
  • kernel-core as a component of Red Hat Enterprise Linux 8
  • kernel-cross-headers as a component of Red Hat Enterprise Linux 8
  • kernel-debug as a component of Red Hat Enterprise Linux 8
  • kernel-debug-core as a component of Red Hat Enterprise Linux 8
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8
Summary
A flaw was found in the Linux kernel's `media: rtl2832` driver. A timing issue during the removal of the `rtl2832` device can lead to a use-after-free vulnerability. This occurs when the system attempts to access memory that has already been released, which can cause system instability or a denial of service (DoS). A local attacker could potentially exploit this flaw.
Remediation
To mitigate this issue, prevent the rtl2832 module from loading. See https://access.redhat.com/solutions/41278 for instructions.
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-55315

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: media: rtl2832: fix use-after-free in rtl2832_remove() cancel_delayed_work_sync() is called before i2c_mux_del_adapters() in rtl2832_remove(). While the cancel waits for any running instance of i2c_gate_work to finish, it does not prevent the timer from being rescheduled by a concurrent thread. During probe, the r820t_attach() call attempts I2C transfers through the mux adapter. These transfers go through i2c_mux_master_xfer(), which calls rtl2832_deselect() after the transfer completes, rescheduling i2c_gate_work via schedule_delayed_work(). If this transfer is still in flight when rtl2832_remove() runs, rtl2832_deselect() can reschedule i2c_gate_work after it has been cancelled, causing a use-after-free when kfree(dev) is called. Fix this by calling i2c_mux_del_adapters() before cancel_delayed_work_sync(). Once the mux adapter is unregistered, no new I2C transfers can go through it, so rtl2832_deselect() can no longer reschedule i2c_gate_work. The subsequent cancel_delayed_work_sync() is then guaranteed to be final.

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 69 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: fix use-after-free in rtl2832_remove() cancel_delayed_work_sync() is called before i2c_mux_del_adapters() in rtl2832_remove(). While the cancel waits for any running instance of i2c_gate_work to finish, it does not prevent the timer from being rescheduled by a concurrent thread. During probe, the r820t_attach() call attempts I2C transfers through the mux adapter. These transfers go through i2c_mux_master_xfer(), which calls rtl2832_deselect() after the transfer completes, rescheduling i2c_gate_work via schedule_delayed_work(). If this transfer is still in flight when rtl2832_remove() runs, rtl2832_deselect() can reschedule i2c_gate_work after it has been cancelled, causing a use-after-free when kfree(dev) is called. Fix this by calling i2c_mux_del_adapters() before cancel_delayed_work_sync(). Once the mux adapter is unregistered, no new I2C transfers can go through it, so rtl2832_deselect() can no longer reschedule i2c_gate_work. The subsequent cancel_delayed_work_sync() is then guaranteed to be final.

What

In the Linux kernel, the following vulnerability has been resolved: media: rtl2832: fix use-after-free in rtl2832_remove() cancel_delayed_work_sync() is called before i2c_mux_del_adapters() in rtl2832_remove(). While the cancel waits for any running instance of i2c_gate_work to finish, it does not prevent the timer from being rescheduled by a concurrent thread. During probe, the r820t_attach() call attempts I2C transfers through the mux adapter. These transfers go through i2c_mux_master_xfer(), which calls rtl2832_deselect() after the transfer completes, rescheduling i2c_gate_work via schedule_delayed_work(). If this transfer is still in flight when rtl2832_remove() runs, rtl2832_deselect() can reschedule i2c_gate_work after it has been cancelled, causing a use-after-free when kfree(dev) is called. Fix this by calling i2c_mux_del_adapters() before cancel_delayed_work_sync(). Once the mux adapter is unregistered, no new I2C transfers can go through it, so rtl2832_deselect() can no longer reschedule i2c_gate_work. The subsequent cancel_delayed_work_sync() is then guaranteed to be final.

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: media: rtl2832: fix use-after-free in rtl2832_remove() cancel_delayed_work_sync() is called before i2c_mux_del_adapters() in rtl2832_remove(). While the cancel waits for any running instance of i2c_gate_work to finish, it does not prevent the timer from being rescheduled by a concurrent thread. During probe, the r820t_attach() call attempts I2C transfers through the mux adapter. These transfers go through i2c_mux_master_xfer(), which calls rtl2832_deselect() after the transfer completes, rescheduling i2c_gate_work via schedule_delayed_work(). If this transfer is still in flight when rtl2832_remove() runs, rtl2832_deselect() can reschedule i2c_gate_work after it has been cancelled, causing a use-after-free when kfree(dev) is called. Fix this by calling i2c_mux_del_adapters() before cancel_delayed_work_sync(). Once the mux adapter is unregistered, no new I2C transfers can go through it, so rtl2832_deselect() can no longer reschedule i2c_gate_work. The subsequent cancel_delayed_work_sync() is then guaranteed to be final.

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

In the Linux kernel, the following vulnerability has been resolved: media: rtl2832: fix use-after-free in rtl2832_remove() cancel_delayed_work_sync() is called before i2c_mux_del_adapters() in rtl2832_remove(). While the cancel waits for any running instance of i2c_gate_work to finish, it does not prevent the timer from being rescheduled by a concurrent thread. During probe, the r820t_attach() call attempts I2C transfers through the mux adapter. These transfers go through i2c_mux_master_xfer(), which calls rtl2832_deselect() after the transfer completes, rescheduling i2c_gate_work via schedule_delayed_work(). If this transfer is still in flight when rtl2832_remove() runs, rtl2832_deselect() can reschedule i2c_gate_work after it has been cancelled, causing a use-after-free when kfree(dev) is called. Fix this by calling i2c_mux_del_adapters() before cancel_delayed_work_sync(). Once the mux adapter is unregistered, no new I2C transfers can go through it, so rtl2832_deselect() can no longer reschedule i2c_gate_work. The subsequent cancel_delayed_work_sync() is then guaranteed to be final.

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-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=CVE-2026-68221 Référence CVE CVE-2026-68222 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-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=CVE-2026-68222 Référence CVE CVE-2026-68223 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-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=CVE-2026-68226 Référence CVE CVE-2026-68227 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-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=CVE-2026-68222 Référence CVE CVE-2026-68223 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-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=CVE-2026-68221 Référence CVE CVE-2026-68222 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: < 4.7, 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 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-55315
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 from remediation: access.redhat.com/CVE-2026-68214 to remediation: access.redhat.com/CVE-2026-68214.
    Before
    remediation: access.redhat.com/CVE-2026-68214
    After
    remediation: access.redhat.com/CVE-2026-68214
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/1e8a6bc19403661661fed5ae82f6eca6c9cdfad2; removed remediation: git.kernel.org/9acd5bbbe1df8e487e49488692c224496d4c9e16.
    Before
    remediation: git.kernel.org/9acd5bbbe1df8e487e49488692c224496d4c9e16
    After
    remediation: git.kernel.org/1e8a6bc19403661661fed5ae82f6eca6c9cdfad2
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    cddcc40b1b1553010acb89add84c64b5d123ec94 < 9acd5bbbe1df8e487e49488692c224496d4c9e16; cddcc40b1b1553010acb89add84c64b5d123ec94 < 24bef237eef8dd1ebcffb129ba21891ddad0d309; cddcc40b1b1553010acb89add84c64b5d123ec94 < 2c71bda6edc630a1f8c3c45d8df5fc22d234e042; cddcc40b1b1553010acb89add84c64b5d123ec94 < 90d781711418881f8c836c2a859cc2886625d750; cddcc40b1b1553010acb89add84c64b5d123ec94 < 680daf40a82d483949f87f0d8f98639dc47e610c; 4.7 · Fixed: < 4.7; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    cddcc40b1b1553010acb89add84c64b5d123ec94 < 1e8a6bc19403661661fed5ae82f6eca6c9cdfad2; cddcc40b1b1553010acb89add84c64b5d123ec94 < 68a9c0290897c1436ddceb8cea604c93377a0299; cddcc40b1b1553010acb89add84c64b5d123ec94 < 13c06056699e66ff7109ba68658cc6ea4a23f516; cddcc40b1b1553010acb89add84c64b5d123ec94 < 9acd5bbbe1df8e487e49488692c224496d4c9e16; cddcc40b1b1553010acb89add84c64b5d123ec94 < 24bef237eef8dd1ebcffb129ba21891ddad0d309; cddcc40b1b1553010acb89add84c64b5d123ec94 < 2c71bda6edc630a1f8c3c45d8df5fc22d234e042; cddcc40b1b1553010acb89add84c64b5d123ec94 < 90d781711418881f8c836c2a859cc2886625d750; cddcc40b1b1553010acb89add84c64b5d123ec94 < 680daf40a82d483949f87f0d8f98639dc47e610c · Fixed: < 4.7; 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 ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    cddcc40b1b1553010acb89add84c64b5d123ec94 < 9acd5bbbe1df8e487e49488692c224496d4c9e16; cddcc40b1b1553010acb89add84c64b5d123ec94 < 24bef237eef8dd1ebcffb129ba21891ddad0d309; cddcc40b1b1553010acb89add84c64b5d123ec94 < 2c71bda6edc630a1f8c3c45d8df5fc22d234e042; cddcc40b1b1553010acb89add84c64b5d123ec94 < 90d781711418881f8c836c2a859cc2886625d750; cddcc40b1b1553010acb89add84c64b5d123ec94 < 680daf40a82d483949f87f0d8f98639dc47e610c; 4.7 · Fixed: < 4.7; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    cddcc40b1b1553010acb89add84c64b5d123ec94 < 9acd5bbbe1df8e487e49488692c224496d4c9e16; cddcc40b1b1553010acb89add84c64b5d123ec94 < 24bef237eef8dd1ebcffb129ba21891ddad0d309; cddcc40b1b1553010acb89add84c64b5d123ec94 < 2c71bda6edc630a1f8c3c45d8df5fc22d234e042; cddcc40b1b1553010acb89add84c64b5d123ec94 < 90d781711418881f8c836c2a859cc2886625d750; cddcc40b1b1553010acb89add84c64b5d123ec94 < 680daf40a82d483949f87f0d8f98639dc47e610c; 4.7 · Fixed: < 4.7; 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-55315↗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-68214 · cve.blacktree.nl