CVE-2010-2803

UnknownEPSS 0.47%

Last modified

CVE-2010-2803 is a vulnerability of currently unknown severity. The drm_ioctl function in drivers/gpu/drm/drm_drv.c in the Direct Rendering Manager (DRM) subsystem in the Linux kernel before 2.6.27.53, 2.6.32.x before 2.6.32.21, 2.6.34.x before 2.6.34.6, and 2.6.35.x before 2.6.35.4 allows local users to obtain potentially sensitive information from kernel memory by requesting a large memory-allocation amount.. EPSS estimates a 0.47% chance of exploitation in the next 30 days.

Description

The drm_ioctl function in drivers/gpu/drm/drm_drv.c in the Direct Rendering Manager (DRM) subsystem in the Linux kernel before 2.6.27.53, 2.6.32.x before 2.6.32.21, 2.6.34.x before 2.6.34.6, and 2.6.35.x before 2.6.35.4 allows local users to obtain potentially sensitive information from kernel memory by requesting a large memory-allocation amount.

Metrics

EPSS Probability
0.47%

36.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
LinuxLinux Kernel< 2.6.27.53
LinuxLinux Kernel>= 2.6.32, < 2.6.32.21
LinuxLinux Kernel>= 2.6.34, < 2.6.34.6
LinuxLinux Kernel>= 2.6.35, < 2.6.35.4
DebianDebian Linux5.0
OpensuseOpensuse11.1
OpensuseOpensuse11.3
SuseLinux Enterprise Desktop11Sp1
SuseLinux Enterprise High Availability Extension11Sp1
SuseLinux Enterprise Real Time11Sp1
SuseLinux Enterprise Server11Sp1

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2010-2803?
The drm_ioctl function in drivers/gpu/drm/drm_drv.c in the Direct Rendering Manager (DRM) subsystem in the Linux kernel before 2.6.27.53, 2.6.32.x before 2.6.32.21, 2.6.34.x before 2.6.34.6, and 2.6.35.x before 2.6.35.4 allows local users to obtain potentially sensitive information from kernel memory by requesting a large memory-allocation amount.
How severe is CVE-2010-2803?
Severity scoring for CVE-2010-2803 is pending analysis. The EPSS model estimates a 0.47% probability of exploitation in the next 30 days.
How do I fix CVE-2010-2803?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2010-2803?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST