Skip to content
Heist/ feed
Back to feed
UnratedFix available

crypto: af_alg - zero initialize memory allocated via sock_kmalloc

Type: advisorySources: OSV

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.

Products
Kernel
Affected versions
Not specified
Fixed versions
5.10.248, 5.15.198, 6.1.160, 6.12.64, 6.18.3, 6.6.120
CVEs
CVE-2025-71113
Confirmed fixed CVEs
Not specified
Updated in this feed
6 Nov 2026, 02:31 UTC · Revision 1

Source evidence

crypto: af_alg - zero initialize memory allocated via sock_kmalloc

core-osv · Original source

Published 14 Jan 2026, 15:05 UTC

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.

osv:CVE-2025-71113

Kernel

Fixed versions: 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3

Complete source record
{
  "id": "40f730847ddae6f2bfac782670b21d13c98a1470955c644b11bd19517924d60d",
  "url": "https://osv.dev/vulnerability/CVE-2025-71113",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "crypto: af_alg - zero initialize memory allocated via sock_kmalloc",
    "summary": "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.",
    "evidence": "osv:CVE-2025-71113",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.10.248",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.15.198",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.1.160",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.120",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.64",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.3",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2025-71113",
      "aliases": [
        "CVE-2025-71113"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "fe869cdb89c95d060c77eea20204d6c91f233b53"
                },
                {
                  "fixed": "e125c8e346e4eb7b3e854c862fcb4392bc13ddba"
                },
                {
                  "fixed": "543bf004e4eafbb302b1e6c78570d425d2ca13a0"
                },
                {
                  "fixed": "f81244fd6b14fecfa93b66b6bb1d59f96554e550"
                },
                {
                  "fixed": "84238876e3b3b262cf62d5f4d1338e983fb27010"
                },
                {
                  "fixed": "5a4b65523608974a81edbe386f8a667a3e10c726"
                },
                {
                  "fixed": "51a5ab36084f3251ef87eda3e6a6236f6488925e"
                },
                {
                  "fixed": "6f6e309328d53a10c0fe1f77dec2db73373179b6"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-71113.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "2.6.38"
                },
                {
                  "fixed": "5.10.248"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.11.0"
                },
                {
                  "fixed": "5.15.198"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "6.1.160"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.120"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.64"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.3"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-71113.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:45.989488946Z",
      "provider": "osv",
      "references": [
        "https://cert-portal.siemens.com/productcert/html/ssa-019113.html",
        "https://cert-portal.siemens.com/productcert/html/ssa-457936.html",
        "https://git.kernel.org/stable/c/51a5ab36084f3251ef87eda3e6a6236f6488925e",
        "https://git.kernel.org/stable/c/543bf004e4eafbb302b1e6c78570d425d2ca13a0",
        "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/e125c8e346e4eb7b3e854c862fcb4392bc13ddba",
        "https://git.kernel.org/stable/c/f81244fd6b14fecfa93b66b6bb1d59f96554e550",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/71xxx/CVE-2025-71113.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-71113",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/71xxx/CVE-2025-71113.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-71113",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 514298,
  "published_at": "2026-01-14T15:05:59.992+00:00"
}