Answer in brief
CVE-2023-53176 records a High severity (CVSS 7.8) vulnerability in serial: 8250: Reinit port->pm on port specific driver unbind. 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-2023-53176 records a High severity (CVSS 7.8) vulnerability in serial: 8250: Reinit port->pm on port specific driver unbind. 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.
CVSS is 7.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <490bf37eaabb0a857ed1ae8e75d8854e41662f1c || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <c9e080c3005fd183c56ff8f4d75edb5da0765d2c || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <d5cd2928d31042a7c0a01464f9a8d95be736421d || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <2c86a1305c1406f45ea780d06953c484ea1d9e6e || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <1ba5594739d858e524ff0f398ee1ebfe0a8b9d41 || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <af4d6dbb1a92ea424ad1ba1d0c88c7fa2345d872 || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <8e596aed5f2f98cf3e6e98d6fe1d689f4a319308 || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <04e82793f068d2f0ffe62fcea03d007a8cdc16a7 | 490bf37eaabb0a857ed1ae8e75d8854e41662f1c, c9e080c3005fd183c56ff8f4d75edb5da0765d2c, d5cd2928d31042a7c0a01464f9a8d95be736421d, 2c86a1305c1406f45ea780d06953c484ea1d9e6e, 1ba5594739d858e524ff0f398ee1ebfe0a8b9d41, af4d6dbb1a92ea424ad1ba1d0c88c7fa2345d872, 8e596aed5f2f98cf3e6e98d6fe1d689f4a319308, 04e82793f068d2f0ffe62fcea03d007a8cdc16a7 |
| Linux/Linuxgeneric | 2.6.37 | Not reported |
Published upstream
Sep 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: serial: 8250: Reinit port->pm on port specific driver unbind When we unbind a serial port hardware specific 8250 driver, the generic serial8250 driver takes over the port. After that we see an oops about 10 seconds later. This can produce the following at least on some TI SoCs: Unhandled fault: imprecise external abort (0x1406) Internal error: : 1406 [#1] SMP ARM Turns out that we may still have the serial port hardware specific driver port->pm in use, and serial8250_pm() tries to call it after the port specific driver is gone: serial8250_pm [8250_base] from uart_change_pm+0x54/0x8c [serial_base] uart_change_pm [serial_base] from uart_hangup+0x154/0x198 [serial_base] uart_hangup [serial_base] from __tty_hangup.part.0+0x328/0x37c __tty_hangup.part.0 from disassociate_ctty+0x154/0x20c disassociate_ctty from do_exit+0x744/0xaac do_exit from do_group_exit+0x40/0x8c do_group_exit from __wake_up_parent+0x0/0x1c Let's fix the issue by calling serial8250_set_defaults() in serial8250_unregister_port(). This will set the port back to using the serial8250 default functions, and sets the port->pm to point to serial8250_pm.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <490bf37eaabb0a857ed1ae8e75d8854e41662f1c || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <c9e080c3005fd183c56ff8f4d75edb5da0765d2c || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <d5cd2928d31042a7c0a01464f9a8d95be736421d || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <2c86a1305c1406f45ea780d06953c484ea1d9e6e || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <1ba5594739d858e524ff0f398ee1ebfe0a8b9d41 || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <af4d6dbb1a92ea424ad1ba1d0c88c7fa2345d872 || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <8e596aed5f2f98cf3e6e98d6fe1d689f4a319308 || >=c161afe9759ddcc174d08e7c4f683d08ac9ba86f <04e82793f068d2f0ffe62fcea03d007a8cdc16a7 | 490bf37eaabb0a857ed1ae8e75d8854e41662f1c, c9e080c3005fd183c56ff8f4d75edb5da0765d2c, d5cd2928d31042a7c0a01464f9a8d95be736421d, 2c86a1305c1406f45ea780d06953c484ea1d9e6e, 1ba5594739d858e524ff0f398ee1ebfe0a8b9d41, af4d6dbb1a92ea424ad1ba1d0c88c7fa2345d872, 8e596aed5f2f98cf3e6e98d6fe1d689f4a319308, 04e82793f068d2f0ffe62fcea03d007a8cdc16a7 |
| Linux/Linuxgeneric | 2.6.37 | Not reported |
Published upstream
Sep 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: serial: 8250: Reinit port->pm on port specific driver unbind When we unbind a serial port hardware specific 8250 driver, the generic serial8250 driver takes over the port. After that we see an oops about 10 seconds later. This can produce the following at least on some TI SoCs: Unhandled fault: imprecise external abort (0x1406) Internal error: : 1406 [#1] SMP ARM Turns out that we may still have the serial port hardware specific driver port->pm in use, and serial8250_pm() tries to call it after the port specific driver is gone: serial8250_pm [8250_base] from uart_change_pm+0x54/0x8c [serial_base] uart_change_pm [serial_base] from uart_hangup+0x154/0x198 [serial_base] uart_hangup [serial_base] from __tty_hangup.part.0+0x328/0x37c __tty_hangup.part.0 from disassociate_ctty+0x154/0x20c disassociate_ctty from do_exit+0x744/0xaac do_exit from do_group_exit+0x40/0x8c do_group_exit from __wake_up_parent+0x0/0x1c Let's fix the issue by calling serial8250_set_defaults() in serial8250_unregister_port(). This will set the port back to using the serial8250 default functions, and sets the port->pm to point to serial8250_pm.
Quoted source text, attributed separately from HOL analysis.