CVE-2026-98754
Severity not reportedData quality: partial.
Some fields were not provided by the source.
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…
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.
CVSS
—
Awaiting analysis by NVD
Timeline (UTC)
Published: 2026-10-18 16:17
Modified: 2026-10-26 07:17
NVD status: Received
Last synced 1 day ago
Verified against the source API 2026-10-27 07:03 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
Not reported by the source (unknown — not "none").
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://git.kernel.org/stable/c/03b49c991abb8d021ca6fe51cd173447236b0552 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/1a9fb9eaeb69b1f6c00bed09289a33d9fe1e7ae4 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/57753441ef84bee3bf0e9ee1e3778d119c44aa32 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/821050631750e982007c0856c119346edba51cae 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/88f6ecb058801e9ce7b9aabc966530118d7cd53c 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Data sources
NVD CVE API 2.0 — fetched 2026-10-27 07:03 UTC · record ↗