Skip to main content
VulnerabilityPublished Updated

CVE-2025-71113: Linux kernel · Memory Buffer Overflow

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f81244fd6b14fecfa93b66b6bb1d59f96554e550 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 11:54 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in f81244fd6b14fecfa93b66b6bb1d59f96554e550, e125c8e346e4eb7b3e854c862fcb4392bc13ddba, 84238876e3b3b262cf62d5f4d1338e983fb27010 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ fe869cdb89c95d060c77eea20204d6c91f233b53, < f81244fd6b14fecfa93b66b6bb1d59f96554e550
Fixed in
  • f81244fd6b14fecfa93b66b6bb1d59f96554e550
LinuxLinuxAffected
  • ≥ fe869cdb89c95d060c77eea20204d6c91f233b53, < e125c8e346e4eb7b3e854c862fcb4392bc13ddba
Fixed in
  • e125c8e346e4eb7b3e854c862fcb4392bc13ddba
LinuxLinuxAffected
  • ≥ fe869cdb89c95d060c77eea20204d6c91f233b53, < 84238876e3b3b262cf62d5f4d1338e983fb27010
Fixed in
  • 84238876e3b3b262cf62d5f4d1338e983fb27010
LinuxLinuxAffected
  • ≥ fe869cdb89c95d060c77eea20204d6c91f233b53, < 543bf004e4eafbb302b1e6c78570d425d2ca13a0
Fixed in
  • 543bf004e4eafbb302b1e6c78570d425d2ca13a0
LinuxLinuxAffected
  • ≥ fe869cdb89c95d060c77eea20204d6c91f233b53, < 51a5ab36084f3251ef87eda3e6a6236f6488925e
Fixed in
  • 51a5ab36084f3251ef87eda3e6a6236f6488925e
LinuxLinuxAffected
  • ≥ fe869cdb89c95d060c77eea20204d6c91f233b53, < 6f6e309328d53a10c0fe1f77dec2db73373179b6
Fixed in
  • 6f6e309328d53a10c0fe1f77dec2db73373179b6

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.

References

Community reviews

Loading reviews…