CVE-2023-52458: block: add check that partition length needs to be aligned with block size
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, biotruncate() 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 biointegrityfree.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2023-52458?
CVE-2023-52458 has been classified with a severity level that indicates a potential risk during partition resizing and adding due to alignment issues with logical block sizes.
How do I fix CVE-2023-52458?
To mitigate CVE-2023-52458, update to the remedied versions provided by your distribution, specifically Red Hat kernel 6.8 or Debian Linux versions indicated.
What systems are affected by CVE-2023-52458?
CVE-2023-52458 affects multiple versions of the Linux kernel, specifically those that do not enforce checks on partition size alignment.
Is CVE-2023-52458 a denial of service risk?
CVE-2023-52458 does not explicitly state a denial of service vulnerability, but improper partition management may lead to unexpected behaviors.
Can CVE-2023-52458 be exploited remotely?
CVE-2023-52458 does not mention remote exploitation, suggesting that exploitation would require local access to the system.