CVE-2025-2295 json
Potential iSCSI R2T PDU Vulnerability
published last yr. modified 4mo ago also EUVD-2025-7558
- cvss
- 3.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
EDK2 contains a vulnerability in BIOS where a user may cause an Integer Overflow or Wraparound by network means. A successful exploitation of this vulnerability may lead to denial of service.
Patch / fix
- edk2 Debian 14, Debian 13 2025.02-4
debian advisories DEBIAN-CVE-2025-2295
- edk2 Ubuntu 22.04 LTS 2022.02-3ubuntu0.22.04.4
- edk2 Ubuntu 24.04 LTS 2024.02-2ubuntu0.6
ubuntu advisories UBUNTU-CVE-2025-2295
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- edk2 Azure Linux 3.0 20240524git3e722403cd16-14
- edk2 CBL-Mariner 2.0 20230301gitf80f052277c8-45
- hvloader CBL-Mariner 2.0 1.0.1-16
azure linux advisories AZL-58803AZL-58822AZL-58828
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
Is CVE-2025-2295 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:L |
Affected products
- TianoCore EDK2
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
References
Sources
- CVE List CVE-2025-2295
- NVD CVE-2025-2295
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.