# CVE-2025-6018: Pam-config: lpe from unprivileged to allow_active in pam > An unprivileged local attacker can escalate privileges to allow_active status, bypassing Polkit restrictions intended for console users. - **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:** 23 Jul 2025 - **Updated:** 30 Jun 2026 - **Also known as:** GHSA-cg9q-xmf9-7r6w, SUSE-RU-2025:20479-1, SUSE-SU-2025:02001-1, SUSE-SU-2025:02002-1, SUSE-SU-2025:02003-1, SUSE-SU-2025:02004-1, SUSE-SU-2025:02005-1, SUSE-SU-2025:02015-1, SUSE-SU-2025:02026-1, SUSE-SU-2025:02031-1, SUSE-SU-2025:02032-1, SUSE-SU-2025:02080-1, SUSE-SU-2025:02081-1, SUSE-SU-2025:02082-1, SUSE-SU-2025:20496-1, SUSE-SU-2025:20513-1, SUSE-SU-2025:20533-1, openSUSE-SU-2025:15219-1, openSUSE-SU-2025:15257-1 ## What is CVE-2025-6018? CVE-2025-6018 is a high-severity vulnerability in Red Hat Enterprise Linux 7, published on 23 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A Local Privilege Escalation (LPE) vulnerability has been discovered in pam-config within Linux Pluggable Authentication Modules (PAM). This flaw allows an unprivileged local attacker (for example, a user logged in via SSH) to obtain the elevated privileges normally reserved for a physically present, "allow_active" user. The highest risk is that the attacker can then perform all allow_active yes Polkit actions, which are typically restricted to console users, potentially gaining unauthorized control over system configurations, services, or other sensitive operations. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2025-6018? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gdm` | SUSE:Enterprise Storage 7.1 | All versions | 3.34.1-150200.8.26.1 | | `pam-config` | SUSE:Enterprise Storage 7.1 | All versions | 1.1-150200.3.14.1 | | `pam_pkcs11` | SUSE:Enterprise Storage 7.1 | All versions | 0.6.10-150100.3.11.1 | | `gdm` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 3.34.1-150200.8.26.1 | | `pam-config` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 1.1-150200.3.14.1 | | `pam_pkcs11` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 0.6.10-150100.3.11.1 | | `gdm` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 41.3-150400.4.14.1 | | `pam-config` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 1.1-150200.3.14.1 | | `pam_pkcs11` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 0.6.10-150100.3.11.1 | | `gdm` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 41.3-150400.4.14.1 | | `pam-config` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 1.1-150200.3.14.1 | | `pam_pkcs11` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 0.6.10-150100.3.11.1 | | `gdm` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 41.3-150400.4.14.1 | | `pam-config` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 1.1-150200.3.14.1 | | `pam_pkcs11` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 0.6.10-150100.3.11.1 | | `gdm` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 41.3-150400.4.14.1 | | `pam-config` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 1.1-150200.3.14.1 | | `pam_pkcs11` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 0.6.10-150100.3.11.1 | | `pam-config` | SUSE:Linux Enterprise Micro 5.1 | All versions | 1.1-150200.3.14.1 | | `pam_pkcs11` | SUSE:Linux Enterprise Micro 5.1 | All versions | 0.6.10-150100.3.11.1 | | `pam-config` | SUSE:Linux Enterprise Micro 5.2 | All versions | 1.1-150200.3.14.1 | | `pam_pkcs11` | SUSE:Linux Enterprise Micro 5.2 | All versions | 0.6.10-150100.3.11.1 | | `pam-config` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.1-150200.3.14.1 | | `pam_pkcs11` | SUSE:Linux Enterprise Micro 5.3 | All versions | 0.6.10-150100.3.11.1 | | `pam-config` | SUSE:Linux Enterprise Micro 5.4 | All versions | 1.1-150200.3.14.1 | | `pam_pkcs11` | SUSE:Linux Enterprise Micro 5.4 | All versions | 0.6.10-150100.3.11.1 | | `pam-config` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.1-150200.3.14.1 | | `pam_pkcs11` | SUSE:Linux Enterprise Micro 5.5 | All versions | 0.6.10-150100.3.11.1 | | `pam-config` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 1.1-150600.16.8.1 | | `pam_pkcs11` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 0.6.10-150600.16.8.1 | | `pam-config` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 1.1-150600.16.8.1 | | `pam_pkcs11` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 0.6.10-150600.16.8.1 | | `gdm` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | All versions | 45.0.1-150600.6.8.1 | | `gdm` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP7 | All versions | 45.0.1-150700.12.5.1 | | `gdm` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 3.10.0.1-54.23.1 | | `pam` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 1.1.8-24.71.1 | | `pam-config` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 0.89-5.8.1 | | `pam_pkcs11` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 0.6.8-7.13.1 | | `gdm` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 3.34.1-150200.8.26.1 | | `pam-config` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 1.1-150200.3.14.1 | Products: Suse Pam-Config. ## How do I fix CVE-2025-6018? Apply the vendor's patch. ## Is CVE-2025-6018 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6018 exists. Public exploit code: - A Proof of Concept for chaining CVE-2025-6018 (PAM/Polkit Active Session Bypass) and CVE-2025-6019 (libblockdev SUID Mount Flaw) to achieve Local Privilege Escalation (LPE) on vulnerable Linux systems. (github_poc): https://github.com/MichaelVenturella/CVE-2025-6018-6019-PoC - CVE-2025-6018 + CVE-2025-6019 Privilege Escalation Exploit (github_poc): https://github.com/muyuanlove/CVE-2025-6018-CVE-2025-6019-Privilege-Escalation-Exploit - Exploit for CVE-2025-6019 (github_poc): https://github.com/dreysanox/CVE-2025-6018_Poc - CVE-2025-6018 CVE-2025-6019 PoC Exploit - Local Privilege Escalation in openSUSE/SUSE Linux Enterprise 15 - PAM bypass + udisks2 XFS race condition LPE to root (github_poc): https://github.com/DesertDemons/CVE-2025-6018-6019 - Exploit Chain of CVE-2025-6018 to CVE-2025-6019 (github_poc): https://github.com/0rionCollector/Exploit-Chain-CVE-2025-6018-6019 - Auto exploit for CVE-2025-6018 & CVE-2025-6019 based on https://github.com/0rionCollector/Exploit-Chain-CVE-2025-6018-6019 (github_poc): https://github.com/Goultarde/CVE-2025-6018_CVE-2025-6019_autopwn ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-6018 and fix it if it is affected. What it is: CVE-2025-6018 is a high-severity vulnerability in Red Hat Enterprise Linux 7, published on 23 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6018 exists. Affected product: Red Hat Enterprise Linux 7. 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-6018/ (Markdown: https://insights.sbomify.com/CVE-2025-6018/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6018 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6018 - OSV: https://osv.dev/vulnerability/CVE-2025-6018 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-6018/ Summaries are generated and may contain mistakes; the official description above is the record.