dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53347

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 6.6.143 / 6.12.94 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: drm/virtio: Fix driver removal with disabled KMS DRM atomic and modesetting aren't initialized if virtio-gpu driver built with disabled KMS, leading to access of uninitialized data on driver removal/unbinding and crashing kernel. Fix it by skipping shutting down atomic core with unavailable KMS.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The virtio-gpu DRM driver fails to initialize DRM atomic and modesetting subsystems when built with KMS (Kernel Mode Setting) disabled, but the driver removal code still attempts to shut down these uninitialized components, causing kernel crashes from accessing uninitialized data.

MitigationUpdate to a Linux kernel version containing the fix that adds a conditional check to skip atomic core shutdown when KMS is unavailable; alternatively, ensure KMS is enabled when using virtio-gpu.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.4, < 6.6.143>= 6.7, < 6.12.94>= 6.13, < 6.18.36>= 6.19, < 7.0.13= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version
    Run `uname -r` or read `/proc/version` to obtain the running kernel version
    Affected if The version falls within any of these ranges: >= 6.4 to < 6.6.143, >= 6.7 to < 6.12.94, >= 6.13 to < 6.18.36, >= 6.19 to < 7.0.13, or equals 7.1
  2. Verify virtio-gpu driver is present
    Check if the virtio-gpu module exists with `lsmod | grep virtio` or check for presence under `/sys/module/virtio_gpu`
    Affected if The virtio-gpu driver is loaded or built into the kernel
  3. Determine if KMS is enabled in kernel config
    Examine the kernel configuration file (typically `/boot/config-$(uname -r)` or decompress `/proc/config.gz` if available); look for CONFIG_DRM_VIRTIO_GPU and related KMS settings such as CONFIG_DRM_KMS_HELPER
    Affected if KMS support (CONFIG_DRM_KMS_HELPER or similar modesetting infrastructure) is disabled while virtio-gpu is present

You are affected if you are running an affected kernel version, have the virtio-gpu driver loaded, and KMS is disabled in your kernel configuration, creating the risk of a kernel crash upon driver removal.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.6.143 / 6.12.94 / 6.18.36 or later
Fixed in 6.6.1436.12.946.18.36
Interim mitigation

Update to a Linux kernel version containing the fix that adds a conditional check to skip atomic core shutdown when KMS is unavailable; alternatively, ensure KMS is enabled when using virtio-gpu.

Recommended fix High confidence

Linux kernel >= 6.6.143, >= 6.12.94, >= 6.18.36, or >= 7.0.13 (depending on your branch)

  1. Identify the currently running kernel version using 'uname -r' or 'cat /proc/version'
  2. Check which version branch your current kernel belongs to (6.4-6.6.x, 6.7-6.12.x, 6.13-6.18.x, or 6.19-7.0.x)
  3. Upgrade the Linux kernel to a version equal to or higher than the fixed version for your branch: 6.6.143, 6.12.94, 6.18.36, or 7.0.13 respectively
  4. Reboot the system to load the new kernel
  5. Verify the fix is applied by checking the kernel version with 'uname -r'
Caveat Kernel upgrades may require rebuilding third-party kernel modules; ensure compatible drivers are available for your specific kernel version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53347 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53347 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data