Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2025-71130— drm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer

EPSS 0.02% · P5
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2025-71130

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
drm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer
Source: NVD (National Vulnerability Database)
Vulnerability Description
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)
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于未初始化数组,可能导致清理逻辑错误。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 544460c33821b44c2f0c643121303c3dc3f66ef1 ~ 25d69e07770745992387c016613fd7ac8eaf9893 -
LinuxLinux 5.16 -

II. Public POCs for CVE-2025-71130

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-71130

登录查看更多情报信息。

Same Patch Batch · Linux · 2026-01-14 · 43 CVEs total

CVE-2025-71112net: hns3: add VLAN id validation before using
CVE-2025-71122iommufd/selftest: Check for overflow in IOMMU_TEST_OP_ADD_RESERVED
CVE-2025-71108usb: typec: ucsi: Handle incorrect num_connectors capability
CVE-2025-71110mm/slub: reset KASAN tag in defer_free() before accessing freed memory
CVE-2025-71109MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits
CVE-2025-71105f2fs: use global inline_xattr_slab instead of per-sb slab cache
CVE-2025-71104KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer
CVE-2025-71103drm/msm: adreno: fix deferencing ifpc_reglist when not declared
CVE-2025-71102scs: fix a wrong parameter in __scs_magic
CVE-2025-71106fs: PM: Fix reverse check in filesystems_freeze_callback()
CVE-2025-71111hwmon: (w83791d) Convert macros to functions to avoid TOCTOU
CVE-2025-71113crypto: af_alg - zero initialize memory allocated via sock_kmalloc
CVE-2025-71114via_wdt: fix critical boot hang due to unnamed resource allocation
CVE-2025-71115um: init cpu_tasks[] earlier
CVE-2025-71116libceph: make decode_pool() more resilient against corrupted osdmaps
CVE-2025-71117block: Remove queue freezing from several sysfs store callbacks
CVE-2025-71118ACPICA: Avoid walking the Namespace if start_node is NULL
CVE-2025-71120SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf
CVE-2025-71119powerpc/kexec: Enable SMT before waking offline CPUs
CVE-2025-71121parisc: Do not reprogram affinitiy on ASP chip

Showing top 20 of 43 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2025-71130

Anonymous User
2026-01-15 06:08:11

Zaproxy alias impedit expedita quisquam pariatur exercitationem. Nemo rerum eveniet dolores rem quia dignissimos.


Leave a comment