CVE-2026-98388: Linux

EPSS: 0.2% probability of exploitation activity in the next 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.

What to do

The record states a fixed version for each range of affected versions. Update to the one for the range your version is in: a later release on another branch may not have the fix.

  • Linux, from 5.10.261, before 5.10.271: fixed in 5.10.271
  • Linux, from 5.15.212, before 5.15.222: fixed in 5.15.222
  • Linux, from 6.1.178, before 6.1.189: fixed in 6.1.189
  • Linux, from 6.6.145, before 6.6.158: fixed in 6.6.158
  • Linux, from 6.12.97, before 6.12.111: fixed in 6.12.111
  • Linux, from 6.18.40, before 6.18.53: fixed in 6.18.53
  • Linux, from 7.1.4, before 7.2: fixed in 7.2
  • Linux, from 7.2, before 7.2.7: fixed in 7.2.7

Affected products

  • Linux Linux: from 5.10.261, before 5.10.271 (fixed in 5.10.271); from 5.15.212, before 5.15.222 (fixed in 5.15.222); from 6.1.178, before 6.1.189 (fixed in 6.1.189); from 6.6.145, before 6.6.158 (fixed in 6.6.158); from 6.12.97, before 6.12.111 (fixed in 6.12.111); from 6.18.40, before 6.18.53 (fixed in 6.18.53); …

Published 2026-10-14. Last modified 2026-10-19.