In the Linux kernel through 4.20.11, af_alg_release() in crypto/af_alg.c neglects to set a NULL value for a certain structure member, which leads to a use-after-free in sockfs_setattr.
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 |
---|---|
http://www.securityfocus.com/bid/107063 | vdb entry third party advisory |
http://patchwork.ozlabs.org/patch/1042902/ | third party advisory patch |
https://usn.ubuntu.com/3930-1/ | third party advisory vendor advisory |
https://usn.ubuntu.com/3931-1/ | third party advisory vendor advisory |
https://usn.ubuntu.com/3931-2/ | third party advisory vendor advisory |
https://usn.ubuntu.com/3930-2/ | third party advisory vendor advisory |
http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00052.html | mailing list third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2020:0174 | third party advisory vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-8912 | issue tracking patch third party advisory |