# CVE-2024-57875: block: RCU protect disk->conv_zones_bitmap

> A use-after-free vulnerability in the Linux kernel block layer allows attackers to cause denial of service or execute arbitrary code via disk revalidation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 11 Jan 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-62633, AZL-68570, BELL-CVE-2024-57875, DEBIAN-CVE-2024-57875, GHSA-xr89-c9w4-g997, ROOT-OS-DEBIAN-11-CVE-2024-57875, ROOT-OS-DEBIAN-12-CVE-2024-57875, ROOT-OS-UBUNTU-2204-CVE-2024-57875, ROOT-OS-UBUNTU-2404-CVE-2024-57875, UBUNTU-CVE-2024-57875

## What is CVE-2024-57875?

CVE-2024-57875 is a high-severity use after free vulnerability in Linux kernel, published on 11 Jan 2025. 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: RCU protect disk->conv_zones_bitmap

Ensure that a disk revalidation changing the conventional zones bitmap
of a disk does not cause invalid memory references when using the
disk_zone_is_conv() helper by RCU protecting the disk->conv_zones_bitmap
pointer.

disk_zone_is_conv() is modified to operate under the RCU read lock and
the function disk_set_conv_zones_bitmap() is added to update a disk
conv_zones_bitmap pointer using rcu_replace_pointer() with the disk
zone_wplugs_lock spinlock held.

disk_free_zone_resources() is modified to call
disk_update_zone_resources() with a NULL bitmap pointer to free the disk
conv_zones_bitmap. disk_set_conv_zones_bitmap() is also used in
disk_update_zone_resources() to set the new (revalidated) bitmap and
free the old one.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-57875?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-57875?

Apply the vendor's patch.

## Is CVE-2024-57875 being exploited?

There is no known exploitation of CVE-2024-57875 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-2024-57875 and fix it if it is affected.

What it is: CVE-2024-57875 is a high-severity use after free vulnerability in Linux kernel, published on 11 Jan 2025. 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-2024-57875 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-2024-57875/ (Markdown: https://insights.sbomify.com/CVE-2024-57875/index.md)
```

## Sources

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

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