🛡️ UBUNTU-CVE-2024-43882
⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

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.

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2024-08-21
Updated 2026-06-15
Modified 2026-06-08
Fix URL N/A

Affected Packages

Software From version Fixed in
linux 6.8.0-49.49
linux-allwinner-5.19
linux-aws 6.8.0-1019.21
linux-aws-5.0
linux-aws-5.11
linux-aws-5.13
linux-aws-5.15 5.15.0-1072.78~20.04.1
linux-aws-5.19
linux-aws-5.3
linux-aws-5.4 5.4.0-1135.145~18.04.1
linux-aws-5.8
linux-aws-6.2
linux-aws-6.5
linux-aws-6.8 6.8.0-1019.21~22.04.1
linux-aws-fips 5.15.0-1072.78+fips1
linux-aws-hwe 4.15.0-1175.188~16.04.1
linux-azure 6.8.0-1018.21
linux-azure-4.15 4.15.0-1183.198
linux-azure-5.11
linux-azure-5.13
linux-azure-5.15 5.15.0-1078.87~20.04.1
linux-azure-5.19
linux-azure-5.3
linux-azure-5.4 5.4.0-1140.147~18.04.1
linux-azure-5.8
linux-azure-6.2
linux-azure-6.5
linux-azure-6.8 6.8.0-1018.21~22.04.1
linux-azure-edge
linux-azure-fde
linux-azure-fde-5.19
linux-azure-fde-6.2
linux-azure-fips 5.15.0-1075.84+fips1
linux-bluefield
linux-fips 6.8.0-78.78+fips1
linux-gcp 6.8.0-1018.20
linux-gcp-4.15 4.15.0-1168.185
linux-gcp-5.11
linux-gcp-5.13
linux-gcp-5.15 5.15.0-1071.79~20.04.1
linux-gcp-5.19
linux-gcp-5.3
linux-gcp-5.4 5.4.0-1139.148~18.04.1
linux-gcp-5.8
linux-gcp-6.2
linux-gcp-6.5
linux-gcp-6.8 6.8.0-1018.20~22.04.1
linux-gcp-fips 5.15.0-1071.79+fips1
linux-gke 6.8.0-1014.18
linux-gke-4.15
linux-gke-5.15
linux-gke-5.4
linux-gkeop 6.8.0-1002.4
linux-gkeop-5.15 5.15.0-1055.62~20.04.1
linux-gkeop-5.4
linux-hwe
linux-hwe-5.11
linux-hwe-5.13
linux-hwe-5.15 5.15.0-125.135~20.04.1
linux-hwe-5.19
linux-hwe-5.4 5.4.0-200.220~18.04.1
linux-hwe-5.8
linux-hwe-6.2
linux-hwe-6.5
linux-hwe-6.8 6.8.0-49.49~22.04.1
linux-hwe-edge
linux-ibm 6.8.0-1016.16
linux-ibm-5.15 5.15.0-1065.68~20.04.1
linux-ibm-5.4 5.4.0-1082.87~18.04.1
linux-ibm-6.8 6.8.0-1016.16~22.04.1
linux-intel-5.13
linux-intel-iot-realtime 5.15.0-1066.68
linux-intel-iotg 5.15.0-1067.73
linux-intel-iotg-5.15 5.15.0-1067.73~20.04.1
linux-iot 5.4.0-1044.45
linux-kvm 5.15.0-1069.74
linux-lowlatency 6.8.0-49.49.1
linux-lowlatency-hwe-5.15 5.15.0-125.135~20.04.1
linux-lowlatency-hwe-5.19
linux-lowlatency-hwe-6.2
linux-lowlatency-hwe-6.5
linux-lowlatency-hwe-6.8 6.8.0-49.49.1~22.04.1
linux-lts-xenial 4.4.0-261.295~14.04.1
linux-nvidia 6.8.0-1018.20
linux-nvidia-6.2
linux-nvidia-6.5
linux-nvidia-6.8 6.8.0-1018.20~22.04.1
linux-nvidia-lowlatency 6.8.0-1018.20.1
linux-nvidia-tegra 5.15.0-1032.32
linux-nvidia-tegra-5.15 5.15.0-1032.32~20.04.1
linux-nvidia-tegra-igx 5.15.0-1020.20
linux-oem
linux-oem-5.10
linux-oem-5.13
linux-oem-5.14
linux-oem-5.17
linux-oem-5.6
linux-oem-6.0
linux-oem-6.1
linux-oem-6.5
linux-oem-6.8 6.8.0-1017.17
linux-oracle 6.8.0-1016.17
linux-oracle-5.0
linux-oracle-5.11
linux-oracle-5.13
linux-oracle-5.15 5.15.0-1070.76~20.04.1
linux-oracle-5.3
linux-oracle-5.4 5.4.0-1134.143~18.04.1
linux-oracle-5.8
linux-oracle-6.5
linux-oracle-6.8 6.8.0-1016.17~22.04.1
linux-raspi 6.8.0-1015.17
linux-raspi-5.4 5.4.0-1119.131~18.04.1
linux-raspi-realtime 6.8.0-2014.15
linux-raspi2
linux-realtime 6.8.1-1012.12
linux-realtime-6.8 6.8.1-1012.12~22.04.1
linux-riscv 6.8.0-49.49.1
linux-riscv-5.11
linux-riscv-5.15 5.15.0-1068.72~20.04.1
linux-riscv-5.19
linux-riscv-5.8
linux-riscv-6.5
linux-riscv-6.8 6.8.0-49.49.1~22.04.1
linux-starfive-5.19
linux-starfive-6.2
linux-starfive-6.5
linux-xilinx 6.8.0-1017.18
linux-xilinx-zynqmp 5.15.0-1038.42

References

Similar Threats

Patch Gap Protection

Running software with known vulnerabilities?

BotEraser can help reduce exposure by blocking IPs associated with exploit activity — even before a patch is available.

Start Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.