Not yet scoredPublished Oct 14, 2026

CVE-2026-98388exec: do_close_on_exec() before taking exec_update_lock

Updated under an hour ago (Oct 27, 2026, 4:10 AM ET)

Does this affect you?

It affects Linux. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: Not yet scored
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Received
Record last updated: Oct 19, 2026
First seen by InfoSec Signals: Oct 14, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from ae1e630bcaac739f625822078edbaea98366930d before 955973fff4a36d39a848b00cac1706863f568fe1; from d54f14655fd7d7b293698a8b6918563c4c0465e7 before 550feab5b01000ab314868b62211fb3ddfd600e8; from bb43679356f1f2a4c6b1c88aec4f021e5b5c74e9 before 5aacc19ba2b1faf84c4a2f2cf9a1784e03d1ff38; 7456ae990a9738962b33146916fabca62ae3d4e0 builds before 3feb4020bfb7ccf0d347f27051639d25e19cd65d; 4bfe8c481846cee52473a2f7d7b30ee8e6749fc4 builds before 0d86cd6b709c39216e6ee5ea8f0fc4242bbb2b53; from f9b4b03ccc9c69bf7f7298d4559906ebea7143b3 before 19ddef61ee0a49782a60f8f497e50597ad5de2da; 6650527444dadc63d84aa939d14ecba4fadb2f69 builds before 63be3d8511bdafa095cd14a393cbf3c58dbbb928; from 6650527444dadc63d84aa939d14ecba4fadb2f69 before e780259b54e618ceb4763fbc21314acf3565e813; and 8 more ranges	CNA record

References

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

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.