LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49031: iio: health: afe4403: Fix oob read in afe4403_read_raw

In the Linux kernel, the following vulnerability has been resolved: iio: health: afe4403: Fix oob read in afe4403_read_raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4403_read_raw+0x42e/0x4c0 Read of size 4 at addr ffffffffc02ac638 by task cat/279 Call Trace: afe4403_read_raw iio_read_channel_info dev_attr_show The buggy address belongs to the variable: afe4403_channel_leds+0x18/0xffffffffffffe9e0 This issue can be reproduced by singe command: $ cat /sys/bus/spi/devices/spi0.0/iio\:device0/in_intensity6_raw The array size of afe4403_channel_leds is less than channels, so access with chan->address cause OOB read in afe4403_read_raw. Fix it by moving access before use it.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is an out-of-bounds read in the AFE4403 health sensor driver. It matters mainly where systems use that driver and expose the related IIO sensor interface. The public record provides fixes but no CVSS score and no evidence of active exploitation.

Executive priority

Treat this as targeted maintenance for Linux-based devices using the affected health sensor driver. It is not currently supported by the sources as an internet-scale emergency, but affected embedded fleets should patch through normal kernel update channels.

Technical view

The flaw is in afe4403_read_raw in the Linux IIO health driver. The driver can index afe4403_channel_leds using a channel address beyond that array, producing a KASAN-reported global out-of-bounds read via the IIO sysfs read path. Stable kernel commits are referenced as fixes.

Likely exposure

Exposure appears most likely on Linux systems, often embedded or device-oriented, that include the AFE4403 driver and expose the affected IIO device interface. General-purpose servers without this driver and device path are less likely to be exposed based on the provided sources.

Exploitation context

The bundle shows a local read path through sysfs and KASAN evidence of an out-of-bounds read. CISA KEV is false, and the provided sources do not claim active exploitation, remote exploitation, privilege escalation, or public exploit availability.

Researcher notes

The key exposure condition is driver and IIO interface presence, not Linux use alone. The source describes an array-size mismatch and fix ordering around channel LED access. Severity, CWE mapping, and exploit impact remain under-specified in the provided record.

Mitigation direction

  • Update to a kernel build containing the referenced stable fixes.
  • Confirm distro or device-vendor kernels include the relevant backport.
  • Prioritize systems using the AFE4403 IIO health sensor driver.
  • If patching is delayed, check vendor guidance for supported workarounds.
  • Track this as a kernel maintenance issue for affected devices.

Validation and detection

  • Inventory Linux kernel versions on devices using AFE4403 hardware or drivers.
  • Check whether the running kernel includes one of the referenced fix commits.
  • Verify whether the affected IIO device interface exists on target systems.
  • Review vendor kernel advisories for backport status and package names.
  • Run regression tests after kernel update on affected hardware.
Prepared
Confidence
medium
Sources
10

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-49031 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
9Source 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
LinuxLinuxb36e8257641a043764c62240316610c81e36376c, b36e8257641a043764c62240316610c81e36376c, b36e8257641a043764c62240316610c81e36376c, b36e8257641a043764c62240316610c81e36376c, b36e8257641a043764c62240316610c81e36376c, b36e8257641a043764c62240316610c81e36376c, b36e8257641a043764c62240316610c81e36376c, b36e8257641a043764c62240316610c81e36376cunaffected
LinuxLinux4.8, 0, 4.9.335, 4.14.301, 4.19.268, 5.4.226, 5.10.158, 5.15.82, 6.0.12, 6.1affected
Weakness

CWE details

No CWE listed

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