LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52488: serial: sc16is7xx: convert from _raw_ to _noinc_ regmap functions for FIFO

In the Linux kernel, the following vulnerability has been resolved: serial: sc16is7xx: convert from _raw_ to _noinc_ regmap functions for FIFO The SC16IS7XX IC supports a burst mode to access the FIFOs where the initial register address is sent ($00), followed by all the FIFO data without having to resend the register address each time. In this mode, the IC doesn't increment the register address for each R/W byte. The regmap_raw_read() and regmap_raw_write() are functions which can perform IO over multiple registers. They are currently used to read/write from/to the FIFO, and although they operate correctly in this burst mode on the SPI bus, they would corrupt the regmap cache if it was not disabled manually. The reason is that when the R/W size is more than 1 byte, these functions assume that the register address is incremented and handle the cache accordingly. Convert FIFO R/W functions to use the regmap _noinc_ versions in order to remove the manual cache control which was a workaround when using the _raw_ versions. FIFO registers are properly declared as volatile so cache will not be used/updated for FIFO accesses.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-52488 is a Linux kernel issue in the SC16IS7XX serial driver. It concerns how FIFO data is read and written through regmap. The public sources describe possible regmap cache corruption, not a broadly exploitable remote attack. Exposure appears limited to systems using this specific serial hardware and driver.

Executive priority

Handle through normal kernel patch governance unless SC16IS7XX serial hardware supports safety-critical, industrial, or revenue-impacting operations. In those environments, prioritize validation because the main risk described is reliability or data integrity in a hardware driver path.

Technical view

The sc16is7xx driver used regmap_raw_read/write for FIFO access. Those APIs assume register addresses increment across multi-byte transfers, while the SC16IS7XX FIFO burst mode does not. The fix converts FIFO operations to regmap no-increment helpers and relies on FIFO registers being volatile so cache is not used or updated for FIFO access.

Likely exposure

Likely exposure is Linux systems with the SC16IS7XX serial driver active, especially embedded or hardware-integrated platforms using this UART bridge. General-purpose servers without this hardware or driver path are unlikely to be affected based on the provided sources.

Exploitation context

The source bundle does not cite active exploitation, public exploit use, KEV listing, CVSS, or CWE data. The described condition is driver and hardware specific. Treat exploitation likelihood as unproven from the available evidence.

Researcher notes

Evidence is limited to kernel commit descriptions, CVE metadata, and a Debian LTS advisory reference. The vulnerability centers on regmap cache behavior during FIFO burst access. The provided sources do not define attacker prerequisites, impact severity, or a standalone mitigation besides applying fixed kernel code.

Mitigation direction

  • Update to a vendor-supported kernel containing the linked stable fixes.
  • Apply relevant distribution security updates, including Debian LTS guidance where applicable.
  • Prioritize systems using SC16IS7XX serial hardware in operational environments.
  • Check vendor advisories for backported fixes before custom kernel changes.
  • Regression test affected serial workflows after updating the kernel.

Validation and detection

  • Inventory kernels and hardware for SC16IS7XX driver usage.
  • Confirm the running kernel includes the relevant stable fix or vendor backport.
  • Review distribution advisory status for deployed Linux versions.
  • Test serial communication paths that depend on SC16IS7XX hardware.
  • Monitor kernel logs for serial driver regressions after patching.
Prepared
Confidence
medium
Sources
9

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-2023-52488 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
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxdfeae619d781dee61666d5551b93ba3be755a86b, dfeae619d781dee61666d5551b93ba3be755a86b, dfeae619d781dee61666d5551b93ba3be755a86b, dfeae619d781dee61666d5551b93ba3be755a86b, dfeae619d781dee61666d5551b93ba3be755a86b, dfeae619d781dee61666d5551b93ba3be755a86bunaffected
LinuxLinux3.16, 0, 5.10.215, 5.15.154, 6.1.76, 6.6.15, 6.7.3, 6.8affected
Weakness

CWE details

No CWE listed

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