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.

Published: 2026-01-14 Last update: 2026-03-25 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Conclusion & alert: CVE-2025-71131 is rated Low Risk (24.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.03%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-71131

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-26 0.06% 0.03% -0.03%
2 2026-02-13 0.02% 0.06% +0.04%
3 2026-01-15 0.02%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-71131

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 3.6 [email protected]

Weakness enumeration for CVE-2025-71131

OS Trackers for CVE-2025-71131

vendor priority summary link
debian not yet assigned CVE-2025-71131 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6. https://security-tracker.debian.org/tracker/CVE-2025-71131
redhat medium https://access.redhat.com/security/cve/CVE-2025-71131
suse medium CVE-2025-71131 severity moderate: SUSE including 388 source package names (13.2-9.1:libsqlite3-0-3.49.1-1.1, 2.1.3-6.115:kernel-default-base-6.4.0-39.1.21.16, …), 577 product×package rows across 66 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (66 product lines)): Fixed 310, Known Affected 231, First Fixed 32, Known Not Affected 4. https://www.suse.com/security/cve/CVE-2025-71131/
ubuntu medium CVE-2025-71131 medium priority: Ubuntu including 157 source packages (linux, linux-allwinner-5.19, …), 1562 status rows across 10 suites (bionic, focal, jammy, noble, plucky, questing, resolute, trusty, upstream, xenial): DNE 1157, ignored 183, released 150, needed 49, pending 12, not-affected 11. https://ubuntu.com/security/CVE-2025-71131

Affected software / configurations for CVE-2025-71131

Vendor Product Version Raw CPE
linux linux_kernel >= 2.6.25.1, < 5.10.248 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.11, < 5.15.198 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.16, < 6.1.160 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.2, < 6.6.120 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.7, < 6.12.64 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.13, < 6.18.4 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 2.6.25 cpe:2.3:o:linux:linux_kernel:2.6.25:-:*:*:*:*:*:*
linux linux_kernel 6.19 cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*
linux linux_kernel 6.19 cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*
linux linux_kernel 6.19 cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*
linux linux_kernel 6.19 cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*
linux linux_kernel 6.19 cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*
linux linux_kernel 6.19 cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*
linux linux_kernel 6.19 cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*
linux linux_kernel 6.19 cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:*

References for CVE-2025-71131

cvelogic Threat Intelligence