VYPR
Unrated severityNVD Advisory· Published Feb 17, 2022· Updated Aug 4, 2024

snapd could be made to escalate privileges and run programs as administrator

CVE-2021-44731

Description

A race condition in snap-confine allows a local attacker to gain root privileges by bind-mounting arbitrary content into a snap's private mount namespace.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A race condition in snap-confine allows a local attacker to gain root privileges by bind-mounting arbitrary content into a snap's private mount namespace.

Vulnerability

A race condition exists in the snap-confine binary (version 2.54.2) when preparing a private mount namespace for a snap. Specifically, during the execution of setup_private_mount(), an attacker can exploit a time-of-check-time-of-use (TOCTOU) flaw to bind-mount their own contents inside the snap's private mount namespace. This affects snapd versions prior to 2.54.3 on Ubuntu 18.04, 20.04, and 21.10 [3][4].

Exploitation

A local attacker with the ability to create a bind mount during the race window can cause snap-confine to execute arbitrary code. The attacker must be able to trigger the race condition by manipulating the filesystem while snap-confine is setting up the mount namespace. No special privileges beyond local access are required [4].

Impact

Successful exploitation allows the attacker to execute arbitrary code as root, resulting in full privilege escalation and compromise of the system. The attacker gains complete control over the affected host [3][4].

Mitigation

The vulnerability is fixed in snapd versions 2.54.3+18.04, 2.54.3+20.04, and 2.54.3+21.10.1. Users should update snapd to the latest version via their package manager. No workaround is available [4].

AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

10

News mentions

0

No linked articles in our index yet.