CVE-2025-71131

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-01-14. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

January 14, 2026

Last Modified

September 8, 2026

Advisory Details (8)

Auto-updated Jul 14, 2026
No patch confirmed yet.
generic

crypto: seqiv - Do not use req->iv after crypto_aead_encrypt - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ccbb96434d88e32358894c879457b33f7508e798
generic

crypto: seqiv - Do not use req->iv after crypto_aead_encrypt - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/baf0e2d1e03ddb04781dfe7f22a654d3611f69b2
generic

crypto: seqiv - Do not use req->iv after crypto_aead_encrypt - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5476f7f8a311236604b78fcc5b2a63b3a61b0169
generic

crypto: seqiv - Do not use req->iv after crypto_aead_encrypt - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50fdb78b7c0bcc550910ef69c0984e751cac72fa
generic

crypto: seqiv - Do not use req->iv after crypto_aead_encrypt - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50f196d2bbaee4ab2494bb1b0d294deba292951a
generic

crypto: seqiv - Do not use req->iv after crypto_aead_encrypt - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18202537856e0fae079fed2c9308780bcff2bb9d
generic

crypto: seqiv - Do not use req->iv after crypto_aead_encrypt - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0279978adec6f1296af66b642cce641c6580be46

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-09-08ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-09-08ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-09-08ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1094.98) @ jammy2026-09-08ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-09-08ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1047.48) @ noble2026-09-08ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1051.54) @ noble2026-09-08ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1054.57+fips1) @ noble2026-09-08ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1052.56) @ noble2026-09-08ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2042.43) @ noble2026-09-08ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1051.54.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-09-08ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1022.22) @ noble2026-09-08ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-09-08ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-09-08ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1049.50) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1013.13) @ questing2026-09-08ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1054.57~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1014.14) @ questing2026-09-08ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-09-08ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1099.98) @ jammy2026-09-08ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-09-08ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-22.22) @ questing2026-09-08ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1011.11) @ questing2026-09-08ubuntu
ubuntulinux-virtual-6.8 (6.8.0-110.110) @ noble2026-09-08ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1010.11~24.04.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1012.12) @ questing2026-09-08ubuntu
redhatkernel-0:6.12.0-55.98.1.el10_02026-08-17redhat
redhatkernel-0:5.14.0-570.132.1.el9_62026-08-10redhat
linuxKernel @ 5.10.248osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (48 versions)5.10.249-1
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)6.1.162-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)6.1.162-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)6.12.69-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (95 versions)6.18.5-1

Additional Vendor Advisories

(22)

Data Freshness Timeline

(refreshed 7× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 168 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 19:30 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:14 UTCEPSS rescore
  5. 2026-09-15 03:10 UTCEPSS rescore
  6. 2026-09-13 16:46 UTCEPSS rescore
  7. 2026-09-12 15:00 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-11 09:36 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-08 09:25 UTCEG score recompute
  13. 2026-09-08 09:25 UTCVendor advisory
  14. 2026-09-08 09:25 UTCGHSA enrichment
  15. 2026-09-07 16:00 UTCEPSS rescore
  16. 2026-09-06 13:47 UTCEPSS rescore
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-08-31 07:25 UTCOSV refresh
  21. 2026-08-30 01:21 UTCEPSS rescore
  22. 2026-08-28 21:40 UTCEPSS rescore
  23. 2026-08-27 14:24 UTCEPSS rescore
  24. 2026-08-26 14:45 UTCEPSS rescore
  25. 2026-08-25 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-24 14:16 UTCEPSS rescore
  2. 2026-08-23 00:18 UTCEPSS rescore
  3. 2026-08-21 23:48 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 13:46 UTCEPSS rescore
  8. 2026-08-16 14:55 UTCEPSS rescore
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 14:16 UTCEG score recompute
  12. 2026-08-14 14:16 UTCVendor advisory
  13. 2026-08-14 14:16 UTCGHSA enrichment
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 13:42 UTCEPSS rescore
  17. 2026-08-10 23:59 UTCEPSS rescore
  18. 2026-08-09 19:45 UTCEG score recompute
  19. 2026-08-09 19:45 UTCVendor advisory
  20. 2026-08-09 19:45 UTCGHSA enrichment
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-08 16:36 UTCEPSS rescore
  23. 2026-08-08 00:36 UTCEG score recompute
  24. 2026-08-08 00:36 UTCVendor advisory
  25. 2026-08-08 00:36 UTCGHSA enrichment
  26. 2026-08-07 16:27 UTCEPSS rescore
  27. 2026-08-06 13:46 UTCEPSS rescore
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-05 12:46 UTCEG score recompute
  30. 2026-08-05 12:46 UTCVendor advisory
  31. 2026-08-05 12:46 UTCGHSA enrichment
  32. 2026-08-04 10:37 UTCEPSS rescore
  33. 2026-08-03 10:35 UTCEPSS rescore
  34. 2026-08-02 23:26 UTCEG score recompute
  35. 2026-08-02 23:26 UTCVendor advisory
  36. 2026-08-02 23:26 UTCGHSA enrichment
  37. 2026-08-02 02:26 UTCEPSS rescore
  38. 2026-08-01 04:15 UTCEPSS rescore
  39. 2026-07-30 16:27 UTCEPSS rescore
  40. 2026-07-30 06:42 UTCEG score recompute
  41. 2026-07-30 06:42 UTCVendor advisory
  42. 2026-07-30 06:41 UTCGHSA enrichment
  43. 2026-07-30 01:30 UTCEPSS rescore
  44. 2026-07-27 14:13 UTCEPSS rescore
  45. 2026-07-26 14:54 UTCEPSS rescore
  46. 2026-07-26 14:54 UTCEPSS rescore
  47. 2026-07-25 14:17 UTCEPSS rescore
  48. 2026-07-25 14:17 UTCEPSS rescore
  49. 2026-07-24 14:17 UTCEPSS rescore
  50. 2026-07-23 14:18 UTCEPSS rescore
  51. 2026-07-23 14:18 UTCEPSS rescore
  52. 2026-07-23 10:19 UTCOSV refresh
  53. 2026-07-23 03:03 UTCEG score recompute
  54. 2026-07-21 15:24 UTCEPSS rescore
  55. 2026-07-20 17:08 UTCEPSS rescore
  56. 2026-07-19 14:30 UTCEPSS rescore
  57. 2026-07-19 14:30 UTCEPSS rescore
  58. 2026-07-19 02:28 UTCEPSS rescore
  59. 2026-07-19 02:28 UTCEPSS rescore
  60. 2026-07-18 10:04 UTCEPSS rescore
  61. 2026-07-18 10:04 UTCEPSS rescore
  62. 2026-07-16 17:02 UTCEPSS rescore
  63. 2026-07-16 17:02 UTCEPSS rescore
  64. 2026-07-15 16:57 UTCEPSS rescore
  65. 2026-07-15 16:57 UTCEPSS rescore
  66. 2026-07-15 02:00 UTCEPSS rescore
  67. 2026-07-15 01:59 UTCEPSS rescore
  68. 2026-07-14 13:19 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  69. 2026-07-13 06:12 UTCEPSS rescore
  70. 2026-07-12 05:46 UTCEPSS rescore
  71. 2026-07-12 05:46 UTCEPSS rescore
  72. 2026-07-11 08:27 UTCEPSS rescore
  73. 2026-07-11 08:27 UTCEPSS rescore
  74. 2026-07-09 19:10 UTCEPSS rescore
  75. 2026-07-08 15:15 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-71131?
CVE-2025-71131 is a medium vulnerability published on January 14, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Do not use req->iv after cryptoaeadencrypt As soon as cryptoaeadencrypt is called, the underlying request may be freed by an asynchronous completion. Thus dereferencing req->iv after it returns is invalid. Instead…
When was CVE-2025-71131 disclosed?
CVE-2025-71131 was first published in the National Vulnerability Database on January 14, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71131 actively exploited?
CVE-2025-71131 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.3% of all scored CVEs.
What is the CVSS score of CVE-2025-71131?
CVE-2025-71131 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-71131?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71131, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71131

Explore →

Is Your Infrastructure Affected by CVE-2025-71131?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.