CVE-2021-47172

iio: adc: ad7124: Fix potential overflow due to non sequential channel numbers

MEDIUM
5.5
CVSS Score
Published: March 25, 2024 at 09:16 AM UTC
Updated: June 17, 2026 at 04:16 AM 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
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: iio: adc: ad7124: Fix potential overflow due to non sequential channel numbers Channel numbering must start at 0 and then not have any holes, or it is possible to overflow the available storage. Note this bug was introduced as part of a fix to ensure we didn't rely on the ordering of child nodes. So we need to support arbitrary ordering but they all need to be there somewhere. Note I hit this when using qemu to test the rest of this series. Arguably this isn't the best fix, but it is probably the most minimal option for backporting etc. Alexandru's sign-off is here because he carried this patch in a larger set that Jonathan then applied.

Affected

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

5.11 ≤ v < 5.12.95.4.14 ≤ v < 5.4.1245.5 ≤ v < 5.10.425.5 ≤ v < 5.12.95.5 ≤ v < 5.135.13 rc15.13 rc25.13 rc35.4.145408cbc6337300d6f1a87c797273c535ed96305ad7857e4ee1ba69732b16c73b2f2dde83ecd78ee4
Vendor states this is fixed in 26da8040eccc6c6b0e415e9a3baf72fd39eb2fdc (fixed)
Vendor states this is fixed in f2a772c51206b0c3f262e4f6a3812c89a650191b (fixed)
Vendor states this is fixed in f49149964d2423fb618fb6b755bb1eaa431cca2c (fixed)
Vendor states this is fixed in f70122825076117787b91e7f219e21c09f11a5b9 (fixed)
Vendor states this is fixed in 5.10.42 (unaffected)
Vendor states this is fixed in 5.12.9 (unaffected)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.4.124 (unaffected)
Vendor states this is fixed in 5.5 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/26da8040eccc6c6b0e415e9a3baf72fd39eb2fdc
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f2a772c51206b0c3f262e4f6a3812c89a650191b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f49149964d2423fb618fb6b755bb1eaa431cca2c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f70122825076117787b91e7f219e21c09f11a5b9

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-120

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