iio: adc: ad7124: Fix potential overflow due to non sequential channel numbers
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.4.124, Kernel f49149964d2423fb618fb6b755bb1eaa431cca2c, Kernel 26da8040eccc6c6b0e415e9a3baf72fd39eb2fdc and 2 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.5, >=5.4.14 <5.4.124, >=5408cbc6337300d6f1a87c797273c535ed96305a <f49149964d2423fb618fb6b755bb1eaa431cca2c, >=d7857e4ee1ba69732b16c73b2f2dde83ecd78ee4 <26da8040eccc6c6b0e415e9a3baf72fd39eb2fdc, >=d7857e4ee1ba69732b16c73b2f2dde83ecd78ee4 <f2a772c51206b0c3f262e4f6a3812c89a650191b, >=d7857e4ee1ba69732b16c73b2f2dde83ecd78ee4 <f70122825076117787b91e7f219e21c09f11a5b9 | 5.4.124, f49149964d2423fb618fb6b755bb1eaa431cca2c, 26da8040eccc6c6b0e415e9a3baf72fd39eb2fdc, f2a772c51206b0c3f262e4f6a3812c89a650191b, f70122825076117787b91e7f219e21c09f11a5b9 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket