A use-after-free flaw was found in the Linux kernel’s mm/mremap memory address space accounting source code. This issue occurs due to a race condition between rmap walk and mremap, allowing a local user to crash the system or potentially escalate their privileges on the system.
Weakness
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Linux_kernel | Linux | * | 5.14 (excluding) |
| Red Hat Enterprise Linux 8 | RedHat | kpatch-patch | * |
Potential Mitigations
References
- https://access.redhat.com/errata/RHSA-2023:1659
- https://access.redhat.com/security/cve/CVE-2023-1476
- https://bugzilla.redhat.com/show_bug.cgi?id=2176035
- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=97113eb39fa7972722ff490b947d8af023e1f6a2
- https://access.redhat.com/errata/RHSA-2023:1659
- https://access.redhat.com/security/cve/CVE-2023-1476
- https://bugzilla.redhat.com/show_bug.cgi?id=2176035
- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=97113eb39fa7972722ff490b947d8af023e1f6a2