Home/CVE/drivers/gpu/drm/i915/i915_gem.c in the Graphics Execution Manager (GEM) in the Intel i915 driver in the Direct Rendering
CVE

CVE-2010-2962

drivers/gpu/drm/i915/i915_gem.c in the Graphics Execution Manager (GEM) in the Intel i915 driver in the Direct Rendering

drivers/gpu/drm/i915/i915_gem.c in the Graphics Execution Manager (GEM) in the Intel i915 driver in the Direct Rendering Manager (DRM) subsystem in the Linux kernel before 2.6.36 does not properly validate pointers to blocks of memory, which allows local users to write to arbitrary kernel memory locations, and consequently gain privileges, via crafted use of the ioctl interface, related to (1) pwrite and (2) pread operations.

HIGH · CVSS 7.2 EPSS 0.00483
EPSS exploitation odds0.48% · top 61%
Schedule remediation
  • CVSS base score ≥ 7.0
Look this up elsewhere - one-click external pivots
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2010-2962, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

Severity & exploitation scoring

CVSS base score
7.2
HIGHCVSS v3.1 · [email protected]
EPSS exploitation probability
0.48%
Top 61%odds of exploitation in the next 30 days
CVSS metric silhouette
No structured CVSS vector for this CVE. Older entries often have only a numeric base score - the metric breakdown radar requires a full AV:_/AC:_/... vector string published by NVD.
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
Lifecycle
  1. 26 Nov 2010Published to NVD
  2. 16 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain

ATT&CK techniques

1

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small marks a technique that N independent sources agree on.

▤ Build a SIEM detection for these techniques

Weakness Classification

Affected Products & Versions

7
📦

Fixed versions by distribution

21
The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
oracle allkernel open
oracle allkernel-debug open
oracle allkernel-debug-devel fixed in 0:2.6.32-100.24.1.el5
oracle allkernel-devel open
oracle allkernel-firmware open
oracle allkernel-headers fixed in 0:2.6.32-100.24.1.el5
oracle allkernel-uek open
oracle allkernel-uek-debug fixed in 0:2.6.32-300.7.1.el6uek
oracle allkernel-uek-debug-devel fixed in 0:2.6.32-300.7.1.el5uek
oracle allkernel-uek-devel open
oracle allkernel-uek-firmware fixed in 0:2.6.32-300.7.1.el6uek
oracle allkernel-uek-headers fixed in 0:2.6.32-300.7.1.el5uek
oracle allmlnx_en-2.6.32-300.7.1.el6uek fixed in 0:1.5.7-0.1
oracle allmlnx_en-2.6.32-300.7.1.el6uekdebug open
oracle allofa-2.6.32-100.24.1.el5 fixed in 0:1.5.1-4.0.23
oracle allofa-2.6.32-100.24.1.el5debug fixed in 0:1.5.1-4.0.23
oracle allofa-2.6.32-300.7.1.el5uek open
oracle allofa-2.6.32-300.7.1.el5uekdebug open
oracle allofa-2.6.32-300.7.1.el6uek fixed in 0:1.5.1-4.0.47
oracle allofa-2.6.32-300.7.1.el6uekdebug fixed in 0:1.5.1-4.0.47
oracle allperf fixed in 0:2.6.32-71.14.1.el6

Vendor Advisories

9
rhsaRHSA-2010:0842Moderate