CVE-2024-43882: exec: Fix ToCToU between perm check and set-uid/gid usage
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 15469d46ba34559bfe7e3de6659115778c624759, 368f6985d46657b8b466a421dddcacd4051f7ada, 90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3e.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 15469d46ba34559bfe7e3de6659115778c624759, 368f6985d46657b8b466a421dddcacd4051f7ada, 90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3e or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 21, 2024
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-367
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.0
- CNA · Linux
- 7.8
- 0.8 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.19.320
- linux linux kernel4.20 and later · before 5.4.282
- linux linux kernel5.5 and later · before 5.10.224
- linux linux kernel5.11 and later · before 5.15.165
- linux linux kernel5.16 and later · before 6.1.106
- linux linux kernel6.2 and later · before 6.6.47
- linux linux kernel6.7 and later · before 6.10.6
- linux linux kernel6.11
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.18affected
- 9167b0b9a0ab7907191523f5a0528e3b9c288e21 and later · before d5c3c7e26275a2d83b894d30f7582a42853a958faffected · git
- 9167b0b9a0ab7907191523f5a0528e3b9c288e21 and later · before 368f6985d46657b8b466a421dddcacd4051f7adaaffected · git
- 9167b0b9a0ab7907191523f5a0528e3b9c288e21 and later · before 15469d46ba34559bfe7e3de6659115778c624759affected · git
- 9167b0b9a0ab7907191523f5a0528e3b9c288e21 and later · before 9b424c5d4130d56312e2a3be17efb0928fec4d64affected · git
- 9167b0b9a0ab7907191523f5a0528e3b9c288e21 and later · before f6cfc6bcfd5e1cf76115b6450516ea4c99897ae1affected · git
- 9167b0b9a0ab7907191523f5a0528e3b9c288e21 and later · before d2a2a4714d80d09b0f8eb6438ab4224690b7121eaffected · git
- 9167b0b9a0ab7907191523f5a0528e3b9c288e21 and later · before 90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3eaffected · git
- 9167b0b9a0ab7907191523f5a0528e3b9c288e21 and later · before f50733b45d865f91db90919f8311e2127ce5a0cbaffected · git
- before 2.6.18not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.106-1 | 6.1.106-1 |
| Debian:13 | linux | before 6.10.6-1 | 6.10.6-1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_56 | before 16-2.1 | 16-2.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_59 | before 10-2.1 | 10-2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_43 | before 18-150300.2.2 | 18-150300.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_44 | before 17-150300.2.2 | 17-150300.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_45 | before 14-150300.2.2 | 14-150300.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_25 | before 18-150400.2.2 | 18-150400.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_26 | before 17-150400.2.2 | 17-150400.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_28 | before 12-150400.2.2 | 12-150400.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_12 | before 18-150500.2.2 | 18-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_13 | before 16-150500.2.2 | 16-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_15 | before 15-150500.2.2 | 15-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_17 | before 10-150500.2.2 | 10-150500.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_1 | before 14-150600.2.2 | 14-150600.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_3 | before 14-150600.2.2 | 14-150600.2.2 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_0 | before 15-150600.3.1 | 15-150600.3.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-default | before 3.0.101-108.162.1 | 3.0.101-108.162.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-ec2 | before 3.0.101-108.162.1 | 3.0.101-108.162.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-source | before 3.0.101-108.162.1 | 3.0.101-108.162.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-syms | before 3.0.101-108.162.1 | 3.0.101-108.162.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-trace | before 3.0.101-108.162.1 | 3.0.101-108.162.1 |
| SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | kernel-xen | before 3.0.101-108.162.1 | 3.0.101-108.162.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-43871Aug 21, 2024 · devres: Fix memory leakage caused by driver API devm_free_percpu()22Monitor
- ← EarlierCVE-2024-43879Aug 21, 2024 · wifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he()22Monitor
- Later →CVE-2022-48867Aug 21, 2024 · dmaengine: idxd: Prevent use after free on completion memory31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 15469d46ba34559bfe7e3de6659115778c624759 | Vendor (CNA) |
| Linux Linux | 368f6985d46657b8b466a421dddcacd4051f7ada | Vendor (CNA) |
| Linux Linux | 90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3e | Vendor (CNA) |
| Linux Linux | 9b424c5d4130d56312e2a3be17efb0928fec4d64 | Vendor (CNA) |
| Linux Linux | d2a2a4714d80d09b0f8eb6438ab4224690b7121e | Vendor (CNA) |
| Linux Linux | d5c3c7e26275a2d83b894d30f7582a42853a958f | Vendor (CNA) |
| Linux Linux | f50733b45d865f91db90919f8311e2127ce5a0cb | Vendor (CNA) |
| Linux Linux | f6cfc6bcfd5e1cf76115b6450516ea4c99897ae1 | Vendor (CNA) |
| debian:linux | 6.1.106-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-default | 3.0.101-108.162.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-ec2 | 3.0.101-108.162.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_43 | 18-150300.2.2 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_45 | 14-150300.2.2 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5_Update_15 | 15-150500.2.2 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_0 | 15-150600.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-source | 3.0.101-108.162.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-syms | 3.0.101-108.162.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-trace | 3.0.101-108.162.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-xen | 3.0.101-108.162.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_56 | 16-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_59 | 10-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-38352335 days apartposix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()KEV61This week
- CVE-2023-2007485 days apartThe specific flaw exists within the DPT I2O Controller driver.31Monitor
- CVE-2024-5023480 days apartwifi: iwlegacy: Clear stale interrupts before resuming device28Monitor
- CVE-2021-4728092 days apartdrm: Fix use-after-free read in drm_getunique()28Monitor
- CVE-2024-26974112 days apartcrypto: qat - resolve race condition during AER recovery28Monitor
- CVE-2023-1295420 days apartPrivilege escalation with IO_RING_OP_CLOSE in the Linux Kernel28Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1309 · Aug 21, 2024(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (12 more)Show less
- git.kernel.org/stable/c/368f6985d46657b8b466a421dddcacd4051f7ada
- git.kernel.org/stable/c/90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3e
- git.kernel.org/stable/c/9b424c5d4130d56312e2a3be17efb0928fec4d64
- git.kernel.org/stable/c/d2a2a4714d80d09b0f8eb6438ab4224690b7121e
- git.kernel.org/stable/c/d5c3c7e26275a2d83b894d30f7582a42853a958f
- git.kernel.org/stable/c/f50733b45d865f91db90919f8311e2127ce5a0cb
- git.kernel.org/stable/c/f6cfc6bcfd5e1cf76115b6450516ea4c99897ae1
- lists.debian.org/debian-lts-announce/2024/10/msg00003.html
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
- cert-portal.siemens.com/productcert/html/ssa-355557.html
- cert-portal.siemens.com/productcert/html/ssa-613116.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.