6 matches found
CVE-2026-72431
A flaw was found in the Linux kernel. A vulnerability exists in the /proc/allocinfo feature where the system may attempt to access memory after it has been freed, known as a use-after-free. This can happen when a kernel module is unloaded while the system is still processing information from...
CVE-2026-72431
In the Linux kernel, the following vulnerability has been resolved: alloctag: fix use-after-free in /proc/allocinfo after module unload allocinfostart only reinitializes the codetag iterator at position 0. For subsequent reads position 0, it reuses cached iterator state from the previous batch...
UBUNTU-CVE-2026-72431
In the Linux kernel, the following vulnerability has been resolved: alloctag: fix use-after-free in /proc/allocinfo after module unload allocinfostart only reinitializes the codetag iterator at position 0. For subsequent reads position 0, it reuses cached iterator state from the previous batch...
EUVD-2026-59330
In the Linux kernel, the following vulnerability has been resolved: alloctag: fix use-after-free in /proc/allocinfo after module unload allocinfostart only reinitializes the codetag iterator at position 0. For subsequent reads position 0, it reuses cached iterator state from the previous batch...
CVE-2026-72431 alloc_tag: fix use-after-free in /proc/allocinfo after module unload
In the Linux kernel, the following vulnerability has been resolved: alloctag: fix use-after-free in /proc/allocinfo after module unload allocinfostart only reinitializes the codetag iterator at position 0. For subsequent reads position 0, it reuses cached iterator state from the previous batch...
CVE-2026-72431 alloc_tag: fix use-after-free in /proc/allocinfo after module unload
In the Linux kernel, the following vulnerability has been resolved: alloctag: fix use-after-free in /proc/allocinfo after module unload allocinfostart only reinitializes the codetag iterator at position 0. For subsequent reads position 0, it reuses cached iterator state from the previous batch...