exec: do_close_on_exec() before taking exec_update_lock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f9b4b03ccc9c69bf7f7298d4559906ebea7143b3 · < 19ddef61ee0a49782a60f8f497e50597ad5de2da| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel can hold exec_update_lock while closing file descriptors during exec. If a filesystem hangs while responding, other code paths using the lock can block; a FUSE filesystem that inspects the calling process can deadlock. The input does not specify authentication requirements or any required user interaction.
Engineers running the Linux kernel should check their versions; the affected versions are not specified.