Look up another CVE · open CVE-2026-53385 in the interactive tracker
CVE-2026-53385
vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write
Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem drivers/tty. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-53385 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 6.1.177-1 | Update the kernel and reboot. Fixed in 6.1.177-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.95-1 | Update the kernel and reboot. Fixed in 6.12.95-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.0.14-1 | Update the kernel and reboot. Fixed in 7.0.14-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.14-1 | Update the kernel and reboot. Fixed in 7.0.14-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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().
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/tty/vt/vc_screen.c
- What this is
- TTY LAYER AND SERIAL DRIVERSMAINTAINERS section matched on drivers/tty/ · linux-kernel@vger.kernel.org · Supported
Check it on the machine
grep -w CONFIG_VT /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian builds this code. Every release below compiles the affected file into the kernels it ships.
- bookworm, trixie, forky, sidy
- y
- built into the kernel image on every flavour - only a patch removes it
- Build switch
- CONFIG_VT
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-07-19 (3 months ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.13%, higher than 2.5% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/tty
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.10.181 | 5.10.260 | 43a628179027 |
| 5.15.113 | 5.15.211 | b6bbb85cf45b |
| 6.1.30 | 6.1.177 | ff4806202749 |
| 6.4 | 6.6.144 | 8232fca73801 |
| 6.4 | 6.12.95 | 73049768ad57 |
| 6.4 | 6.18.37 | 7cc3dd79777f |
| 6.4 | 7.0.14 | 74be188eb2dc |
| 6.4 | 7.1.2 | 09a43e81279b |
| 6.4 | 7.2 | a287620312dc |
| 4.14.327 | 0 | 0 |
| 4.19.284 | 0 | 0 |
| 5.4.244 | 0 | 0 |
| 6.3.4 | 0 | 0 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4717-1 | 2026-08-05 | bullseye 5.10.262-1 | tracker |
| DLA-4700-1 | 2026-07-26 | bullseye 6.1.177-1~deb11u1 | tracker |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-53385, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.