First published: Fri Dec 03 2021(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/kernel-rt | <0:3.10.0-1160.62.1.rt56.1203.el7 | 0:3.10.0-1160.62.1.rt56.1203.el7 |
redhat/kernel | <0:3.10.0-1160.62.1.el7 | 0:3.10.0-1160.62.1.el7 |
redhat/kernel | <0:3.10.0-514.101.1.el7 | 0:3.10.0-514.101.1.el7 |
redhat/kernel | <0:3.10.0-693.99.1.el7 | 0:3.10.0-693.99.1.el7 |
redhat/kernel | <0:3.10.0-957.92.1.el7 | 0:3.10.0-957.92.1.el7 |
redhat/kernel | <0:3.10.0-1062.66.1.el7 | 0:3.10.0-1062.66.1.el7 |
redhat/kernel-rt | <0:4.18.0-372.9.1.rt7.166.el8 | 0:4.18.0-372.9.1.rt7.166.el8 |
redhat/kernel | <0:4.18.0-372.9.1.el8 | 0:4.18.0-372.9.1.el8 |
redhat/kernel | <0:4.18.0-147.64.1.el8_1 | 0:4.18.0-147.64.1.el8_1 |
redhat/kernel-rt | <0:4.18.0-193.79.1.rt13.129.el8_2 | 0:4.18.0-193.79.1.rt13.129.el8_2 |
redhat/kernel | <0:4.18.0-193.79.1.el8_2 | 0:4.18.0-193.79.1.el8_2 |
redhat/kernel-rt | <0:4.18.0-305.45.1.rt7.117.el8_4 | 0:4.18.0-305.45.1.rt7.117.el8_4 |
redhat/kernel | <0:4.18.0-305.45.1.el8_4 | 0:4.18.0-305.45.1.el8_4 |
redhat/redhat-virtualization-host | <0:4.3.22-20220330.1.el7_9 | 0:4.3.22-20220330.1.el7_9 |
redhat/kernel | <5.16 | 5.16 |
Linux Kernel | <4.4.294 | |
Linux Kernel | >=4.5<4.9.292 | |
Linux Kernel | >=4.10<4.14.257 | |
Linux Kernel | >=4.15<4.19.220 | |
Linux Kernel | >=4.20<5.4.164 | |
Linux Kernel | >=5.5.0<5.10.84 | |
Linux Kernel | >=5.11<5.15.7 | |
Linux Kernel | =5.16-rc1 | |
Linux Kernel | =5.16-rc2 | |
Linux Kernel | =5.16-rc3 | |
All of | ||
netapp h410c firmware | ||
netapp h410c | ||
All of | ||
netapp h300s firmware | ||
netapp h300s | ||
All of | ||
NetApp H500S Firmware | ||
netapp h500s | ||
All of | ||
netapp h700s firmware | ||
netapp h700s | ||
All of | ||
netapp h300e firmware | ||
netapp h300e | ||
All of | ||
netapp h500e firmware | ||
netapp h500e | ||
All of | ||
netapp h700e firmware | ||
netapp h700e | ||
All of | ||
netapp h410s firmware | ||
netapp h410s | ||
Debian GNU/Linux | =9.0 | |
Debian GNU/Linux | =10.0 | |
netapp hci management node | ||
netapp solidfire | ||
oracle communications Cloud native core binding support function | =22.1.3 | |
oracle communications cloud native core network exposure function | =22.1.1 | |
oracle communications Cloud native core policy | =22.2.0 | |
netapp h410c firmware | ||
netapp h410c | ||
netapp h300s firmware | ||
netapp h300s | ||
NetApp H500S Firmware | ||
netapp h500s | ||
netapp h700s firmware | ||
netapp h700s | ||
netapp h300e firmware | ||
netapp h300e | ||
netapp h500e firmware | ||
netapp h500e | ||
netapp h700e firmware | ||
netapp h700e | ||
netapp h410s firmware | ||
netapp h410s | ||
debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.128-1 6.12.12-1 6.12.15-1 | |
Android |
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2021-4083 has been rated as a medium severity vulnerability, which may allow local users to escalate their privileges or crash the system.
CVE-2021-4083 occurs due to a read-after-free memory flaw in the Linux kernel's garbage collection for Unix domain socket file handlers.
To fix CVE-2021-4083, update your kernel to a version that is patched and not vulnerable, such as those listed in the affected software section.
CVE-2021-4083 affects multiple versions of the Linux kernel, including various kernel-rt and kernel packages in Red Hat distributions.
Currently, there are no known workarounds for CVE-2021-4083 other than applying the security patch as soon as possible.