boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Wednesday, August 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2024-43882HIGH
Linux Linux — exec: Fix ToCToU between perm check and set-uid/gid usage
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   L   H   L   N  U  H  H  H    7.0   .0024   15.7     —
AFFECTED
  Product  Versions                                    Fixed
  Linux    9167b0b9a0ab7907191523f5a0528e3b9c288e21 –  —
  Linux    2.6.18 –                                    4.19.320
TIMELINE
  Aug 17  Reserved by Linux
  Aug 21  Published (CNA: Linux)
  Aug 4   RESCORED — CVE-2024-43882 (Linux). CVSS 7.8 → 7 (NVD).
CWE-367 · CNA: Linux · CVSS v3.1 · 13 references · NVD status: Modified

Description

In the Linux kernel, the following vulnerability has been resolved: exec: Fix ToCToU between perm check and set-uid/gid usage When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges. For example, if a file could change permissions from executable and not set-id: ---------x 1 root root 16048 Aug 7 13:16 target to set-id and non-executable: ---S------ 1 root root 16048 Aug 7 13:16 target it is possible to gain root privileges when execution should have been disallowed. While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating the setuid bits of installed programs. Such files start with being world-executable but then are adjusted to be group-exec with a set-uid bit. For example, "chmod o-x,u+s target" makes "target" executable only by uid "root" and gid "cdrom", while also becoming setuid-root: -rwxr-xr-x 1 root cdrom 16048 Aug 7 13:16 target becomes: -rwsr-xr-- 1 root cdrom 16048 Aug 7 13:16 target But racing the chmod means users without group "cdrom" membership can get the permission to execute "target" just before the chmod, and when the chmod finishes, the exec reaches brpm_fill_uid(), and performs the setuid to root, violating the expressed authorization of "only cdrom group members can setuid to root". Re-check that we still have execute permissions in case the metadata has changed. It would be better to keep a copy from the perm-check time, but until we can do that refactoring, the least-bad option is to do a full inode_permission() call (under inode lock). It is understood that this is safe against dead-locks, but hardly optimal.

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
August 17, 2024ReservedReserved by Linux
August 21, 2024PublishedPublished (CNA: Linux)
August 4, 2026RESCOREDRESCORED — CVE-2024-43882 (Linux). CVSS 7.8 → 7 (NVD).

Affected

Affected products and packages — 2 rows
VendorProduct / PackageEcosystemVersion introducedFixed
LinuxLinux9167b0b9a0ab7907191523f5a0528e3b9c288e21
LinuxLinux2.6.184.19.320

Weaknesses

CWE-367

References (13)

Related

Authoritative record: CVE-2024-43882 at cve.org

Vendors: linux

Weaknesses: CWE-367

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2024-43882 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Wednesday, August 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.