Live › vulnerability › CVE-2026-98754
Go to dashboardThe Linux kernel's vcc (Sun LDOM virtual console) driver clears a tty pointer without holding the port lock, so an LDC event callback can run concurrently and dereference a tty that was already freed. The sources describe this as a use-after-free, which can crash the kernel or be abused for code execution, but they do not state a severity or exploitability.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
The flaw is in the vcc virtual console driver, which is relevant to Linux guests running on Sun/Oracle LDOM-style virtualized SPARC systems that use LDC channels. Systems without this driver loaded are unlikely to be affected. The sources do not say which kernel versions are impacted.
No product ranges from the sources yet.
uname -r and compare it against the fixed kernel versions listed in the NVD entry (unknown from the sources)lsmod | grep vcc or grep -r vcc /proc/devices (unknown from the sources)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup
vcc_cleanup() sets port->tty to NULL without holding port->lock, racing with vcc_event() LDC callbacks that read port->tty under port->lock and then use tty->port. This can cause a use-after-free when the callback dereferences tty->port after cleanup has already destroyed and freed it.
This page as .md · .json · in your agent: get_signal("CVE-2026-98754")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.