cbcvebase.
CVE-2024-43882
published 2024-08-21

CVE-2024-43882: 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…

PriorityP335high7CVSS 3.1
AVLACHPRLUINSUCHIHAH
EPSS
0.24%
15.5th percentile
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

Affected

41 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.106-1 (bookworm)linux 6.1.106-1 (bookworm)
debianlinux-6.1< linux 6.1.106-1 (bookworm)linux 6.1.106-1 (bookworm)
linuxlinux
linuxlinux>= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < d5c3c7e26275a2d83b894d30f7582a42853a958fd5c3c7e26275a2d83b894d30f7582a42853a958f
linuxlinux>= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 368f6985d46657b8b466a421dddcacd4051f7ada368f6985d46657b8b466a421dddcacd4051f7ada
linuxlinux>= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 15469d46ba34559bfe7e3de6659115778c62475915469d46ba34559bfe7e3de6659115778c624759
linuxlinux>= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 9b424c5d4130d56312e2a3be17efb0928fec4d649b424c5d4130d56312e2a3be17efb0928fec4d64
linuxlinux>= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < f6cfc6bcfd5e1cf76115b6450516ea4c99897ae1f6cfc6bcfd5e1cf76115b6450516ea4c99897ae1
linuxlinux>= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < d2a2a4714d80d09b0f8eb6438ab4224690b7121ed2a2a4714d80d09b0f8eb6438ab4224690b7121e
linuxlinux>= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3e90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3e
linuxlinux>= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < f50733b45d865f91db90919f8311e2127ce5a0cbf50733b45d865f91db90919f8311e2127ce5a0cb
linuxlinux_kernel< 4.19.3204.19.320
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.226-15.10.226-1
linuxlinux_kernel>= 0 < 6.1.106-16.1.106-1
linuxlinux_kernel>= 0 < 6.10.6-16.10.6-1
linuxlinux_kernel>= 0 < 6.10.6-16.10.6-1
linuxlinux_kernel>= 0 < 5.4.0-200.2205.4.0-200.220
linuxlinux_kernel>= 0 < 5.15.0-125.1355.15.0-125.135
linuxlinux_kernel>= 0 < 6.8.0-49.496.8.0-49.49
linuxlinux_kernel>= 0 < 4.4.0-261.2954.4.0-261.295
linuxlinux_kernel>= 0 < 4.4.0-267.3014.4.0-267.301
linuxlinux_kernel>= 0 < 4.15.0-233.2454.15.0-233.245
linuxlinux_kernel>= 0 < 4.15.0-232.2444.15.0-232.244
linuxlinux_kernel>= 0 < 4.15.0-231.2434.15.0-231.243

CVSS provenance

nvdv3.17.0HIGHCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
osv8.8HIGH
vendor_ubuntu8.8HIGH
vendor_debian7.0HIGH
vendor_msrc7.0HIGH
vendor_redhat7.0HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.