aio: fix mremap after fork null-deref
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e4a0d3e720e7e508749c1439b5ba3aff56c92976 · < af126acf01a12bdb04986fd26fc2eb3b40249e0d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
aio: fix mremap after fork null-deref
Commit e4a0d3e720e7 ("aio: Make it possible to remap aio ring") introduced a null-deref if mremap is called on an old aio mapping after fork as mm->ioctx_table will be set to NULL.
[jmoyer@redhat.com: fix 80 column issue]
From the CVE record · Linux
The Linux kernel's aio code can dereference a null pointer when mremap is called on an old aio mapping after fork. A local process can trigger this condition; the input does not specify authentication requirements or whether another user's interaction is needed.
Anyone running the Linux kernel should check whether their kernel includes the affected aio code; affected versions are not specified.