CVE-2026-53347
drm/virtio: Fix driver removal with disabled KMS
Description
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.
INFO
Published Date :
July 1, 2026, 2:16 p.m.
Last Modified :
July 22, 2026, 7:15 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update the Linux kernel to the latest stable version.
- Ensure KMS is properly configured or handled.
- Test driver removal after applying updates.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-53347.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-53347 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-53347
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-53347 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-53347 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jul. 22, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE CWE-908 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.36 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.94 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.13 *cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc7:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.4 up to (excluding) 6.6.143 Added Reference Type kernel.org: https://git.kernel.org/stable/c/15e561869a8b4e4db69733be1d6f33770664f989 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/19a6a00ff50c284f3a9818882ad2be58b33b790a Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/38a5f891cda6d121c149c94cda89c31ec7024ee3 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/ed3e134700a2e07caa99b9bc0683ebbe0327c562 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/f329e8325e054bd6d84d10904f8dd51137281b92 Types: Patch -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 01, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '72122c69d71784e390527819754ea456421c4501', 'lessThan': 'ed3e134700a2e07caa99b9bc0683ebbe0327c562', 'versionType': 'git'}, {'status': 'affected', 'version': '72122c69d71784e390527819754ea456421c4501', 'lessThan': '38a5f891cda6d121c149c94cda89c31ec7024ee3', 'versionType': 'git'}, {'status': 'affected', 'version': '72122c69d71784e390527819754ea456421c4501', 'lessThan': '19a6a00ff50c284f3a9818882ad2be58b33b790a', 'versionType': 'git'}, {'status': 'affected', 'version': '72122c69d71784e390527819754ea456421c4501', 'lessThan': '15e561869a8b4e4db69733be1d6f33770664f989', 'versionType': 'git'}, {'status': 'affected', 'version': '72122c69d71784e390527819754ea456421c4501', 'lessThan': 'f329e8325e054bd6d84d10904f8dd51137281b92', 'versionType': 'git'}], 'programFiles': ['drivers/gpu/drm/virtio/virtgpu_drv.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.4'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.4', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.143', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.94', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.36', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.13', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/gpu/drm/virtio/virtgpu_drv.c'], 'defaultStatus': 'affected'}] Added Description 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. Added Reference https://git.kernel.org/stable/c/15e561869a8b4e4db69733be1d6f33770664f989 Added Reference https://git.kernel.org/stable/c/19a6a00ff50c284f3a9818882ad2be58b33b790a Added Reference https://git.kernel.org/stable/c/38a5f891cda6d121c149c94cda89c31ec7024ee3 Added Reference https://git.kernel.org/stable/c/ed3e134700a2e07caa99b9bc0683ebbe0327c562 Added Reference https://git.kernel.org/stable/c/f329e8325e054bd6d84d10904f8dd51137281b92