First published: Tue May 25 2021(Updated: )
A memory leak vulnerability was found in Linux kernel in llcp_sock_connect
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | ||
Fedora | =32 | |
Fedora | =33 | |
Fedora | =34 | |
Debian | =9.0 | |
NetApp Active IQ Unified Manager | ||
NetApp Cloud Backup | ||
All of | ||
NetApp SolidFire Baseboard Management Controller Firmware | ||
NetApp SolidFire | ||
All of | ||
NetApp H410C | ||
NetApp H410C Firmware | ||
All of | ||
NetApp H300S Firmware | ||
NetApp H300S Firmware | ||
All of | ||
NetApp H500e Firmware | ||
NetApp H500e Firmware | ||
All of | ||
NetApp H700S | ||
NetApp H700S | ||
All of | ||
NetApp H300E | ||
NetApp H300E Firmware | ||
All of | ||
NetApp H500E | ||
NetApp H500e Firmware | ||
All of | ||
NetApp H700E | ||
NetApp H700E | ||
All of | ||
NetApp H410S | ||
NetApp H410S Firmware | ||
NetApp SolidFire Baseboard Management Controller Firmware | ||
NetApp SolidFire | ||
NetApp H410C | ||
NetApp H410C Firmware | ||
NetApp H300S Firmware | ||
NetApp H300S Firmware | ||
NetApp H500e Firmware | ||
NetApp H500e Firmware | ||
NetApp H700S | ||
NetApp H700S | ||
NetApp H300E | ||
NetApp H300E Firmware | ||
NetApp H500E | ||
NetApp H500e Firmware | ||
NetApp H700E | ||
NetApp H700E | ||
NetApp H410S | ||
NetApp H410S Firmware | ||
debian/linux | 5.10.223-1 5.10.234-1 6.1.123-1 6.1.128-1 6.12.12-1 6.12.17-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2020-25672 is classified as medium due to its potential for memory leaks affecting system performance.
To fix CVE-2020-25672, update the Linux kernel to versions 5.10.223-1, 5.10.226-1, 6.1.119-1, 6.1.123-1, 6.12.10-1, or 6.12.11-1.
CVE-2020-25672 affects multiple versions of the Linux kernel, specifically those prior to the patched versions mentioned in the fixes.
CVE-2020-25672 is not known to be exploitable remotely, as it primarily affects the local socket connection.
A definitive workaround for CVE-2020-25672 is not documented; the best course of action is to apply the available updates.