Answer in brief
CVE-2024-44951 records a Unknown severity vulnerability in serial: sc16is7xx: fix TX fifo corruption. 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 | >=4409df5866b7ff7686ba27e449ca97a92ee063c9 <09cfe05e9907f3276887a20e267cc40e202f4fdd || >=4409df5866b7ff7686ba27e449ca97a92ee063c9 <133f4c00b8b2bfcacead9b81e7e8edfceb4b06c4 || 4b068e55bf5ea7bab4d8a282c6a24b03e80c0b68 || 9879e1bec3c0f077427dd0d258c80c63ce9babdf || dbe196ca489f3833e0f9eeb86ac346194f131c91 || >=6.1.76 <6.2 || >=6.6.15 <6.7 || >=6.7.3 <6.8 | 09cfe05e9907f3276887a20e267cc40e202f4fdd, 133f4c00b8b2bfcacead9b81e7e8edfceb4b06c4, 6.2, 6.7, 6.8 |
| Linux/Linuxgeneric | 6.8 | Not reported |
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 TX fifo corruption Sometimes, when a packet is received on channel A at almost the same time as a packet is about to be transmitted on channel B, we observe with a logic analyzer that the received packet on channel A is transmitted on channel B. In other words, the Tx buffer data on channel B is corrupted with data from channel A. The problem appeared since commit 4409df5866b7 ("serial: sc16is7xx: change EFR lock to operate on each channels"), which changed the EFR locking to operate on each channel instead of chip-wise. This commit has introduced a regression, because the EFR lock is used not only to protect the EFR registers access, but also, in a very obscure and undocumented way, to protect access to the data buffer, which is shared by the Tx and Rx handlers, but also by each channel of the IC. Fix this regression first by switching to kfifo_out_linear_ptr() in sc16is7xx_handle_tx() to eliminate the need for a shared Rx/Tx buffer. Secondly, replace the chip-wise Rx buffer with a separate Rx buffer for each channel.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-44951 records a Unknown severity vulnerability in serial: sc16is7xx: fix TX fifo corruption. 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 | >=4409df5866b7ff7686ba27e449ca97a92ee063c9 <09cfe05e9907f3276887a20e267cc40e202f4fdd || >=4409df5866b7ff7686ba27e449ca97a92ee063c9 <133f4c00b8b2bfcacead9b81e7e8edfceb4b06c4 || 4b068e55bf5ea7bab4d8a282c6a24b03e80c0b68 || 9879e1bec3c0f077427dd0d258c80c63ce9babdf || dbe196ca489f3833e0f9eeb86ac346194f131c91 || >=6.1.76 <6.2 || >=6.6.15 <6.7 || >=6.7.3 <6.8 | 09cfe05e9907f3276887a20e267cc40e202f4fdd, 133f4c00b8b2bfcacead9b81e7e8edfceb4b06c4, 6.2, 6.7, 6.8 |
| Linux/Linuxgeneric | 6.8 | Not reported |
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 TX fifo corruption Sometimes, when a packet is received on channel A at almost the same time as a packet is about to be transmitted on channel B, we observe with a logic analyzer that the received packet on channel A is transmitted on channel B. In other words, the Tx buffer data on channel B is corrupted with data from channel A. The problem appeared since commit 4409df5866b7 ("serial: sc16is7xx: change EFR lock to operate on each channels"), which changed the EFR locking to operate on each channel instead of chip-wise. This commit has introduced a regression, because the EFR lock is used not only to protect the EFR registers access, but also, in a very obscure and undocumented way, to protect access to the data buffer, which is shared by the Tx and Rx handlers, but also by each channel of the IC. Fix this regression first by switching to kfifo_out_linear_ptr() in sc16is7xx_handle_tx() to eliminate the need for a shared Rx/Tx buffer. Secondly, replace the chip-wise Rx buffer with a separate Rx buffer for each channel.
Quoted source text, attributed separately from HOL analysis.