Skip to content
Fencer Intel
medium 4.9

CVE-2012-2384 json

Integer overflow in the i915_gem_do_execbuffer function in drivers/gpu/drm/i915/i915_gem_execbuffer.c in the Direct Rendering Manager (DRM)…

published 2012-06-13 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2372

cvss
4.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits
0
none known

Summary

Integer overflow in the i915_gem_do_execbuffer function in drivers/gpu/drm/i915/i915_gem_execbuffer.c in the Direct Rendering Manager (DRM) subsystem in the Linux kernel before 3.3.5 on 32-bit platforms allows local users to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact via a crafted ioctl call.

Patch / fix

  • kernel RHEL 6 2.6.32-279.9.1.el6
  • perf RHEL 6 2.6.32-279.9.1.el6
  • python-perf RHEL 6 2.6.32-279.9.1.el6
  • kernel-kdump RHEL 6 2.6.32-279.9.1.el6
  • kernel-firmware RHEL 6 2.6.32-279.9.1.el6
  • kernel-bootwrapper RHEL 6 2.6.32-279.9.1.el6
  • kernel-debuginfo-common-i686 RHEL 6 2.6.32-279.9.1.el6
  • kernel-debuginfo-common-ppc64 RHEL 6 2.6.32-279.9.1.el6

red hat advisories RHSA-2012:1304

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-2384 updated cvss 4.9

kernel: drm/i915: integer overflow in i915_gem_do_execbuffer()

  • Red Hat Enterprise Linux Desktop (v. 6) perf 2.6.32-279.9.1.el6, kernel 2.6.32-279.9.1.el6, kernel-firmware 2.6.32-279.9.1.el6, kernel-debuginfo-common-i686 2.6.32-279.9.1.el6, kernel-debuginfo-common-x86_64 2.6.32-279.9.1.el6 Red Hat Enterprise Linux Desktop Optional (v. 6) kernel 2.6.32-279.9.1.el6, python-perf 2.6.32-279.9.1.el6, kernel-debuginfo-common-i686 2.6.32-279.9.1.el6, kernel-debuginfo-common-x86_64 2.6.32-279.9.1.el6 Red Hat Enterprise Linux HPC Node (v. 6) perf 2.6.32-279.9.1.el6, kernel 2.6.32-279.9.1.el6, kernel-firmware 2.6.32-279.9.1.el6, kernel-debuginfo-common-x86_64 2.6.32-279.9.1.el6 Red Hat Enterprise Linux HPC Node Optional (v. 6) kernel 2.6.32-279.9.1.el6, python-perf 2.6.32-279.9.1.el6, kernel-debuginfo-common-x86_64 2.6.32-279.9.1.el6 Red Hat Enterprise Linux Server (v. 6) perf 2.6.32-279.9.1.el6, kernel 2.6.32-279.9.1.el6, kernel-kdump 2.6.32-279.9.1.el6, kernel-firmware 2.6.32-279.9.1.el6, kernel-bootwrapper 2.6.32-279.9.1.el6, kernel-debuginfo-common-i686 2.6.32-279.9.1.el6, +3 more Red Hat Enterprise Linux Server Optional (v. 6) kernel 2.6.32-279.9.1.el6, python-perf 2.6.32-279.9.1.el6, kernel-debuginfo-common-i686 2.6.32-279.9.1.el6, kernel-debuginfo-common-ppc64 2.6.32-279.9.1.el6, kernel-debuginfo-common-s390x 2.6.32-279.9.1.el6, kernel-debuginfo-common-x86_64 2.6.32-279.9.1.el6
    +2 more products
    Red Hat Enterprise Linux Workstation (v. 6) perf 2.6.32-279.9.1.el6, kernel 2.6.32-279.9.1.el6, kernel-firmware 2.6.32-279.9.1.el6, kernel-debuginfo-common-i686 2.6.32-279.9.1.el6, kernel-debuginfo-common-x86_64 2.6.32-279.9.1.el6 Red Hat Enterprise Linux Workstation Optional (v. 6) kernel 2.6.32-279.9.1.el6, python-perf 2.6.32-279.9.1.el6, kernel-debuginfo-common-i686 2.6.32-279.9.1.el6, kernel-debuginfo-common-x86_64 2.6.32-279.9.1.el6
    fixed: vendor fix RHSA-2012:1304
  • Red Hat Enterprise Linux 5 kernel Red Hat Enterprise MRG 2 kernel-rt, mrg-rt-release, kernel-rt-trace, kernel-rt-vanilla, kernel-rt-firmware
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.9 AV:L/AC:L/Au:N/C:N/I:N/A:C

Classification

Weakness
Technology feeds

References

Sources

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.