A flaw was found in linux-pam. The module pam_namespace may use access user-controlled paths without proper protection, allowing local users to elevate their privileges to root via multiple symlink attacks and race conditions.
Security readout for executives and security teams
Plain-English summary
CVE-2025-6020 is a local privilege-escalation flaw in linux-pam’s pam_namespace module. A user who already has local access may be able to gain root privileges through unsafe handling of user-controlled paths. This is not a remote internet-facing bug, but it is serious on shared Linux systems or servers with many local accounts.
Executive priority
Treat as high priority for Linux servers where users can log in locally or through SSH. It is less urgent than a remote unauthenticated flaw, but successful exploitation could give full root control. Patch affected RHEL systems through standard emergency or accelerated Linux maintenance windows.
Technical view
The flaw is described as directory traversal in linux-pam pam_namespace, involving access to user-controlled paths without proper protection. The CVE notes multiple symlink attacks and race conditions that can allow local users to elevate privileges to root. CVSS 3.1 is 7.8, with local attack vector, low complexity, low privileges, and high confidentiality, integrity, and availability impact.
Likely exposure
Confirmed affected packages are Red Hat pam builds across RHEL 7 ELS, RHEL 8, RHEL 9, RHEL 10, and several EUS/AUS/E4S/TUS/SAP channels listed in the source bundle. Exposure requires a local user account and likely depends on pam_namespace being present or used in the authentication/session stack.
Exploitation context
Sources do not show CISA KEV listing or active exploitation. The vulnerability is locally exploitable after an attacker has some account or code execution on the host. Risk is higher on multi-user systems, developer servers, jump hosts, shared compute, and systems where untrusted users can log in.
Researcher notes
The public bundle identifies CWE-22 and describes symlink/race-condition abuse, but does not provide detailed preconditions, proof-of-concept status, or distribution-wide impact beyond listed Red Hat packages. Avoid assuming active exploitation. Validate exposure by package version and pam_namespace configuration rather than CVE presence alone.
Mitigation direction
Apply the relevant Red Hat RHSA update for each affected RHEL channel.
Prioritize hosts with local users, shared access, or exposed login services.
Check vendor guidance for non-Red Hat linux-pam distributions.
Review whether pam_namespace is required in your PAM configuration.
Validation and detection
Inventory installed pam or linux-pam package versions across Linux assets.
Compare versions against the affected Red Hat package list and advisories.
Identify systems using pam_namespace in PAM session configuration.
Confirm remediation by verifying updated vendor package versions after patching.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
3ADP providers
32Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.