CVE-2024-50010
Last modified
CVE-2024-50010 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: exec: don't WARN for racy path_noexec check Both i_mode and noexec checks wrapped in WARN_ON stem from an artifact of the previous implementation. They used to legitimately check for the condition, but that got moved up in two commits: 633fb6ac3980 ("exec: move S_ISREG() check earlier") 0fd338b2d2cd ("exec: move path_noexec() check earlier") Instead of being removed said checks are WARN_ON'ed instead, which has some debug value. However, the spurious path_noexec check is racy, resulting in unwarranted warnings should someone race with setting the noexec flag. One can note there is more to perm-checking whether execve is allowed and none of the conditions are guaranteed to still hold after they were tested for. Additionally this does not validate whether the code path did any perm checking to begin with -- it will pass if the inode happens to be regular. Keep the redundant path_noexec() check even though it's mindless nonsense checking for guarantee that isn't given so drop the WARN. Reword the commentary and do small tidy ups while here. [brauner: keep redundant path_noexec() check]. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: exec: don't WARN for racy path_noexec check Both i_mode and noexec checks wrapped in WARN_ON stem from an artifact of the previous implementation. They used to legitimately check for the condition, but that got moved up in two commits: 633fb6ac3980 ("exec: move S_ISREG() check earlier") 0fd338b2d2cd ("exec: move path_noexec() check earlier") Instead of being removed said checks are WARN_ON'ed instead, which has some debug value. However, the spurious path_noexec check is racy, resulting in unwarranted warnings should someone race with setting the noexec flag. One can note there is more to perm-checking whether execve is allowed and none of the conditions are guaranteed to still hold after they were tested for. Additionally this does not validate whether the code path did any perm checking to begin with -- it will pass if the inode happens to be regular. Keep the redundant path_noexec() check even though it's mindless nonsense checking for guarantee that isn't given so drop the WARN. Reword the commentary and do small tidy ups while here. [brauner: keep redundant path_noexec() check]
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 6.11.3 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-50010?
How severe is CVE-2024-50010?
How do I fix CVE-2024-50010?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-50005In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-50006In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-50007In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-50008In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50009In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5001The Image Hover Effects for Elementor with Lightbox and Flip…5.4
- CVE-2024-50011In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50012In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50013In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50014In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50015In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50016Rejected reason: This CVE ID has been rejected or withdrawn …
Are you affected by CVE-2024-50010?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
