CVE-2025-6018
gdm: This update for gdm fixes the following issues: - CVE-2025-6018: Removes pam_env from auth stack for security reason...
CVE-2025-6018 is fixed in 4 products on 1 platform, first by SUSE-SU-2025:02003-1, released June 18, 2025. It is not reported as exploited. Patch Radar priority: Routine.
Routine
CVSS
n/a
No vendor severity
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0110
65th percentile
This update for gdm fixes the following issues: - CVE-2025-6018: Removes pam_env from auth stack for security reason (bsc#1243226).
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| gdm · opensuse-leap 15.6 | 45.0.1-150600.6.8.1 | SUSE-SU-2025:02003-1 | Jun 18, 2025 |
| gdm · sles 15.6 | 45.0.1-150600.6.8.1 | SUSE-SU-2025:02003-1 | Jun 18, 2025 |
| gdm · sles 15.7 | 45.0.1-150700.12.5.1 | SUSE-SU-2025:02005-1 | Jun 18, 2025 |
| pam · opensuse-leap 15.6 | 1.3.0-150000.6.83.1 | SUSE-SU-2025:02013-1 | Jun 18, 2025 |
| pam · sles 15.6 | 1.3.0-150000.6.83.1 | SUSE-SU-2025:02013-1 | Jun 18, 2025 |
| pam · sles 15.7 | 1.3.0-150000.6.83.1 | SUSE-SU-2025:02013-1 | Jun 18, 2025 |
| pam-config · opensuse-leap 15.6 | 1.1-150600.16.8.1 | SUSE-SU-2025:02080-1 | Jun 24, 2025 |
| pam-config · sles 15.6 | 1.1-150600.16.8.1 | SUSE-SU-2025:02080-1 | Jun 24, 2025 |
| pam-config · sles 15.7 | 1.1-150600.16.8.1 | SUSE-SU-2025:02080-1 | Jun 24, 2025 |
| pam_pkcs11 · opensuse-leap 15.6 | 0.6.10-150600.16.8.1 | SUSE-SU-2025:02026-1 | Jun 19, 2025 |
| pam_pkcs11 · sles 15.6 | 0.6.10-150600.16.8.1 | SUSE-SU-2025:02026-1 | Jun 19, 2025 |
| pam_pkcs11 · sles 15.7 | 0.6.10-150600.16.8.1 | SUSE-SU-2025:02026-1 | Jun 19, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
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.