Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 251185 - (CVE-2007-3851) CVE-2007-3851 i965 DRM allows insecure packets
CVE-2007-3851 i965 DRM allows insecure packets
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
high Severity high
: ---
: ---
Assigned To: Aristeu Rozanski
: Security
Depends On: 251188 252305
  Show dependency treegraph
Reported: 2007-08-07 12:59 EDT by Marcel Holtmann
Modified: 2012-05-02 11:11 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-05-02 11:11:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2007:0705 normal SHIPPED_LIVE Important: kernel security update 2007-09-13 05:21:22 EDT

  None (edit)
Description Marcel Holtmann 2007-08-07 12:59:33 EDT
The Intel 965 and above chipsets moved the batch buffer security bit to
another place, this means the current DRM allows commands that can touch
any part of main memory to be submitted on those chipsets. The user
requires to be logged onto a local X server and have access to the drm. 

a) which users typically have access to the drm?  Anyone?

There is an xorg config option to set the permissions, but typically
only the logged in user on the primary X server can actually do anything
as there is a separate authentication processes, so usually the user
already has physical access at that point..

b) what actually can they do with it?  Modify arbitrary physical
   addresses with user-provided data?  Or something less bad?

Transfer user data to any physcial memory address...

The documentation required to actually exploit this bug isn't publicly

Note You need to log in before you can comment on or make changes to this bug.