In snapd versions prior to 2.62, snapd failed to properly check the file
nvd · CVE-2024-29068 · Published
No access to your tenant or devices. Every item links to its source. What this means
Historical advisory recorded 24 Oct 2026 23:17:34 UTC. Read the latest advisory.
In snapd versions prior to 2.62, snapd failed to properly check the file type when extracting a snap. The snap format is a squashfs file-system image and so can contain files that are non-regular files (such as pipes or sockets etc). Various file entries within the snap squashfs image (such as icons etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained non-regular files at these paths could then cause snapd to block indefinitely trying to read from such files and cause a denial of service.
Read the publisher's advisorySee how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
nvd · CVE-2024-29068 · Published
This historical link shows only this version and versions saved before it. Browse all advisory history.