CVE-2023-52646
aio: fix mremap after fork null-deref
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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]
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.19
References 7
git.kernel.org
- stable/c/808f1e4b5723ae4eda724d2ad6f6638905eefd95
- stable/c/d8dca1bfe9adcae38b35add64977818c0c13dd22
- stable/c/4326d0080f7e84fba775da41d158f46cf9d3f1c2
- stable/c/c261f798f7baa8080cf0214081d43d5f86bb073f
- stable/c/178993157e8c50aef7f35d7d6d3b44bb428199e1
- stable/c/af126acf01a12bdb04986fd26fc2eb3b40249e0d
- stable/c/81e9d6f8647650a7bead74c5f926e29970e834d1