CVE-2025-6018: Suse Pam-config broken access control (CVSS 7.8)

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.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Suse Pam-config1.1.8-24.71.1

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://access.redhat.com/security/cve/CVE-2025-6018Third Party Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=2372693Issue TrackingThird Party Advisory
https://bugzilla.suse.com/show_bug.cgi?id=1243226ExploitThird Party Advisory
https://cdn2.qualys.com/2025/06/17/suse15-pam-udisks-lpe.txtExploitIssue TrackingThird Party Advisory
http://www.openwall.com/lists/oss-security/2025/08/28/4

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-6018 being actively exploited?

CVE-2025-6018 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.05%.

How severe is CVE-2025-6018?

CVE-2025-6018 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 1.05% probability of exploitation.

Which products are affected by CVE-2025-6018?

Affected products include Suse Pam-config.

How do I fix CVE-2025-6018?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-6018 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo