CVE-2026-53347: Linux kernel · drm/virtio: Fix driver removal with disabled KMS
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Until a fix is applied, avoid removing or unbinding the virtio-gpu driver when KMS is disabled to prevent kernel crashes.
Description
A vulnerability in the Linux kernel's drm/virtio driver occurs when KMS (Kernel Mode Setting) is disabled. The issue involves uninitialized DRM atomic and modesetting components, which leads to accessing uninitialized data during driver removal or unbinding, causing a kernel crash. The flaw is fixed by skipping the shutdown of the atomic core when KMS is unavailable.
References
- nvd.nist.gov/vuln/detail/CVE-2026-53347 (opens in a new tab)
- git.kernel.org/stable/c/15e561869a8b4e4db69733be1d6f33770664f989 (opens in a new tab)
- git.kernel.org/stable/c/19a6a00ff50c284f3a9818882ad2be58b33b790a (opens in a new tab)
- git.kernel.org/stable/c/38a5f891cda6d121c149c94cda89c31ec7024ee3 (opens in a new tab)
- git.kernel.org/stable/c/ed3e134700a2e07caa99b9bc0683ebbe0327c562 (opens in a new tab)
- git.kernel.org/stable/c/f329e8325e054bd6d84d10904f8dd51137281b92 (opens in a new tab)