i2c: i801: Fix block process call transactions According to the Intel datasheets, software must reset the block buffer index twice for block process call transactions: once before writing the outgoing data to the buffer, and once again before reading the incoming data from the buffer. The driver is currently missing the second reset, causing the wrong portion of the block buffer to be read.
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 2265898]
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:2394 https://access.redhat.com/errata/RHSA-2024:2394
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:3618 https://access.redhat.com/errata/RHSA-2024:3618
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:3627 https://access.redhat.com/errata/RHSA-2024:3627
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2024-26593 is: CHECK Maybe valid. Check manually. with impact LOW (that is an approximation based on flags USB SIMPLEFIX ; these flags parsed automatically based on patch data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later.