futex: Also allocate private hash on vfork()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
futex: Also allocate private hash on vfork()
As Jann demonstrated, it is entirely feasible to access the mm through vfork(). Therefore we need to allocate a private hash on vfork() as well as any other CLONE_VM user.
Specifically, it must be avoided to have (private) futex waiters before allocating the private hash.
From the CVE record · Linux
The Linux kernel can have private futex waiters before it allocates a private hash during vfork(). A local process using vfork() can access the shared memory context; the input does not specify a further attacker outcome.
Engineers running Linux kernels should check whether their version is affected; no affected versions are specified.