CVE-2024-44951

serial: sc16is7xx: fix TX fifo corruption

HIGH
7.8
CVSS Score
Published: September 4, 2024 at 06:35 PM UTC
Updated: October 21, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.1.76 ≤ v < 6.26.6.15 ≤ v < 6.76.7.3 ≤ v < 6.86.8 ≤ v < 6.10.54409df5866b7ff7686ba27e449ca97a92ee063c94b068e55bf5ea7bab4d8a282c6a24b03e80c0b686.1.766.116.11 rc16.11 rc26.6.156.7.39879e1bec3c0f077427dd0d258c80c63ce9babdfdbe196ca489f3833e0f9eeb86ac346194f131c91
Vendor states this is fixed in 09cfe05e9907f3276887a20e267cc40e202f4fdd (fixed)
Vendor states this is fixed in 133f4c00b8b2bfcacead9b81e7e8edfceb4b06c4 (fixed)
Vendor states this is fixed in 6.10.5 (unaffected)
Vendor states this is fixed in 6.11 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.160 (unaffected)
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.8 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card