Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-71113crypto: af_alg - zero initialize memory allocated via sock_kmalloc

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-71113, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected fe869cdb89c95d060c77eea20204d6c91f233b53 – < e125c8e346e4eb7b3e854c862fcb4392bc13ddba
    • affected fe869cdb89c95d060c77eea20204d6c91f233b53 – < 543bf004e4eafbb302b1e6c78570d425d2ca13a0
    • affected fe869cdb89c95d060c77eea20204d6c91f233b53 – < f81244fd6b14fecfa93b66b6bb1d59f96554e550
    • affected fe869cdb89c95d060c77eea20204d6c91f233b53 – < 84238876e3b3b262cf62d5f4d1338e983fb27010
    • affected fe869cdb89c95d060c77eea20204d6c91f233b53 – < 5a4b65523608974a81edbe386f8a667a3e10c726
    • affected fe869cdb89c95d060c77eea20204d6c91f233b53 – < 51a5ab36084f3251ef87eda3e6a6236f6488925e
    • affected fe869cdb89c95d060c77eea20204d6c91f233b53 – < 6f6e309328d53a10c0fe1f77dec2db73373179b6
  • Linux · Linux

    • affected 2.6.38
    • unaffected < 2.6.38
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.64 – ≤ 6.12.*
    • unaffected 6.18.3 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-71113 badge
[![CVE-2025-71113](https://cveledger.app/badge/CVE-2025-71113.svg)](https://cveledger.app/cve/CVE-2025-71113)

Record last updated .