CVE-2026-53385In the Linux kernel, the following vulnerability has been resolved: vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write A KASAN null-ptr-deref was observed in vcs_notifier():…
Updated under an hour ago ()
Does this affect you?
It affects linux_kernel. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write A KASAN null-ptr-deref was observed in vcs_notifier(): BUG: KASAN: null-ptr-deref in vcs_notifier+0x98/0x130 Read of size 2 at addr qmp_cmd_name: qmp_capabilities, arguments: {} The issue is a race condition in vcs_write(). When the console_lock is temporarily dropped (to copy data from userspace), the vc_data pointer obtained from vcs_vc() may become stale. After re-acquiring the lock, vcs_vc() is called again to re-validate the pointer. If the vc has been deallocated in the meantime, vcs_vc() returns NULL, and the while loop breaks (with written > 0). However, after the loop, vcs_scr_updated(vc) is still called with the now-NULL vc pointer, leading to a null pointer dereference in the notifier chain (vcs_notifier dereferences param->vc). Fix this by adding a NULL check for vc before calling vcs_scr_updated().
- CVSS
- 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-476
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Aug 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
linux linux_kernel linux:linux_kernel | from 4.14.327 before 4.15; from 4.19.284 before 4.20; from 5.4.244 before 5.5; from 5.10.181 before 5.10.260; from 5.15.113 before 5.15.211; from 6.1.30 before 6.1.177; from 6.3.4 before 6.4; from 6.4.1 before 6.6.144; and 10 more ranges | NVD |
References
- https://git.kernel.org/stable/c/09a43e81279b8da15526da09877134b8bcf618b0patch
- https://git.kernel.org/stable/c/43a6281790273c1b0a9ab76609ff0245b968f1e6patch
- https://git.kernel.org/stable/c/73049768ad57145acd337102c5aa3c788e6642c8patch
- https://git.kernel.org/stable/c/74be188eb2dc1c99d63986167b9a67d415fe7326patch
- https://git.kernel.org/stable/c/7cc3dd79777f6ae4625ec37e84dd18a26dc88bdepatch
- https://git.kernel.org/stable/c/8232fca738011ca2ec865b46ec721d1796dc0580patch
- https://git.kernel.org/stable/c/a287620312dc6dcb9a093417a0e589bf30fcf38apatch
- https://git.kernel.org/stable/c/b6bbb85cf45bf0b070e741997fe0af3a772c5ad5patch
- https://git.kernel.org/stable/c/ff4806202749a51938236214adc0281481a57366patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.