# CVE-2025-11568: Luksmeta: data corruption when handling luks1 partitions with luksmeta > An attacker with permissions can corrupt encrypted data by writing excessive metadata to LUKS1 devices due to improper space validation. - **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Oct 2025 - **Updated:** 1 Sep 2026 - **Also known as:** ALSA-2025:23086, ALSA-2026:18421, ALSA-2026:18824, AZL-72866, CLSA-2026-1779796898, CLSA-2026-1780411655, DEBIAN-CVE-2025-11568, GHSA-pvmm-7c2r-wmp4, OESA-2025-2688, RHSA-2025:23086, RHSA-2026:18421, RHSA-2026:18824, RLSA-2025:23086, RLSA-2026:18421, RLSA-2026:18824, UBUNTU-CVE-2025-11568 ## What is CVE-2025-11568? CVE-2025-11568 is a medium-severity vulnerability in Latchset Red Hat Enterprise Linux 10, published on 15 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A data corruption vulnerability has been identified in the luksmeta utility when used with the LUKS1 disk encryption format. An attacker with the necessary permissions can exploit this flaw by writing a large amount of metadata to an encrypted device. The utility fails to correctly validate the available space, causing the metadata to overwrite and corrupt the user's encrypted data. This action leads to a permanent loss of the stored information. Devices using the LUKS formats other than LUKS1 are not affected by this issue. Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input) ## Which versions are affected by CVE-2025-11568? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libluksmeta` | AlmaLinux:10 | All versions | 10-1.el10 | | `libluksmeta-devel` | AlmaLinux:10 | All versions | 10-1.el10 | | `luksmeta` | AlmaLinux:10 | All versions | 10-1.el10 | | `libluksmeta` | AlmaLinux:8 | All versions | 9-4.el8_10.1 | | `libluksmeta-devel` | AlmaLinux:8 | All versions | 9-4.el8_10.1 | | `luksmeta` | AlmaLinux:8 | All versions | 9-4.el8_10.1 | | `libluksmeta` | AlmaLinux:9 | All versions | 10-1.el9 | | `libluksmeta-devel` | AlmaLinux:9 | All versions | 10-1.el9 | | `luksmeta` | AlmaLinux:9 | All versions | 10-1.el9 | | `libluksmeta` | Red Hat:enterprise_linux:10.2 | All versions | 0:10-1.el10 | | `libluksmeta-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:10-1.el10 | | `libluksmeta-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:10-1.el10 | | `luksmeta` | Red Hat:enterprise_linux:10.2 | All versions | 0:10-1.el10 | | `luksmeta-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:10-1.el10 | | `luksmeta-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:10-1.el10 | | `libluksmeta` | Red Hat:enterprise_linux:8::appstream | All versions | 0:9-4.el8_10.1 | | `libluksmeta-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:9-4.el8_10.1 | | `libluksmeta-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:9-4.el8_10.1 | | `luksmeta` | Red Hat:enterprise_linux:8::appstream | All versions | 0:9-4.el8_10.1 | | `luksmeta-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:9-4.el8_10.1 | | `luksmeta-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:9-4.el8_10.1 | | `libluksmeta` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10-1.el9 | | `libluksmeta-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10-1.el9 | | `luksmeta` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10-1.el9 | | `luksmeta-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10-1.el9 | | `luksmeta-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:10-1.el9 | | `libluksmeta-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:10-1.el9 | | `libluksmeta-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:10-1.el9 | | `luksmeta-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:10-1.el9 | | `luksmeta-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:10-1.el9 | | `luksmeta` | Rocky Linux:10 | All versions | 0:10-1.el10 | | `luksmeta` | Rocky Linux:8 | All versions | 0:9-4.el8_10.1 | | `luksmeta` | Rocky Linux:9 | All versions | 0:10-1.el9 | ## How do I fix CVE-2025-11568? Apply the vendor's patch. ## Is CVE-2025-11568 being exploited? There is no known exploitation of CVE-2025-11568 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-11568 and fix it if it is affected. What it is: CVE-2025-11568 is a medium-severity vulnerability in Latchset Red Hat Enterprise Linux 10, published on 15 Oct 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-2025-11568 in the wild and no public exploit code. Affected product: Latchset Red Hat Enterprise Linux 10. 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-2025-11568/ (Markdown: https://insights.sbomify.com/CVE-2025-11568/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11568 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11568 - OSV: https://osv.dev/vulnerability/CVE-2025-11568 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-11568/ Summaries are generated and may contain mistakes; the official description above is the record.