Once the attacker gains these elevated permissions, they exploit a race condition in UDisks2 and libblockdev (CVE-2025-6019). This vulnerability occurs during the Filesystem.Resize D-Bus method call, where an attacker can mount a malicious XFS filesystem image containing a SUID root binary. Because the system fails to unmount the filesystem properly after a triggered error, the SUID binary becomes accessible in a temporary directory, allowing the attacker to execute it and obtain a root shell.

Attack Chain

1. Attacker prepares a 300MB XFS filesystem image containing a SUID root bash binary on a local system.
2. Attacker transfers the malicious filesystem image to the target SUSE system, typically placing it in /tmp/.
3. Attacker modifies the local ~/.pam_environment file on the target to include malicious XDG session variables (e.g., XDG_SEAT, XDG_VTNR).
4. Attacker triggers the PAM injection by logging out and logging back into the target system via SSH.
5. The target's systemd-logind processes the malicious environment, elevating the attacker's session status to 'allow_active' within PolicyKit.
6. Attacker initiates the Filesystem.Resize method via D-Bus, targeting the previously uploaded XFS image.
7. The libblockdev component mounts the image but fails to unmount it after the resize operation errors out, leaving the files accessible in /tmp/blockdev*/.
8. Attacker executes the SUID root bash binary found in the temporary mount point to gain root privileges.

Impact

Successful exploitation results in full local privilege escalation, granting an attacker root access on affected SUSE and openSUSE systems. This allows for total system compromise, data exfiltration, and persistence, provided the attacker has already obtained an initial unprivileged user session.

Recommendation

• Prioritize patching SUSE and openSUSE systems by applying official updates that address CVE-2025-6018 and CVE-2025-6019.
• Monitor systems for suspicious creation of ~/.pam_environment files, particularly those containing XDG variable overrides.
• Audit PolicyKit configuration and limit 'allow_active' permissions for standard, non-interactive service accounts.
• Use File Integrity Monitoring (FIM) to detect the presence of SUID binaries in temporary directories like /tmp/.