cve.bz

CVE-2025-71130 linux linux kernel: NULL Pointer Dereference

5.5 mediumEPSS 0.2%Fix available

Medium (5.5) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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)

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-476 NULL Pointer Dereference
CWE-457 Use of Uninitialized Variable
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-71130 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-71130?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-71130?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-71130 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-71130

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-71130](https://cve.bz/cve/badge/CVE-2025-71130.svg)](https://cve.bz/cve/CVE-2025-71130)

HTML:

<a href="https://cve.bz/cve/CVE-2025-71130"><img src="https://cve.bz/cve/badge/CVE-2025-71130.svg" alt="CVE-2025-71130"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.16 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.160
Linux6.66.6.120
Linux6.126.12.64
Linux6.186.18.4
Linuxlater releases6.19

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11linux-6.16.1.162-1~deb11u1DLA-4476-1
Debian12linux6.1.162-1DEBIAN-CVE-2025-71130 DSA-6127-1
Debian13linux6.12.69-1DEBIAN-CVE-2025-71130 DSA-6126-1
Debian14linux6.18.5-1DEBIAN-CVE-2025-71130
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-71130
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-71130
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-71130
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-71130 USN-8179-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1059.65~22.04.1UBUNTU-CVE-2025-71130 USN-8440-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-71130
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1054.57~22.04.1UBUNTU-CVE-2025-71130 USN-8179-4
Ubuntu22.04:LTSlinux-hwe-6.8, linux-riscv-6.86.8.0-110.110~22.04.1UBUNTU-CVE-2025-71130 USN-8179-3
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1051.51~22.04.1UBUNTU-CVE-2025-71130 USN-8179-3
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-110.110.1~22.04.1UBUNTU-CVE-2025-71130 USN-8179-1
Ubuntu22.04:LTSlinux-nvidia-6.86.8.0-1051.54~22.04.1UBUNTU-CVE-2025-71130 USN-8185-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1049.50~22.04.1UBUNTU-CVE-2025-71130 USN-8203-1
42 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.31.1SUSE-SU-2026:0447-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.26.1SUSE-SU-2026:20615-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_91-150700.1.3.2SUSE-SU-2026:0587-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_91-150700.15.3.1SUSE-SU-2026:0447-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.31.1SUSE-SU-2026:0447-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.31.1.150700.17.21.1SUSE-SU-2026:0447-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150700.53.31.1SUSE-SU-2026:0447-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure, kernel-syms-azure, kernel-source-azure6.4.0-150700.20.27.1SUSE-SU-2026:0472-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.26.1SUSE-SU-2026:20599-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.26.1.160000.2.7SUSE-SU-2026:20599-1
SUSELinux Micro 6.0kernel-default-base6.4.0-39.1.21.16SUSE-SU-2026:20477-1
SUSELinux Micro 6.0kernel-rt, kernel-source-rt6.4.0-40.1SUSE-SU-2026:20845-1
9 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 16.0kernel-default-base6.12.0-160000.26.1.160000.2.7openSUSE-SU-2026:20287-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.26.1openSUSE-SU-2026:20287-1
Alpaquita23linux-lts6.1.161-r0BELL-CVE-2025-71130
Alpaquita25linux-lts6.12.65-r0BELL-CVE-2025-71130
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-71130

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

An uninitialized pointer cleanup bug in the i915 execbuffer path can occur when eb_lookup_vmas fails after eb_add_vma has already stored a vma pointer for the current buffer but the following eb.vma entries still contain non zero uninitialized data. eb_release_vmas uses NULL as the stop marker, so cleanup may continue past the valid entries and dereference poison or stale pointer values, causing a kernel crash. For the CVSS the PR:L is used because a local process with access to the i915 DRM render or primary device can submit execbuffer ioctls, which is lower than full administrator privileges in many desktop and GPU compute deployments. The issue is not network reachable and requires local access to the GPU device node. Impact is at least local denial of service via kernel crash.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtAffected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-71130.

References

Check your stackJSON