In the Linux kernel before 5.2, a setxattr operation, after a mount of a crafted ext4 image, can cause a slab-out-of-bounds write access because of an ext4_xattr_set_entry use-after-free in fs/ext4/xattr.c when a large old_size value is used in a memset call, aka CID-345c0dbf3a30.
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://github.com/bobfuzzer/CVE/tree/master/CVE-2019-19319 | third party advisory exploit |
https://security.netapp.com/advisory/ntap-20200103-0001/ | third party advisory |
http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00021.html | mailing list third party advisory vendor advisory |
https://lists.debian.org/debian-lts-announce/2020/06/msg00011.html | mailing list |
https://lists.debian.org/debian-lts-announce/2020/06/msg00012.html | mailing list |
https://lists.debian.org/debian-lts-announce/2020/06/msg00013.html | mailing list |
https://www.debian.org/security/2020/dsa-4698 | vendor advisory |
https://usn.ubuntu.com/4391-1/ | vendor advisory |
https://bugzilla.suse.com/show_bug.cgi?id=1158021 | |
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=345c0dbf3a30 |