CVE-2026-25704
Received Received - Intake
TOCTOU Race Condition in cosmic-greeter Enables Privilege Escalation

Publication date: 2026-03-30

Last updated on: 2026-04-16

Assigner: SUSE

Description
A Privilege Dropping / Lowering Errors/Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability inΒ  cosmic-greeter can allow an attacker to regain privileges that should have been dropped and abuse them in the racy checking logic. This issue affects cosmic-greeter before https://github.Com/pop-os/cosmic-greeter/pull/426.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-30
Last Modified
2026-04-16
Generated
2026-05-07
AI Q&A
2026-03-30
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
pop-os cosmic-greeter *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-271 The product does not drop privileges before passing control of a resource to an actor that does not have those privileges.
CWE-367 The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-25704 is a security vulnerability in the cosmic-greeter D-Bus service, which is part of the cosmic-greeter package used in openSUSE Tumbleweed. The service attempts to drop privileges when processing user configuration files by changing the effective user ID, but it does not fully drop privileges because the group ID remains as root. This incomplete privilege dropping combined with a race condition known as Time-of-check to Time-of-use (TOCTOU) allows an attacker to exploit the racy checking logic to regain higher privileges than intended.

Specifically, the vulnerability arises because the service performs file system operations on user configuration files with root group privileges still active, and the TOCTOU race condition creates a window for attacks such as symlink manipulation or Denial-of-Service (DoS). Exploitation requires invoking a vulnerable D-Bus method by an authorized user, and the issue is categorized under privilege dropping errors and TOCTOU race conditions.


How can this vulnerability impact me? :

This vulnerability can allow an attacker with local access and membership in the 'greeter' group to regain elevated privileges that should have been dropped, potentially leading to unauthorized access or control over system resources.

The incomplete privilege dropping combined with the TOCTOU race condition can be exploited to perform actions such as symlink attacks or Denial-of-Service (DoS), which may compromise system integrity and availability.

However, exploitation complexity is high and requires local access with specific permissions, somewhat limiting the risk to authorized users invoking the vulnerable D-Bus method.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves the cosmic-greeter D-Bus service, which is accessible only to members of the "greeter" group and exposes the method com.system76.CosmicGreeter.GetUserData. Detection can focus on monitoring the usage of this D-Bus method and inspecting the privilege dropping behavior of the service.

One approach is to trace system calls related to privilege changes and file operations in the cosmic-greeter process, such as statx, mkdir, openat, and setresuid, to identify incomplete privilege dropping and TOCTOU race conditions.

Suggested commands include using strace to monitor the cosmic-greeter process for suspicious system calls and privilege changes:

  • sudo strace -p $(pidof cosmic-greeter) -e trace=statx,mkdir,openat,setresuid
  • dbus-monitor "type='method_call',interface='com.system76.CosmicGreeter'"

Additionally, checking group membership and effective user/group IDs of the cosmic-greeter process can help detect incomplete privilege dropping:

  • ps -o pid,user,group,euid,egid,cmd -C cosmic-greeter

What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting access to the cosmic-greeter D-Bus service by limiting membership of the "greeter" group to trusted users only.

Since the vulnerability arises from incomplete privilege dropping (only effective user ID is changed, but group ID remains root), applying any available upstream patches or updates that improve privilege dropping is critical.

If patches are not yet available, consider temporarily disabling or restricting the cosmic-greeter service to prevent exploitation.

Monitoring and logging usage of the vulnerable D-Bus method can also help detect potential exploitation attempts.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart