Answer in brief
CVE-2026-53384 records a Unknown severity vulnerability in serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-53384 records a Unknown severity vulnerability in serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=57f83e5dd6a33c4696699954784f8fee789b1d0c <ccdf4510a3873b14e5e348cdb038717996f09fda || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <511d2b92f8d20de04acafab676150d26fb5c67f4 || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <07ffe414a708ae60551401cec5d727ed156b8caf || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <3d205fe80f2181f0109150ad1fa06ee5bc046935 || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <d72650a4f334581b23a1892b888a4cb1be142f76 || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <778b9dda4b24005a27bcd9c35c110bf8d7f259ca || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <10fc708b4de7f86002d2d735a2dbf3b5b7f65692 | ccdf4510a3873b14e5e348cdb038717996f09fda, 511d2b92f8d20de04acafab676150d26fb5c67f4, 07ffe414a708ae60551401cec5d727ed156b8caf, 3d205fe80f2181f0109150ad1fa06ee5bc046935, d72650a4f334581b23a1892b888a4cb1be142f76, 778b9dda4b24005a27bcd9c35c110bf8d7f259ca, 10fc708b4de7f86002d2d735a2dbf3b5b7f65692 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails dw8250_probe() registers the 8250 port via serial8250_register_8250_port() and then, if the device has a clock, registers a clock notifier. If clk_notifier_register() fails, probe returns the error but leaves the 8250 port registered. The matching serial8250_unregister_port() lives in dw8250_remove(), which is not called when probe fails, so the port slot stays occupied until the device is rebound or the system is rebooted. The devm-allocated driver data is freed while the port still references it (via the saved private_data and serial_in/serial_out callbacks), so any access to that port slot before a rebind is a use-after-free hazard. Unregister the port on the clk_notifier_register() error path.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=57f83e5dd6a33c4696699954784f8fee789b1d0c <ccdf4510a3873b14e5e348cdb038717996f09fda || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <511d2b92f8d20de04acafab676150d26fb5c67f4 || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <07ffe414a708ae60551401cec5d727ed156b8caf || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <3d205fe80f2181f0109150ad1fa06ee5bc046935 || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <d72650a4f334581b23a1892b888a4cb1be142f76 || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <778b9dda4b24005a27bcd9c35c110bf8d7f259ca || >=57f83e5dd6a33c4696699954784f8fee789b1d0c <10fc708b4de7f86002d2d735a2dbf3b5b7f65692 | ccdf4510a3873b14e5e348cdb038717996f09fda, 511d2b92f8d20de04acafab676150d26fb5c67f4, 07ffe414a708ae60551401cec5d727ed156b8caf, 3d205fe80f2181f0109150ad1fa06ee5bc046935, d72650a4f334581b23a1892b888a4cb1be142f76, 778b9dda4b24005a27bcd9c35c110bf8d7f259ca, 10fc708b4de7f86002d2d735a2dbf3b5b7f65692 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails dw8250_probe() registers the 8250 port via serial8250_register_8250_port() and then, if the device has a clock, registers a clock notifier. If clk_notifier_register() fails, probe returns the error but leaves the 8250 port registered. The matching serial8250_unregister_port() lives in dw8250_remove(), which is not called when probe fails, so the port slot stays occupied until the device is rebound or the system is rebooted. The devm-allocated driver data is freed while the port still references it (via the saved private_data and serial_in/serial_out callbacks), so any access to that port slot before a rebind is a use-after-free hazard. Unregister the port on the clk_notifier_register() error path.
Quoted source text, attributed separately from HOL analysis.