CVE-2025-71130: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-fcj7-h6w4-whvj
Share
CVSS 5.5
CWE-457 CWE-476
Published
Advisory Summary

CVE-2025-71130 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-457: Use of Uninitialized Variable) affecting Software libraries in the Maven ecosystem. The weakness occurs when the code uses a variable that has not been initialized, leading to unpredictable or unintended results.. Remediation is available in the latest vendor maintenance releases.

CVE-2025-71130 at a Glance

CVE Identifier CVE-2025-71130
GHSA Identifier GHSA-fcj7-h6w4-whvj
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-457: Use of Uninitialized Variable
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2025-71130

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-71130, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-457: Use of Uninitialized Variable, where the code uses a variable that has not been initialized, leading to unpredictable or unintended results. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: drm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer Initialize the eb.vma array with values of 0 when the eb structure is first set up. In particular, this sets the eb->vma[i].vma pointers to NULL, simplifying cleanup and getting rid of the bug described below. During the execution of eb_lookup_vmas(), the eb->vma array is successively filled up with struct eb_vma objects. This process includes calling eb_add_vma(), which might fail; however, even in the event of failure, eb->vma[i].vma is set for the currently processed buffer. If eb_add_vma() fails, eb_lookup_vmas() returns with an error, which prompts a call to eb_release_vmas() to clean up the mess. Since eb_lookup_vmas() might fail during processing any (possibly not first) buffer, eb_release_vmas() checks whether a buffer's vma is NULL to know at what point did the lookup function fail. In eb_lookup_vmas(), eb->vma[i].vma is set to NULL if either the helper function eb_lookup_vma() or eb_validate_vma() fails. eb->vma[i+1].vma is set to NULL in case i915_gem_object_userptr_submit_init() fails; the current one needs to be cleaned up by eb_release_vmas() at this point, so the next one is set. If eb_add_vma() fails, neither the current nor the next vma is set to NULL, which is a source of a NULL deref bug described in the issue linked in the Closes tag. When entering eb_lookup_vmas(), the vma pointers are set to the slab poison value, instead of NULL. This doesn't matter for the actual lookup, since it gets overwritten anyway, however the eb_release_vmas() function only recognizes NULL as the stopping value, hence the pointers are being set to NULL as they go in case of intermediate failure. This patch changes the approach to filling them all with NULL at the start instead, rather than handling that manually during failure. (cherry picked from commit 08889b706d4f0b8d2352b7ca29c2d8df4d0787cd)

References

NVD — CVE-2025-71130 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-71130
git.kernel.org/stable/c/0336188cc8... WEB
https://git.kernel.org/stable/c/0336188cc85d0eab8463bd1bbd4ded4e9602de8b
git.kernel.org/stable/c/24d55ac8e3... WEB
https://git.kernel.org/stable/c/24d55ac8e31d2f8197bfad71ffcb3bae21ed7117
git.kernel.org/stable/c/25d69e0777... WEB
https://git.kernel.org/stable/c/25d69e07770745992387c016613fd7ac8eaf9893
git.kernel.org/stable/c/4fe2bd1954... WEB
https://git.kernel.org/stable/c/4fe2bd195435e71c117983d87f278112c5ab364c
git.kernel.org/stable/c/63f23aa2fb... WEB
https://git.kernel.org/stable/c/63f23aa2fbb823c8b15a29269fde220d227ce5b3

Frequently Asked Questions

What is CVE-2025-71130?
CVE-2025-71130 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-457: Use of Uninitialized Variable.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2025-71130?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2025-71130?
CVE-2025-71130 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2025-71130?
CVE-2025-71130 is classified under CWE-457: Use of Uninitialized Variable (The code uses a variable that has not been initialized, leading to unpredictable or unintended results.).
How can I check Maven dependencies for CVE-2025-71130?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fcj7-h6w4-whvj",
  "modified" : "2026-03-25T21:30:22Z",
  "published" : "2026-01-14T15:33:02Z",
  "aliases" : [ "CVE-2025-71130" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer\n\nInitialize the eb.vma array with values of 0 when the eb structure is\nfirst set up. In particular, this sets the eb->vma[i].vma pointers to\nNULL, simplifying cleanup and getting rid of the bug described below.\n\nDuring the execution of eb_lookup_vmas(), the eb->vma array is\nsuccessively filled up with struct eb_vma objects. This process includes\ncalling eb_add_vma(), which might fail; however, even in the event of\nfailure, eb->vma[i].vma is set for the currently processed buffer.\n\nIf eb_add_vma() fails, eb_lookup_vmas() returns with an error, which\nprompts a call to eb_release_vmas() to clean up the mess. Since\neb_lookup_vmas() might fail during processing any (possibly not first)\nbuffer, eb_release_vmas() checks whether a buffer's vma is NULL to know\nat what point did the lookup function fail.\n\nIn eb_lookup_vmas(), eb->vma[i].vma is set to NULL if either the helper\nfunction eb_lookup_vma() or eb_validate_vma() fails. eb->vma[i+1].vma is\nset to NULL in case i915_gem_object_userptr_submit_init() fails; the\ncurrent one needs to be cleaned up by eb_release_vmas() at this point,\nso the next one is set. If eb_add_vma() fails, neither the current nor\nthe next vma is set to NULL, which is a source of a NULL deref bug\ndescribed in the issue linked in the Closes tag.\n\nWhen entering eb_lookup_vmas(), the vma pointers are set to the slab\npoison value, instead of NULL. This doesn't matter for the actual\nlookup, since it gets overwritten anyway, however the eb_release_vmas()\nfunction only recognizes NULL as the stopping value, hence the pointers\nare being set to NULL as they go in case of intermediate failure. This\npatch changes the approach to filling them all with NULL at the start\ninstead, rather than handling that manually during failure.\n\n(cherry picked from commit 08889b706d4f0b8d2352b7ca29c2d8df4d0787cd)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-71130"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0336188cc85d0eab8463bd1bbd4ded4e9602de8b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/24d55ac8e31d2f8197bfad71ffcb3bae21ed7117"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/25d69e07770745992387c016613fd7ac8eaf9893"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4fe2bd195435e71c117983d87f278112c5ab364c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/63f23aa2fbb823c8b15a29269fde220d227ce5b3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-457", "CWE-476" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-01-14T15:16:02Z"
  }
}