aio: fix mremap after fork null-deref
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 178993157e8c50aef7f35d7d6d3b44bb428199e1, Kernel 4326d0080f7e84fba775da41d158f46cf9d3f1c2, Kernel 808f1e4b5723ae4eda724d2ad6f6638905eefd95 and 4 more.
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]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.19, >=e4a0d3e720e7e508749c1439b5ba3aff56c92976 <178993157e8c50aef7f35d7d6d3b44bb428199e1, >=e4a0d3e720e7e508749c1439b5ba3aff56c92976 <4326d0080f7e84fba775da41d158f46cf9d3f1c2, >=e4a0d3e720e7e508749c1439b5ba3aff56c92976 <808f1e4b5723ae4eda724d2ad6f6638905eefd95, >=e4a0d3e720e7e508749c1439b5ba3aff56c92976 <81e9d6f8647650a7bead74c5f926e29970e834d1, >=e4a0d3e720e7e508749c1439b5ba3aff56c92976 <af126acf01a12bdb04986fd26fc2eb3b40249e0d, >=e4a0d3e720e7e508749c1439b5ba3aff56c92976 <c261f798f7baa8080cf0214081d43d5f86bb073f, >=e4a0d3e720e7e508749c1439b5ba3aff56c92976 <d8dca1bfe9adcae38b35add64977818c0c13dd22 | 178993157e8c50aef7f35d7d6d3b44bb428199e1, 4326d0080f7e84fba775da41d158f46cf9d3f1c2, 808f1e4b5723ae4eda724d2ad6f6638905eefd95, 81e9d6f8647650a7bead74c5f926e29970e834d1, af126acf01a12bdb04986fd26fc2eb3b40249e0d, c261f798f7baa8080cf0214081d43d5f86bb073f, d8dca1bfe9adcae38b35add64977818c0c13dd22 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket