Answer in brief
CVE-2024-44950 records a Unknown severity vulnerability in serial: sc16is7xx: fix invalid FIFO access with special register set. 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 | 3.16 | Not reported |
| Linux/Linuxgeneric | >=dfeae619d781dee61666d5551b93ba3be755a86b <cc6a3f35bc9b3a8da1b195420a2e8d9fdadfa831 || >=dfeae619d781dee61666d5551b93ba3be755a86b <dc5ead0e8fc5ef53b8553394d4aab60c277976b3 || >=dfeae619d781dee61666d5551b93ba3be755a86b <6a6730812220a9a5ce4003eb347da1ee5abd06b0 || >=dfeae619d781dee61666d5551b93ba3be755a86b <7d3b793faaab1305994ce568b59d61927235f57b | cc6a3f35bc9b3a8da1b195420a2e8d9fdadfa831, dc5ead0e8fc5ef53b8553394d4aab60c277976b3, 6a6730812220a9a5ce4003eb347da1ee5abd06b0, 7d3b793faaab1305994ce568b59d61927235f57b |
Published upstream
Sep 4, 2024
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: sc16is7xx: fix invalid FIFO access with special register set When enabling access to the special register set, Receiver time-out and RHR interrupts can happen. In this case, the IRQ handler will try to read from the FIFO thru the RHR register at address 0x00, but address 0x00 is mapped to DLL register, resulting in erroneous FIFO reading. Call graph example: sc16is7xx_startup(): entry sc16is7xx_ms_proc(): entry sc16is7xx_set_termios(): entry sc16is7xx_set_baud(): DLH/DLL = $009C --> access special register set sc16is7xx_port_irq() entry --> IIR is 0x0C sc16is7xx_handle_rx() entry sc16is7xx_fifo_read(): --> unable to access FIFO (RHR) because it is mapped to DLL (LCR=LCR_CONF_MODE_A) sc16is7xx_set_baud(): exit --> Restore access to general register set Fix the problem by claiming the efr_lock mutex when accessing the Special register set.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-44950 records a Unknown severity vulnerability in serial: sc16is7xx: fix invalid FIFO access with special register set. 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 | 3.16 | Not reported |
| Linux/Linuxgeneric | >=dfeae619d781dee61666d5551b93ba3be755a86b <cc6a3f35bc9b3a8da1b195420a2e8d9fdadfa831 || >=dfeae619d781dee61666d5551b93ba3be755a86b <dc5ead0e8fc5ef53b8553394d4aab60c277976b3 || >=dfeae619d781dee61666d5551b93ba3be755a86b <6a6730812220a9a5ce4003eb347da1ee5abd06b0 || >=dfeae619d781dee61666d5551b93ba3be755a86b <7d3b793faaab1305994ce568b59d61927235f57b | cc6a3f35bc9b3a8da1b195420a2e8d9fdadfa831, dc5ead0e8fc5ef53b8553394d4aab60c277976b3, 6a6730812220a9a5ce4003eb347da1ee5abd06b0, 7d3b793faaab1305994ce568b59d61927235f57b |
Published upstream
Sep 4, 2024
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: sc16is7xx: fix invalid FIFO access with special register set When enabling access to the special register set, Receiver time-out and RHR interrupts can happen. In this case, the IRQ handler will try to read from the FIFO thru the RHR register at address 0x00, but address 0x00 is mapped to DLL register, resulting in erroneous FIFO reading. Call graph example: sc16is7xx_startup(): entry sc16is7xx_ms_proc(): entry sc16is7xx_set_termios(): entry sc16is7xx_set_baud(): DLH/DLL = $009C --> access special register set sc16is7xx_port_irq() entry --> IIR is 0x0C sc16is7xx_handle_rx() entry sc16is7xx_fifo_read(): --> unable to access FIFO (RHR) because it is mapped to DLL (LCR=LCR_CONF_MODE_A) sc16is7xx_set_baud(): exit --> Restore access to general register set Fix the problem by claiming the efr_lock mutex when accessing the Special register set.
Quoted source text, attributed separately from HOL analysis.