# CVE-2025-24032: libpam-pkcs11: PAM-PKCS#11 is a Linux-PAM login module that allows a X.509 certificatebased user login

CVE-2025-24032 is fixed in 3 products on 1 platform, first by libpam-pkcs11 0.6.12-2ubuntu0.24.10.1, released February 7, 2025. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2025-24032
- Priority: High
- CVSS: n/a (High)
- EPSS: 0.0071
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Feb 10, 2025

## Description

PAM-PKCS#11 is a Linux-PAM login module that allows a X.509 certificatebased user login. Prior to version 0.6.13, if cert_policy is set to none(the default value), then pam_pkcs11 will only check if the user is capableof logging into the token. An attacker may create a different token withthe user's public data (e.g. the user's certificate) and a PIN known to theattacker. If no signature with the private key is required, then theattacker may now login as user with that created token. The default to*not* check the private key's signature has been changed with commitcommi6638576892b59a99389043c90a1e7dd4d783b921, so that all versionsstarting with pam_pkcs11-0.6.0 should be affected. As a workaround, in`pam_pkcs11.conf`, set at least `cert_policy = signature;`.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | libpam-pkcs11 Ubuntu 18.04.6 LTS (bionic) | 0.6.9-2ubuntu0.1~esm1 | [libpam-pkcs11 0.6.9-2ubuntu0.1~esm1](https://patchblox.com/security/data/fix/linux/ubuntu-bionic-libpam-pkcs11-0.6.9-2ubuntu0.1-esm1.md) | Feb 10, 2025 |
| Linux | libpam-pkcs11 Ubuntu 20.04 LTS (focal) | 0.6.11-2ubuntu0.1 | [libpam-pkcs11 0.6.11-2ubuntu0.1](https://patchblox.com/security/data/fix/linux/ubuntu-focal-libpam-pkcs11-0.6.11-2ubuntu0.1.md) | Feb 10, 2025 |
| Linux | libpam-pkcs11 Ubuntu 22.04.1 LTS (jammy) | 0.6.11-4ubuntu0.1 | [libpam-pkcs11 0.6.11-4ubuntu0.1](https://patchblox.com/security/data/fix/linux/ubuntu-jammy-libpam-pkcs11-0.6.11-4ubuntu0.1.md) | Feb 10, 2025 |
| Linux | libpam-pkcs11 Ubuntu 24.04.5 LTS (noble) | 0.6.12-2ubuntu0.24.04.1 | [libpam-pkcs11 0.6.12-2ubuntu0.24.04.1](https://patchblox.com/security/data/fix/linux/ubuntu-noble-libpam-pkcs11-0.6.12-2ubuntu0.24.04.1.md) | Feb 10, 2025 |
| Linux | libpam-pkcs11 Ubuntu 24.10 (oracular) | 0.6.12-2ubuntu0.24.10.1 | [libpam-pkcs11 0.6.12-2ubuntu0.24.10.1](https://patchblox.com/security/data/fix/linux/ubuntu-oracular-libpam-pkcs11-0.6.12-2ubuntu0.24.10.1.md) | Feb 7, 2025 |
| Linux | pam-pkcs11 Debian 11.6 (bullseye) | 0.6.11-4+deb11u1 | [DLA-4058-1](https://patchblox.com/security/data/fix/linux/dla-4058-1.md) | Feb 18, 2025 |
| Linux | pam-pkcs11 Debian 12.15 (bookworm) | 0.6.12-1+deb12u1 | [DSA-5864-1](https://patchblox.com/security/data/fix/linux/dsa-5864-1.md) | Feb 12, 2025 |
| Linux | pam-pkcs11 Debian 13.5 (trixie) | 0.6.13-1 | [DEBIAN-CVE-2025-24032](https://patchblox.com/security/data/fix/linux/debian-cve-2025-24032.md) | Feb 10, 2025 |
| Linux | pam-pkcs11 Debian 14 | 0.6.13-1 | [DEBIAN-CVE-2025-24032](https://patchblox.com/security/data/fix/linux/debian-cve-2025-24032.md) | Feb 10, 2025 |
| Linux | pam_pkcs11 opensuse-leap 15.6 | 0.6.10-150600.16.3.1 | [SUSE-SU-2025:0689-1](https://patchblox.com/security/data/fix/linux/suse-su-2025-0689-1.md) | Feb 24, 2025 |
| Linux | pam_pkcs11 sles 15.6 | 0.6.10-150600.16.3.1 | [SUSE-SU-2025:0689-1](https://patchblox.com/security/data/fix/linux/suse-su-2025-0689-1.md) | Feb 24, 2025 |

---

Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.