CVE-2026-98388

Unknown

Last modified

CVE-2026-98388 is a vulnerability of currently unknown severity. 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..

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ae1e630bcaac739f625822078edbaea98366930d, < 955973fff4a36d39a848b00cac1706863f568fe1; >= d54f14655fd7d7b293698a8b6918563c4c0465e7, < 550feab5b01000ab314868b62211fb3ddfd600e8; >= bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9, < 5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38; >= 7456ae990a9738962b33146916fabca62ae3d4e0, < 3feb4020bfb7ccf0d347f27051639d25e19cd65d; >= 4bfe8c481846cee52473a2f7d7b30ee8e6749fc4, < 0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53; >= f9b4b03ccc9c69bf7f7298d4559906ebea7143b3, < 19ddef61ee0a49782a60f8f497e50597ad5de2da; >= 6650527444dadc63d84aa939d14ecba4fadb2f69, < 63be3d8511bdafa095cd14a393cbf3c58dbbb928; >= 6650527444dadc63d84aa939d14ecba4fadb2f69, < e780259b54e618ceb4763fbc21314acf3565e813; c1cfd63326f5d09999134e9052c353faf738286e; >= 5.10.261, < 5.10.271; >= 5.15.212, < 5.15.222; >= 6.1.178, < 6.1.189; >= 6.6.145, < 6.6.158; >= 6.12.97, < 6.12.111; >= 6.18.40, < 6.18.53; >= 7.1.4, < 7.2
LinuxLinux7.2

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98388?
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.
How severe is CVE-2026-98388?
Severity scoring for CVE-2026-98388 is pending analysis.
How do I fix CVE-2026-98388?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98388?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST