LiveActive security incident?Get immediate response
CVE Record

CVE-2024-44951: serial: sc16is7xx: fix TX fifo corruption

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-44951 is a Linux kernel serial-driver bug where data received on one SC16IS7xx channel can corrupt data being transmitted on another. For exposed systems, the business risk is unreliable or misdirected serial communications, not a documented internet-facing compromise path.

Executive priority

Targeted review is warranted, not broad emergency response. Prioritize assets where serial data integrity affects operations, safety monitoring, access control, or device-to-device communications. Official severity and CVSS are not provided in the source bundle.

Technical view

The issue is a regression after Linux commit 4409df5866b7. Per-channel EFR locking no longer protected a shared data buffer used by Tx, Rx, and multiple IC channels. Fixes remove shared Tx buffer reliance with kfifo_out_linear_ptr() and use separate Rx buffers per channel.

Likely exposure

Exposure appears limited to Linux systems using the sc16is7xx serial driver with affected kernel code. The provided record lists Linux as the affected product and references stable kernel fixes, but does not give CPEs or a complete deployment inventory.

Exploitation context

The supplied sources describe observed packet corruption using a logic analyzer. They do not report active exploitation, public weaponization, or KEV listing. Treat this as an integrity and potential cross-channel data exposure issue in affected serial deployments.

Researcher notes

Key uncertainty is exact affected-version boundaries from the supplied normalized data. The root cause is shared buffer protection loss after an EFR locking regression. Analysis should focus on whether downstream vendor kernels carry the regression and the stable buffer-isolation fixes.

Mitigation direction

  • Check whether systems use the Linux sc16is7xx serial driver.
  • Update to a vendor kernel containing the referenced stable fixes.
  • Prioritize embedded, industrial, and appliance systems using multi-channel serial interfaces.
  • If immediate update is unavailable, ask the vendor for supported mitigation guidance.

Validation and detection

  • Inventory running kernel versions and loaded serial drivers.
  • Confirm whether SC16IS7xx hardware or device-tree entries are present.
  • Compare kernel source or package changelog against the referenced stable commits.
  • Run regression tests for serial Tx/Rx behavior after patching.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-44951 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4409df5866b7ff7686ba27e449ca97a92ee063c9, 4409df5866b7ff7686ba27e449ca97a92ee063c9, 4b068e55bf5ea7bab4d8a282c6a24b03e80c0b68, 9879e1bec3c0f077427dd0d258c80c63ce9babdf, dbe196ca489f3833e0f9eeb86ac346194f131c91, 6.1.76, 6.6.15, 6.7.3unaffected
LinuxLinux6.8, 0, 6.10.5, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.