mm/mremap.c in the Linux kernel before 5.13.3 has a use-after-free via a stale TLB because an rmap lock is not held during a PUD move.
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.
Link | Tags |
---|---|
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.13.3 | release notes vendor advisory |
https://bugs.chromium.org/p/project-zero/issues/detail?id=2347 | exploit third party advisory mailing list issue tracking patch |
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=97113eb39fa7972722ff490b947d8af023e1f6a2 | vendor advisory patch |
http://packetstormsecurity.com/files/168466/Linux-Stable-5.4-5.10-Use-After-Free-Race-Condition.html | vdb entry third party advisory |
https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html | third party advisory mailing list |
https://security.netapp.com/advisory/ntap-20230214-0008/ | third party advisory |
http://packetstormsecurity.com/files/171005/Kernel-Live-Patch-Security-Notice-LNS-0091-1.html | third party advisory patch |