LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48927: iio: adc: tsc2046: fix memory corruption by preventing array overflow

In the Linux kernel, the following vulnerability has been resolved: iio: adc: tsc2046: fix memory corruption by preventing array overflow On one side we have indio_dev->num_channels includes all physical channels + timestamp channel. On other side we have an array allocated only for physical channels. So, fix memory corruption by ARRAY_SIZE() instead of num_channels variable. Note the first case is a cleanup rather than a fix as the software timestamp channel bit in active_scanmask is never set by the IIO core.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory corruption issue in the tsc2046 IIO ADC touchscreen driver. It comes from using a channel count that includes a timestamp entry against an array sized only for physical channels. Business urgency depends on whether affected kernels and this driver are present in deployed systems.

Executive priority

Handle through routine kernel patch governance unless internal inventory shows exposed embedded or device fleets using this driver. Escalate if the affected driver is present on safety-critical, physical-accessible, or hard-to-patch systems.

Technical view

CVE-2022-48927 fixes an array overflow in the Linux kernel tsc2046 ADC driver. indio_dev->num_channels includes physical channels plus the timestamp channel, while the target array only covers physical channels. The upstream fix uses ARRAY_SIZE() to avoid writing past the allocated array.

Likely exposure

Exposure is most likely in Linux systems running affected kernel versions with the tsc2046 driver built in or loadable. The provided data does not identify specific distributions, appliances, or cloud images, so product-level exposure requires local kernel and vendor-package checks.

Exploitation context

The source bundle reports no CISA KEV listing, no CVSS score, and no public exploitation evidence. Treat this as a memory corruption defect with uncertain exploitability rather than confirmed active exploitation.

Researcher notes

Evidence is limited to the CVE description and Linux stable commit references. The bug is an array bounds issue caused by mismatched channel accounting. The note says one related case is cleanup because IIO core never sets the software timestamp channel bit in active_scanmask.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes matching CVE-2022-48927.
  • Prioritize systems using the tsc2046 IIO ADC touchscreen driver.
  • If patch status is unclear, request vendor guidance before assuming remediation.
  • Track kernel update completion through normal vulnerability management workflow.

Validation and detection

  • Inventory kernel versions across Linux hosts and embedded images.
  • Check whether the tsc2046 driver is built, loaded, or packaged.
  • Confirm installed kernel changelogs reference CVE-2022-48927 or the stable commits.
  • Review vendor advisories for affected and fixed package versions.
  • Retest representative devices after kernel update for touchscreen and ADC behavior.
Prepared
Confidence
medium
Sources
5

Public sources used

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-2022-48927 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
4Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9374e8f5a38defe90bc65b2decf317c1c62d91dd, 9374e8f5a38defe90bc65b2decf317c1c62d91dd, 9374e8f5a38defe90bc65b2decf317c1c62d91ddunaffected
LinuxLinux5.14, 0, 5.15.26, 5.16.12, 5.17affected
Weakness

CWE details

No CWE listed

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