CVE-2026-74653

Full vulnerability record from the local CVENow database.

Description

In the Linux kernel, the following vulnerability has been resolved: serial: 8250_of: clear stuck empty-FIFO RX-timeout on LPC32xx The NXP LPC32xx UART (PORT_LPC3220) can latch an RX character-timeout interrupt while the RX FIFO is empty: IIR reports UART_IIR_RX_TIMEOUT (0x0c) but LSR.DR is clear. A character timeout is only cleared by reading RHR, but serial8250_rx_chars() reads RHR only when LSR.DR is set, so nothing ever clears the condition. The interrupt is level-triggered and re-fires immediately, so on a single-core ARM926 the resulting interrupt storm livelocks the CPU. It is reproducible when userspace repeatedly opens the front-panel port (ttyS1): serial8250_do_set_termios() re-enables interrupts on unlock and the handler then spins forever with iir=0xcc lsr=0x60 ier=0x05, tripping the soft-lockup detector in serial8250_handle_irq_locked(). LPC32xx has no dedicated 8250 glue driver, it's driven by the generic 8250_of. Add a hardware specific handle_irq for PORT_LPC3220, wired up in of_platform_serial_setup() the same way fsl8250_handle_irq is installed. The handler follows dw8250_handle_irq(): on an RX timeout with an empty FIFO (LSR.DR and LSR.BI clear) it does one throwaway RHR read to clear the condition, then calls serial8250_handle_irq_locked(). No real received data is ever discarded, and it is a no-op on healthy UARTs which never report a timeout with DR clear. This is the same class of bug already worked around in other 8250 drivers; see commit 424d79183af0 ("serial: 8250_dw: Avoid "too much work" from bogus rx timeout interrupt") which reports the identical iir=0xcc/lsr=0x60. See also UART_RX_TIMEOUT_QUIRK in 8250_omap, and the note in 8250_bcm7271.

Severity

Not scored

CVSS score

Not available

Vulnerability status

Received

Source identifier

416baaa9-dc9f-4396-8d5f-8c081fb06d67

Published

2026-08-22 16:16:38.827000

Last modified

2026-10-21 13:19:48.270000

View original CVE JSON

{
  "id": "CVE-2026-74653",
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "published": "2026-08-22T16:16:38.827",
  "lastModified": "2026-10-21T13:19:48.270",
  "vulnStatus": "Received",
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nserial: 8250_of: clear stuck empty-FIFO RX-timeout on LPC32xx\n\nThe NXP LPC32xx UART (PORT_LPC3220) can latch an RX character-timeout\ninterrupt while the RX FIFO is empty: IIR reports UART_IIR_RX_TIMEOUT\n(0x0c) but LSR.DR is clear. A character timeout is only cleared by\nreading RHR, but serial8250_rx_chars() reads RHR only when LSR.DR is\nset, so nothing ever clears the condition. The interrupt is\nlevel-triggered and re-fires immediately, so on a single-core ARM926\nthe resulting interrupt storm livelocks the CPU.\n\nIt is reproducible when userspace repeatedly opens the front-panel port\n(ttyS1): serial8250_do_set_termios() re-enables interrupts on unlock and\nthe handler then spins forever with iir=0xcc lsr=0x60 ier=0x05, tripping\nthe soft-lockup detector in serial8250_handle_irq_locked().\n\nLPC32xx has no dedicated 8250 glue driver, it's driven by the generic\n8250_of. Add a hardware specific handle_irq for PORT_LPC3220, wired up\nin of_platform_serial_setup() the same way fsl8250_handle_irq is\ninstalled. The handler follows dw8250_handle_irq(): on an RX timeout\nwith an empty FIFO (LSR.DR and LSR.BI clear) it does one throwaway RHR\nread to clear the condition, then calls serial8250_handle_irq_locked().\nNo real received data is ever discarded, and it is a no-op on healthy\nUARTs which never report a timeout with DR clear.\n\nThis is the same class of bug already worked around in other 8250 drivers;\nsee commit 424d79183af0 (\"serial: 8250_dw: Avoid \"too much work\" from bogus rx timeout interrupt\")\nwhich reports the identical iir=0xcc/lsr=0x60. See also\nUART_RX_TIMEOUT_QUIRK in 8250_omap, and the note in 8250_bcm7271."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nserial: 8250_of: limpiar el tiempo de espera de RX atascado de FIFO vacío en LPC32xx\n\nLa UART NXP LPC32xx (PORT_LPC3220) puede enganchar una interrupción de tiempo de espera de carácter RX mientras la FIFO de RX está vacía: IIR informa UART_IIR_RX_TIMEOUT (0x0c) pero LSR.DR está despejado. Un tiempo de espera de carácter solo se borra leyendo RHR, pero serial8250_rx_chars() lee RHR solo cuando LSR.DR está establecido, por lo que nada borra nunca la condición. La interrupción es activada por nivel y se vuelve a disparar inmediatamente, por lo que en un ARM926 de un solo núcleo la tormenta de interrupciones resultante bloquea la CPU.\n\nEs reproducible cuando el espacio de usuario abre repetidamente el puerto del panel frontal (ttyS1): serial8250_do_set_termios() vuelve a habilitar las interrupciones al desbloquear y el gestor luego gira indefinidamente con iir=0xcc lsr=0x60 ier=0x05, activando el detector de bloqueo suave en serial8250_handle_irq_locked().\n\nLPC32xx no tiene un controlador de pegamento 8250 dedicado, es impulsado por el genérico 8250_of. Añadir un handle_irq específico del hardware para PORT_LPC3220, cableado en of_platform_serial_setup() de la misma manera que se instala fsl8250_handle_irq. El gestor sigue a dw8250_handle_irq(): en un tiempo de espera de RX con una FIFO vacía (LSR.DR y LSR.BI despejados) realiza una lectura de RHR de descarte para borrar la condición, luego llama a serial8250_handle_irq_locked(). Nunca se descartan datos reales recibidos, y es una operación nula en UARTs saludables que nunca informan un tiempo de espera con DR despejado.\n\nEsta es la misma clase de error ya solucionado en otros controladores 8250; ver commit 424d79183af0 ('serial: 8250_dw: Evitar 'demasiado trabajo' de interrupción de tiempo de espera de rx falsa') que informa el idéntico iir=0xcc/lsr=0x60. Ver también UART_RX_TIMEOUT_QUIRK en 8250_omap, y la nota en 8250_bcm7271."
    }
  ],
  "affected": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "affectedData": [
        {
          "vendor": "Linux",
          "product": "Linux",
          "defaultStatus": "unaffected",
          "programFiles": [
            "drivers/tty/serial/8250/8250_of.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "versions": [
            {
              "version": "e6e912c4964ce5976e508881207dfa96d5f856d7",
              "lessThan": "cc325ce1c40a111824827532ac132afb3d1c342b",
              "versionType": "git",
              "status": "affected"
            },
            {
              "version": "e6e912c4964ce5976e508881207dfa96d5f856d7",
              "lessThan": "c321dc5172c8c66e21ffbeeb7a2ebb88ae6fd4c3",
              "versionType": "git",
              "status": "affected"
            },
            {
              "version": "e6e912c4964ce5976e508881207dfa96d5f856d7",
              "lessThan": "3ce24bc4d115336218e59b7e286fd3a79f4fc4c6",
              "versionType": "git",
              "status": "affected"
            },
            {
              "version": "e6e912c4964ce5976e508881207dfa96d5f856d7",
              "lessThan": "7795e8abedc86438cae0454602cbf9038b94bf38",
              "versionType": "git",
              "status": "affected"
            },
            {
              "version": "e6e912c4964ce5976e508881207dfa96d5f856d7",
              "lessThan": "1423415471274abda87024967d7fe2206ceee0ea",
              "versionType": "git",
              "status": "affected"
            }
          ]
        },
        {
          "vendor": "Linux",
          "product": "Linux",
          "defaultStatus": "affected",
          "programFiles": [
            "drivers/tty/serial/8250/8250_of.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "versions": [
            {
              "version": "2.6.36",
              "status": "affected"
            },
            {
              "version": "0",
              "lessThan": "2.6.36",
              "versionType": "semver",
              "status": "unaffected"
            },
            {
              "version": "6.6.160",
              "lessThanOrEqual": "6.6.*",
              "versionType": "semver",
              "status": "unaffected"
            },
            {
              "version": "6.12.106",
              "lessThanOrEqual": "6.12.*",
              "versionType": "semver",
              "status": "unaffected"
            },
            {
              "version": "6.18.45",
              "lessThanOrEqual": "6.18.*",
              "versionType": "semver",
              "status": "unaffected"
            },
            {
              "version": "7.1.9",
              "lessThanOrEqual": "7.1.*",
              "versionType": "semver",
              "status": "unaffected"
            },
            {
              "version": "7.2",
              "lessThanOrEqual": "*",
              "versionType": "original_commit_for_fix",
              "status": "unaffected"
            }
          ]
        }
      ]
    }
  ],
  "metrics": {},
  "references": [
    {
      "url": "https://git.kernel.org/stable/c/1423415471274abda87024967d7fe2206ceee0ea",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/3ce24bc4d115336218e59b7e286fd3a79f4fc4c6",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/7795e8abedc86438cae0454602cbf9038b94bf38",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/c321dc5172c8c66e21ffbeeb7a2ebb88ae6fd4c3",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/cc325ce1c40a111824827532ac132afb3d1c342b",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ]
}