luksmeta - Debian Package Tracker

general

source: luksmeta (main)
version: 10-2
maintainer: Christoph Biedl (DMD)
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 9-3
oldstable: 9-4+deb12u1
stable: 9-4+deb13u1
testing: 10-2
unstable: 10-2

versioned links

9-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
9-4+deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
9-4+deb13u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
10-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libluksmeta-dev
libluksmeta0
luksmeta

action needed

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2026-10-19 Last update: 2026-10-22 06:21

2 security issues in trixie high

There are 2 open security issues in trixie.

1 important issue:

CVE-2026-107565: A flaw was found in luksmeta. A local attacker with administrative privileges can cause data corruption when saving metadata to a Linux Unified Key Setup (LUKS) device. Due to incorrect boundary calculations and flawed overlap detection, new metadata entries can be written beyond available free space or over existing records. This issue can corrupt stored encrypted payload data or existing metadata, potentially rendering the affected data inaccessible.

1 issue left for the package maintainer to handle:

CVE-2026-111555: (needs triaging) A flaw was found in luksmeta. Improper boundary validation of metadata slots allows an attacker capable of supplying or modifying a disk header to redirect wipe or load operations outside the intended metadata area. An attacker could exploit this vulnerability by providing a crafted header with valid checksums to overwrite or zero out encrypted payload data, resulting in persistent data loss and corrupted storage. Exploitation typically requires privileged access to modify raw block devices or the ability to induce an administrator to process an untrusted disk image.

You can find information about how to handle this issue in the security team's documentation.

Created: 2026-10-09 Last update: 2026-10-21 11:33

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2026-107565: A flaw was found in luksmeta. A local attacker with administrative privileges can cause data corruption when saving metadata to a Linux Unified Key Setup (LUKS) device. Due to incorrect boundary calculations and flawed overlap detection, new metadata entries can be written beyond available free space or over existing records. This issue can corrupt stored encrypted payload data or existing metadata, potentially rendering the affected data inaccessible.

Created: 2026-10-09 Last update: 2026-10-21 11:33

1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:

CVE-2026-107565: A flaw was found in luksmeta. A local attacker with administrative privileges can cause data corruption when saving metadata to a Linux Unified Key Setup (LUKS) device. Due to incorrect boundary calculations and flawed overlap detection, new metadata entries can be written beyond available free space or over existing records. This issue can corrupt stored encrypted payload data or existing metadata, potentially rendering the affected data inaccessible.

Created: 2026-10-09 Last update: 2026-10-21 11:33

2 security issues in bookworm high

There are 2 open security issues in bookworm.

1 important issue:

CVE-2026-107565: A flaw was found in luksmeta. A local attacker with administrative privileges can cause data corruption when saving metadata to a Linux Unified Key Setup (LUKS) device. Due to incorrect boundary calculations and flawed overlap detection, new metadata entries can be written beyond available free space or over existing records. This issue can corrupt stored encrypted payload data or existing metadata, potentially rendering the affected data inaccessible.

1 issue postponed or untriaged:

CVE-2026-111555: (postponed; to be fixed through a stable update) A flaw was found in luksmeta. Improper boundary validation of metadata slots allows an attacker capable of supplying or modifying a disk header to redirect wipe or load operations outside the intended metadata area. An attacker could exploit this vulnerability by providing a crafted header with valid checksums to overwrite or zero out encrypted payload data, resulting in persistent data loss and corrupted storage. Exploitation typically requires privileged access to modify raw block devices or the ability to induce an administrator to process an untrusted disk image.

Created: 2026-10-09 Last update: 2026-10-21 11:33

Multiarch hinter reports 1 issue(s) normal

There are issues with the multiarch metadata for this package.

libluksmeta-dev could be marked Multi-Arch: same

Created: 2026-10-20 Last update: 2026-10-22 15:30

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.2).

Created: 2025-12-23 Last update: 2026-10-19 04:30

news

[rss feed]

[2026-10-22] luksmeta 10-2 MIGRATED to testing (Debian testing watch)
[2026-10-18] Accepted luksmeta 10-2 (source) into unstable (Christoph Biedl)
[2025-12-06] Accepted luksmeta 9-4+deb12u1 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Christoph Biedl)
[2025-11-05] Accepted luksmeta 9-4+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Christoph Biedl)
[2025-11-04] luksmeta 10-1 MIGRATED to testing (Debian testing watch)
[2025-11-01] Accepted luksmeta 10-1 (source) into unstable (Christoph Biedl)
[2022-12-31] luksmeta 9-4 MIGRATED to testing (Debian testing watch)
[2022-12-25] Accepted luksmeta 9-4 (source) into unstable (Christoph Biedl)
[2019-03-11] luksmeta 9-3 MIGRATED to testing (Debian testing watch)
[2019-03-01] Accepted luksmeta 9-3 (source) into unstable (Christoph Biedl)
[2018-12-12] luksmeta 9-2 MIGRATED to testing (Debian testing watch)
[2018-12-09] Accepted luksmeta 9-2 (source) into unstable (Christoph Biedl)
[2018-08-31] luksmeta 9-1 MIGRATED to testing (Debian testing watch)
[2018-08-26] Accepted luksmeta 9-1 (source) into unstable (Christoph Biedl)
[2017-11-22] luksmeta 8-3 MIGRATED to testing (Debian testing watch)
[2017-11-16] Accepted luksmeta 8-3 (source powerpc) into unstable (Christoph Biedl)
[2017-11-14] Accepted luksmeta 8-2 (source powerpc) into unstable (Christoph Biedl)
[2017-11-14] Accepted luksmeta 8-1 (source powerpc) into unstable, unstable (Christoph Biedl)

bugs [bug history graph]

all: 1
RC: 0
I&N: 1
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian
buildd: logs, reproducibility, cross
popcon
browse source code
other distros
security tracker
debian patches

ubuntu

[Information about Ubuntu for Debian Developers]

version: 10-1