---
id: CVE-2024-43882
title: |-
  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 t…
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 t…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-367
vendor: linux
product: linux_kernel
affected:
  - linux_kernel < 4.19.320
  - 'linux_kernel >= 4.20, < 5.4.282'
  - 'linux_kernel >= 5.5, < 5.10.224'
  - 'linux_kernel >= 5.11, < 5.15.165'
  - 'linux_kernel >= 5.16, < 6.1.106'
  - 'linux_kernel >= 6.2, < 6.6.47'
  - 'linux_kernel >= 6.7, < 6.10.6'
  - linux_kernel = 6.11
patched:
  - linux_kernel 6.10.6
published: '2024-08-21'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T01:18:48.850'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2024-43882'
references:
  - url: 'https://git.kernel.org/stable/c/15469d46ba34559bfe7e3de6659115778c624759'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/368f6985d46657b8b466a421dddcacd4051f7ada'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/9b424c5d4130d56312e2a3be17efb0928fec4d64'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d2a2a4714d80d09b0f8eb6438ab4224690b7121e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d5c3c7e26275a2d83b894d30f7582a42853a958f'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f50733b45d865f91db90919f8311e2127ce5a0cb'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f6cfc6bcfd5e1cf76115b6450516ea4c99897ae1'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-265688.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-355557.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-613116.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.00242
epssPercentile: 0.15282
ingestedAt: '2026-10-15T03:30:12.736Z'
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2024-12-10T04:55:56.573367Z'
---

## Overview

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

- `linux_kernel < 4.19.320`
- `linux_kernel >= 4.20, < 5.4.282`
- `linux_kernel >= 5.5, < 5.10.224`
- `linux_kernel >= 5.11, < 5.15.165`
- `linux_kernel >= 5.16, < 6.1.106`
- `linux_kernel >= 6.2, < 6.6.47`
- `linux_kernel >= 6.7, < 6.10.6`
- `linux_kernel = 6.11`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.10.6`