kernel/fork: clear PF_BLOCK_TS in copy_process()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
kernel/fork: clear PF_BLOCK_TS in copy_process()
PF_BLOCK_TS is only set in blk_time_get_ns() when current->plug is non-NULL, and blk_finish_plug() clears it via __blk_flush_plug() before NULLing the plug pointer. copy_process() breaks the invariant by inheriting PF_BLOCK_TS from the parent while resetting the child's plug to NULL.
Clear PF_BLOCK_TS alongside that assignment so callers can rely on "PF_BLOCK_TS set implies current->plug != NULL" and dereference current->plug unguarded.
From the CVE record · Linux
The Linux kernel can leave PF_BLOCK_TS set in a child process while resetting the child’s plug pointer to NULL. Code that relies on the flag to dereference that pointer can then encounter a null pointer dereference. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running the Linux kernel should check their versions; affected versions are not specified.