iio: dac: ad3552r-hs: fix out-of-bound write in ad3552r_hs_write_data_source
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 978d28136c53df38f8f0b747191930e2f95e9084 and Kernel db16e7c52032c79156930a337ee17232931794ba.
In the Linux kernel, the following vulnerability has been resolved: iio: dac: ad3552r-hs: fix out-of-bound write in ad3552r_hs_write_data_source When simple_write_to_buffer() succeeds, it returns the number of bytes actually copied to the buffer. The code incorrectly uses 'count' as the index for null termination instead of the actual bytes copied. If count exceeds the buffer size, this leads to out-of-bounds write. Add a check for the count and use the return value as the index. The bug was validated using a demo module that mirrors the original code and was tested under QEMU. Pattern of the bug: - A fixed 64-byte stack buffer is filled using count. - If count > 64, the code still does buf[count] = '\0', causing an - out-of-bounds write on the stack. Steps for reproduce: - Opens the device node. - Writes 128 bytes of A to it. - This overflows the 64-byte stack buffer and KASAN reports the OOB. Found via static analysis. This is similar to the commit da9374819eb3 ("iio: backend: fix out-of-bound write")
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=b1c5d68ea66e511dfb16cd0e6a730488bd3c3317 <978d28136c53df38f8f0b747191930e2f95e9084, >=b1c5d68ea66e511dfb16cd0e6a730488bd3c3317 <db16e7c52032c79156930a337ee17232931794ba | 978d28136c53df38f8f0b747191930e2f95e9084, db16e7c52032c79156930a337ee17232931794ba |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket