Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-50010exec: don't WARN for racy path_noexec check

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]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-50010, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.

Affected products

  • Linux · Linux

    • affected 0fd338b2d2cdf827091ae819ae90ad760b94ad0c – < c9b77438077d5a20c79ead95bcdaf9bd4797baaf
    • affected 0fd338b2d2cdf827091ae819ae90ad760b94ad0c – < b723f96407a0a078cf75970e4dbf16b46d286a61
    • affected 0fd338b2d2cdf827091ae819ae90ad760b94ad0c – < 0bdf77be2330062b3a64f2bec39f62ab874a6796
    • affected 0fd338b2d2cdf827091ae819ae90ad760b94ad0c – < 0d16f53c91111cec914f0811fcc526a2ba77b20d
    • affected 0fd338b2d2cdf827091ae819ae90ad760b94ad0c – < 0d196e7589cefe207d5d41f37a0a28a1fdeeb7c6
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.10.229 – ≤ 5.10.*
    • unaffected 5.15.170 – ≤ 5.15.*
    • unaffected 6.1.115 – ≤ 6.1.*
    • unaffected 6.6.59 – ≤ 6.6.*
    • unaffected 6.12 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-50010 badge
[![CVE-2024-50010](https://cveledger.app/badge/CVE-2024-50010.svg)](https://cveledger.app/cve/CVE-2024-50010)

Record last updated .