Before calling add partition or resize partition, there is no check on whether the length is aligned with the logical block size. If the logical block size of the disk is larger than 512 bytes, then the partition size maybe not the multiple of the logical block size, and when the last sector is read, bio_truncate() will adjust the bio size, resulting in an IO error if the size of the read command is smaller than the logical block size.If integrity data is supported, this will also result in a null pointer dereference when calling bio_integrity_free.
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 2265806]
Fixed in 5.15.148 with commit 5010c2712096 Fixed in 6.1.75 with commit ef31cc877947 Fixed in 6.6.14 with commit cb16cc1abda1 Fixed in 6.7.2 with commit bcdc288e7bc0 Fixed in 6.8-rc1 with commit 6f64f866aa1a
This was fixed for Fedora with the 6.6.14 stable kernel updates.
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2023-52458 is: CHECK Maybe valid. Check manually. with impact MODERATE (that is approximation based on flags NULLPTR DISK SIMPLEFIX LOG IMPROVEONLY ; these flags parsed automatically based on patche 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.
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:4928 https://access.redhat.com/errata/RHSA-2024:4928
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Extended Update Support Via RHSA-2024:5067 https://access.redhat.com/errata/RHSA-2024:5067
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Extended Update Support Via RHSA-2024:5066 https://access.redhat.com/errata/RHSA-2024:5066