A read-after-free memory flaw was found in the Linux kernel's garbage collection for Unix domain socket file handlers in the way users call close() and fget() simultaneously and can potentially trigger a race condition. This flaw allows a local user to crash the system or escalate their privileges on the system. This flaw affects Linux kernel versions prior to 5.16-rc4.
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.
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
| Link | Tags |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=2029923 | issue tracking third party advisory patch |
| https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=054aa8d439b9 | mailing list patch |
| https://lists.debian.org/debian-lts-announce/2022/03/msg00011.html | third party advisory mailing list |
| https://lists.debian.org/debian-lts-announce/2022/03/msg00012.html | third party advisory mailing list |
| https://www.debian.org/security/2022/dsa-5096 | third party advisory vendor advisory |
| https://www.oracle.com/security-alerts/cpujul2022.html | third party advisory patch |
| https://security.netapp.com/advisory/ntap-20220217-0005/ | third party advisory |