A use-after-free flaw was found in the Linux kernel’s FUSE filesystem in the way a user triggers write(). This flaw allows a local user to gain unauthorized access to data from the FUSE filesystem, resulting in privilege escalation.
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://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git/commit/?h=for-next | vendor advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=2064855 | third party advisory issue tracking |
| https://lists.debian.org/debian-lts-announce/2022/07/msg00000.html | third party advisory mailing list |
| https://www.debian.org/security/2022/dsa-5173 | third party advisory vendor advisory |
| https://www.oracle.com/security-alerts/cpujul2022.html | third party advisory |