{"id":"CVE-2026-90336","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nserial: core: clear freed pointers on uart_register_driver() failure\n\nuart_register_driver() leaves drv->state pointing to freed memory when\ntty_alloc_driver() fails","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nserial: core: clear freed pointers on uart_register_driver() failure\n\nuart_register_driver() leaves drv->state pointing to freed memory when\ntty_alloc_driver() fails. I…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 06b376432974fe5f25f2843a8e8438c6a1cf3d50","Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 61a2fb25551be0375bc16ef2a70c987dfca26183","Linux 2.6.12"],"published":"2026-09-17","updated":"2026-09-17","sourceUpdated":"2026-09-17T17:17:32.180","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-90336","references":[{"url":"https://git.kernel.org/stable/c/06b376432974fe5f25f2843a8e8438c6a1cf3d50","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/61a2fb25551be0375bc16ef2a70c987dfca26183","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-17T16:21:47.818Z","epss":0.00189,"epssPercentile":0.08808,"slug":"CVE-2026-90336","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nserial: core: clear freed pointers on uart_register_driver() failure\n\nuart_register_driver() leaves drv->state pointing to freed memory when\ntty_alloc_driver() fails. If tty_register_driver() fails, drv->tty_driver\nalso retains a pointer after its reference is dropped.\n\nDrivers that use drv->state as an \"already registered\" flag can then skip\nregistration on the next probe and pass the freed state to\nuart_add_one_port().\n\nThis issue was found with failslab on QEMU's raspi1ap board by\nfailing registration and binding the PL011 port again.\n\nClear both pointers on their failure paths, as uart_unregister_driver()\nalready does.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}