futex: Require sys_futex_requeue() to have identical flags
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:
futex: Require sys_futex_requeue() to have identical flags
Nicholas reported that his LLM found it was possible to create a UaF when sys_futex_requeue() is used with different flags. The initial motivation for allowing different flags was the variable sized futex, but since that hasn't been merged (yet), simply mandate the flags are identical, as is the case for the old style sys_futex() requeue operations.
From the CVE record · Linux
The Linux kernel’s sys_futex_requeue() can trigger a use-after-free when called with different flags. A local caller can trigger the flaw by using mismatched flags; the input does not specify any further access requirements or user interaction.
Engineers running Linux kernels should check whether their kernel includes the futex requeue fix; affected versions were not specified.