CVE-2026-98388

exec: do_close_on_exec() before taking exec_update_lock

N/A
Published: October 14, 2026 at 01:25 PM UTC
Updated: October 19, 2026 at 10:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4bfe8c481846cee52473a2f7d7b30ee8e6749fc45.10.2615.15.2126.1.1786.12.976.18.406.6.1456650527444dadc63d84aa939d14ecba4fadb2f697.1.47.27456ae990a9738962b33146916fabca62ae3d4e0ae1e630bcaac739f625822078edbaea98366930dbb43679356f1f2a4c6b1c88aec4f021e5b5c74e9c1cfd63326f5d09999134e9052c353faf738286ed54f14655fd7d7b293698a8b6918563c4c0465e7f9b4b03ccc9c69bf7f7298d4559906ebea7143b3
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card