CVE-2024-43882

Summary

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.

Affected Software

VendorProductVersion RangeStatus
LinuxLinux9167b0b9a0ab7907191523f5a0528e3b9c288e21 < d5c3c7e26275a2d83b894d30f7582a42853a958faffected
LinuxLinux9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 368f6985d46657b8b466a421dddcacd4051f7adaaffected
LinuxLinux9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 15469d46ba34559bfe7e3de6659115778c624759affected
LinuxLinux9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 9b424c5d4130d56312e2a3be17efb0928fec4d64affected
LinuxLinux9167b0b9a0ab7907191523f5a0528e3b9c288e21 < f6cfc6bcfd5e1cf76115b6450516ea4c99897ae1affected
LinuxLinux9167b0b9a0ab7907191523f5a0528e3b9c288e21 < d2a2a4714d80d09b0f8eb6438ab4224690b7121eaffected
LinuxLinux9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3eaffected
LinuxLinux9167b0b9a0ab7907191523f5a0528e3b9c288e21 < f50733b45d865f91db90919f8311e2127ce5a0cbaffected
LinuxLinux2.6.18affected
LinuxLinux0 < 2.6.18unaffected
LinuxLinux4.19.320 <= 4.19.*unaffected
LinuxLinux5.4.282 <= 5.4.*unaffected
LinuxLinux5.10.224 <= 5.10.*unaffected
LinuxLinux5.15.165 <= 5.15.*unaffected
LinuxLinux6.1.106 <= 6.1.*unaffected
LinuxLinux6.6.47 <= 6.6.*unaffected
LinuxLinux6.10.6 <= 6.10.*unaffected
LinuxLinux6.11 <= *unaffected

Weaknesses

ADP Enrichment

CISA ADP Vulnrichment

  • SSVC:
  • Exploitation: none
    • Automatable: no
    • Technical Impact: total

CVE Program Container

Additional References

Additional References

References