Missing Initialization of Resource Affecting libperf package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS10-LIBPERF-14956961
- published15 Jan 2026
- disclosed1 Jan 2025
Introduced: 1 Jan 2025
CVE-2025-71113 (opens in a new tab)How to fix?
There is no fixed version for Centos:10 libperf.
NVD Description
Note: Versions mentioned in the description apply only to the upstream libperf package and not the libperf package as distributed by Centos.
See How to fix? for Centos:10 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
crypto: af_alg - zero initialize memory allocated via sock_kmalloc
Several crypto user API contexts and requests allocated with sock_kmalloc() were left uninitialized, relying on callers to set fields explicitly. This resulted in the use of uninitialized data in certain error paths or when new fields are added in the future.
The ACVP patches also contain two user-space interface files: algif_kpp.c and algif_akcipher.c. These too rely on proper initialization of their context structures.
A particular issue has been observed with the newly added 'inflight' variable introduced in af_alg_ctx by commit:
67b164a871af ("crypto: af_alg - Disallow multiple in-flight AIO requests")
Because the context is not memset to zero after allocation, the inflight variable has contained garbage values. As a result, af_alg_alloc_areq() has incorrectly returned -EBUSY randomly when the garbage value was interpreted as true:
https://github.com/gregkh/linux/blame/master/crypto/af_alg.c#L1209
The check directly tests ctx->inflight without explicitly comparing against true/false. Since inflight is only ever set to true or false later, an uninitialized value has triggered -EBUSY failures. Zero-initializing memory allocated with sock_kmalloc() ensures inflight and other fields start in a known state, removing random issues caused by uninitialized data.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2429611
- https://access.redhat.com/security/cve/CVE-2025-71113
- https://git.kernel.org/stable/c/51a5ab36084f3251ef87eda3e6a6236f6488925e
- https://git.kernel.org/stable/c/5a4b65523608974a81edbe386f8a667a3e10c726
- https://git.kernel.org/stable/c/6f6e309328d53a10c0fe1f77dec2db73373179b6
- https://git.kernel.org/stable/c/84238876e3b3b262cf62d5f4d1338e983fb27010
- https://git.kernel.org/stable/c/f81244fd6b14fecfa93b66b6bb1d59f96554e550
- https://git.kernel.org/stable/c/543bf004e4eafbb302b1e6c78570d425d2ca13a0
- https://git.kernel.org/stable/c/e125c8e346e4eb7b3e854c862fcb4392bc13ddba