CVE-2026-53384
Linux 8250_dw serial driver can leave port referencing freed data, causing kernel use-after-free.
Is CVE-2026-53384 being exploited?
Not confirmed. CVE-2026-53384 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.52% probability of exploitation in the next 30 days.
How severe is CVE-2026-53384?
CVE-2026-53384 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53384?
Yes. A fix has been recorded for CVE-2026-53384. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53384 affect?
CVE-2026-53384 affects Linux kernel (8250_dw / serial8250 driver), Embedded devices with 8250 UARTs, Servers/workstations running affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53384?
Install vendor kernel updates and reboot affected systems.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local use-after-free via serial port registration error can trigger kernel crash or local privilege escalation (potential RCE via device interaction).
Patch immediately and reboot affected systems
- affected>= 57f83e5dd6a33c4696699954784f8fee789b1d0c and < ccdf4510a3873b14e5e348cdb038717996f09fda
- affected>= 57f83e5dd6a33c4696699954784f8fee789b1d0c and < 511d2b92f8d20de04acafab676150d26fb5c67f4
- affected>= 57f83e5dd6a33c4696699954784f8fee789b1d0c and < 07ffe414a708ae60551401cec5d727ed156b8caf
- affected>= 57f83e5dd6a33c4696699954784f8fee789b1d0c and < 3d205fe80f2181f0109150ad1fa06ee5bc046935
- affected>= 57f83e5dd6a33c4696699954784f8fee789b1d0c and < d72650a4f334581b23a1892b888a4cb1be142f76
- affected>= 57f83e5dd6a33c4696699954784f8fee789b1d0c and < 778b9dda4b24005a27bcd9c35c110bf8d7f259ca
- affected>= 57f83e5dd6a33c4696699954784f8fee789b1d0c and < 10fc708b4de7f86002d2d735a2dbf3b5b7f65692
- affected5.19
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.