LiveActive security incident?Get immediate response
CVE Record

CVE-2010-5331: In the Linux kernel before 2.6.34, a range check issue in drivers/gpu/drm/radeon/atombios.c could cause an...

In the Linux kernel before 2.6.34, a range check issue in drivers/gpu/drm/radeon/atombios.c could cause an off by one (buffer overflow) problem. NOTE: At least one Linux maintainer believes that this CVE is incorrectly assigned and should be rejected because the value is hard coded and are not user-controllable where it is used

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a potential off-by-one buffer overflow in an old Linux Radeon graphics driver path before kernel 2.6.34. The record also includes a maintainer dispute stating the value may be hard coded and not user-controllable. Business urgency is mainly legacy-system hygiene unless a vendor says your product is affected.

Executive priority

Treat as low immediate urgency but a useful signal for legacy Linux risk. Escalate only if a maintained vendor product in your environment confirms exposure or unsupported pre-2.6.34 kernels remain in production.

Technical view

The issue is described as a range-check error in drivers/gpu/drm/radeon/atombios.c that could cause an off-by-one overflow. The available record provides no CVSS score or CWE, and notes disagreement that the CVE may be incorrectly assigned because the relevant value is not user-controllable.

Likely exposure

Exposure appears limited to very old Linux kernel deployments before 2.6.34 where the Radeon DRM AtomBIOS code is present and relevant. The source bundle does not identify specific affected vendors or products beyond the Linux kernel description.

Exploitation context

No provided source indicates active exploitation, public exploit use, or inclusion in CISA KEV. The maintainer dispute reduces confidence that this is practically exploitable without further vendor analysis.

Researcher notes

The main research issue is CVE validity. The record cites a kernel commit and 2.6.34 changelog but also states a maintainer believes the assignment should be rejected because the value is hard coded and not user-controllable.

Mitigation direction

  • Inventory systems running Linux kernels older than 2.6.34.
  • Check Linux distribution and appliance vendor guidance for CVE-2010-5331.
  • Upgrade legacy kernels where vendor guidance confirms exposure.
  • Prioritize replacement of unsupported systems that cannot receive kernel maintenance.

Validation and detection

  • Confirm kernel versions across servers, appliances, and embedded Linux assets.
  • Identify assets using or shipping the Radeon DRM driver path.
  • Review vendor advisories before marking products affected.
  • Document any unsupported legacy kernel exceptions and compensating controls.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2010-5331 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.