Description
A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey and ctx. That function uses named return parameters to free pkey and ctx if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey and ctx will be nil inside the deferred function that should free them.
References10
- access.redhat.com/errata/RHSA-2024:1462
- access.redhat.com/errata/RHSA-2024:1468
- access.redhat.com/errata/RHSA-2024:1472
- access.redhat.com/errata/RHSA-2024:1501
- access.redhat.com/errata/RHSA-2024:1502
- access.redhat.com/errata/RHSA-2024:1561
- access.redhat.com/errata/RHSA-2024:1563
- access.redhat.com/errata/RHSA-2024:1566
- access.redhat.com/errata/RHSA-2024:1567
- access.redhat.com/errata/RHSA-2024:1574
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 2% percentile: 75 · as of 5 November 2026
- CWE
- CWE-401
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.