Memory Leak Affecting runc package, versions <1:1.1.12-4.module+el8.10.0+22202+761b9a65

Note: Versions mentioned in the description apply only to the upstream runc package and not the runc package as distributed by Centos. See How to fix? for Centos:8 relevant fixed versions and status.

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.

• https://access.redhat.com/security/cve/CVE-2024-1394
• https://bugzilla.redhat.com/show_bug.cgi?id=2262921
• https://github.com/golang-fips/openssl/security/advisories/GHSA-78hx-gp6g-7mj6
• https://github.com/golang-fips/openssl/commit/85d31d0d257ce842c8a1e63c4d230ae850348136
• https://github.com/microsoft/go-crypto-openssl/commit/104fe7f6912788d2ad44602f77a0a0a62f1f259f
• https://pkg.go.dev/vuln/GO-2024-2660
• https://vuln.go.dev/ID/GO-2024-2660.json
• https://access.redhat.com/errata/RHSA-2024:5258