Buffer overflow in Linux
CVE-2021-47172
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.
Vulnerability class: Buffer Overflow
EPSS: 0.002 (13.3th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 5.5 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Affected products
- Linux — versions 5.5, d7857e4ee1ba69732b16c73b2f2dde83ecd78ee4, 5.4.124
- Linux Linux_kernel — versions 5.13
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2021-47172?
- CVE-2021-47172 is a medium-severity vulnerability in Linux, classified under Buffer Copy without Checking Size of Input (Classic Buffer Overflow). CVSS score: 5.5/10. Published 2024-03-25.
- How severe is CVE-2021-47172?
- Medium severity. CVSS v3 base score is 5.5 out of 10.