LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71131: crypto: seqiv - Do not use req->iv after crypto_aead_encrypt

In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Do not use req->iv after crypto_aead_encrypt As soon as crypto_aead_encrypt is called, the underlying request may be freed by an asynchronous completion. Thus dereferencing req->iv after it returns is invalid. Instead of checking req->iv against info, create a new variable unaligned_info and use it for that purpose instead.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel crypto bug. After an encryption call, the request object may already be freed by asynchronous completion, but the code could still read its IV pointer. The sources confirm a kernel fix, but do not provide CVSS, exploitability, or business impact details.

Executive priority

Track and remediate through normal kernel patch governance unless vendor guidance raises urgency. Current evidence confirms a real kernel memory-safety fix but does not support active exploitation, severity, or broad product impact claims.

Technical view

The seqiv AEAD path dereferenced req->iv after crypto_aead_encrypt returned. Because asynchronous completion may free the underlying request immediately, that dereference is invalid. The fix avoids using req->iv after the call by tracking unaligned_info separately.

Likely exposure

Exposure is limited to systems running affected Linux kernel builds containing the vulnerable seqiv code path. The bundle lists Linux as affected across multiple kernel version lines and includes stable commit references. It does not identify specific distributions, appliances, or Siemens products as affected.

Exploitation context

No active exploitation is stated. KEV is false, and the bundle does not provide exploit reports, attack vector, required privileges, or proof-of-concept details. Treat exploitability as unconfirmed from the supplied evidence.

Researcher notes

The key issue is post-call lifetime misuse in crypto/seqiv. The source bundle supports the code-level root cause and fix direction, but lacks reachability, trigger conditions, privilege assumptions, crash behavior, and affected downstream product mapping.

Mitigation direction

  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Follow distribution or product vendor advisories before changing managed kernels.
  • Check Siemens guidance if your environment uses Siemens products covered by SSA-019113.
  • Prioritize critical systems once vendor severity and applicability are confirmed.

Validation and detection

  • Inventory running kernel versions across servers, appliances, and embedded systems.
  • Compare vendor kernel builds against the referenced stable fix commits.
  • Check distribution security trackers for backported fixes under CVE-2025-71131.
  • Confirm whether Siemens SSA-019113 applies to deployed products.
  • Record unknown applicability where vendor evidence is not yet available.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71131 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0a270321dbf948963aeb0e8382fe17d2c2eb3771, 0a270321dbf948963aeb0e8382fe17d2c2eb3771, 0a270321dbf948963aeb0e8382fe17d2c2eb3771, 0a270321dbf948963aeb0e8382fe17d2c2eb3771, 0a270321dbf948963aeb0e8382fe17d2c2eb3771, 0a270321dbf948963aeb0e8382fe17d2c2eb3771, 0a270321dbf948963aeb0e8382fe17d2c2eb3771unaffected
LinuxLinux2.6.25, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.4, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.