# CVE-2023-52458: block: add check that partition length needs to be aligned with block size

> A missing alignment check in the Linux kernel block layer can cause a null pointer dereference and IO errors when reading the last sector of a partition on disks with large logical block sizes.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Feb 2024
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2023-52458, DEBIAN-CVE-2023-52458, GHSA-w4r8-q3v5-4x28, UBUNTU-CVE-2023-52458

## What is CVE-2023-52458?

CVE-2023-52458 is a medium-severity vulnerability in Linux kernel, published on 23 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

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, 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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2023-52458?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-52458?

Apply the vendor's patch.

## Is CVE-2023-52458 being exploited?

There is no known exploitation of CVE-2023-52458 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52458 and fix it if it is affected.

What it is: CVE-2023-52458 is a medium-severity vulnerability in Linux kernel, published on 23 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52458 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-52458/ (Markdown: https://insights.sbomify.com/CVE-2023-52458/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-52458
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-52458
- OSV: https://osv.dev/vulnerability/CVE-2023-52458

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-52458/
Summaries are generated and may contain mistakes; the official description above is the record.