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-2026-98388exec: do_close_on_exec() before taking exec_update_lock

Description

In the Linux kernel, the following vulnerability has been resolved: exec: do_close_on_exec() before taking exec_update_lock do_close_on_exec() currently happens while holding the exec_update_lock, which is used in a lot of places that access process state to synchronize access checks. I recently added another such use of exec_update_lock, causing a regression. do_close_on_exec() can block waiting for a reply from a filesystem. That means a hung filesystem can block codepaths that use exec_update_lock; and it also means that a FUSE filesystem which attempts to inspect the calling process can deadlock. To avoid such problems, move do_close_on_exec() before the exec_update_lock is taken, but after the FD table has been copied if necessary. I have looked through all the calls between the old and new position of the do_close_on_exec() call; there seems to be no file descriptor table access in between.

Timeline

  1. ID reserved

    By Linux

  2. · 19 days later

    Published

  3. · 5 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected ae1e630bcaac739f625822078edbaea98366930d – < 955973fff4a36d39a848b00cac1706863f568fe1
    • affected d54f14655fd7d7b293698a8b6918563c4c0465e7 – < 550feab5b01000ab314868b62211fb3ddfd600e8
    • affected bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9 – < 5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38
    • affected 7456ae990a9738962b33146916fabca62ae3d4e0 – < 3feb4020bfb7ccf0d347f27051639d25e19cd65d
    • affected 4bfe8c481846cee52473a2f7d7b30ee8e6749fc4 – < 0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53
    • affected f9b4b03ccc9c69bf7f7298d4559906ebea7143b3 – < 19ddef61ee0a49782a60f8f497e50597ad5de2da
    • affected 6650527444dadc63d84aa939d14ecba4fadb2f69 – < 63be3d8511bdafa095cd14a393cbf3c58dbbb928
    • affected 6650527444dadc63d84aa939d14ecba4fadb2f69 – < e780259b54e618ceb4763fbc21314acf3565e813
    • affected c1cfd63326f5d09999134e9052c353faf738286e
    • affected 5.10.261 – < 5.10.271
    • affected 5.15.212 – < 5.15.222
    • affected 6.1.178 – < 6.1.189
    • affected 6.6.145 – < 6.6.158
    • affected 6.12.97 – < 6.12.111
    • affected 6.18.40 – < 6.18.53
    • affected 7.1.4 – < 7.2
  • Linux · Linux

    • affected 7.2
    • unaffected < 7.2
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .