LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42259: drm/i915/gem: Fix Virtual Memory mapping boundaries calculation

In the Linux kernel, the following vulnerability has been resolved: drm/i915/gem: Fix Virtual Memory mapping boundaries calculation Calculating the size of the mapped area as the lesser value between the requested size and the actual size does not consider the partial mapping offset. This can cause page fault access. Fix the calculation of the starting and ending addresses, the total size is now deduced from the difference between the end and start addresses. Additionally, the calculations have been rewritten in a clearer and more understandable form. [Joonas: Add Requires: tag] Requires: 60a2066c5005 ("drm/i915/gem: Adjust vma offset for framebuffer mmap offset") (cherry picked from commit 97b6784753da06d9d40232328efc5c5367e53417)

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-42259 is a Linux kernel issue in the Intel i915 graphics memory-mapping path. A boundary calculation can be wrong when a partial mapping offset is used, causing page-fault access. The public sources do not provide CVSS, CWE, confirmed exploitation, or a complete impact statement.

Executive priority

Treat this as a kernel maintenance item requiring timely patch verification, not an emergency exploitation event. Priority should rise for shared workstations, multi-user Linux hosts, and vendor appliances where kernel patching lags.

Technical view

The flaw is in drm/i915/gem virtual memory mapping boundary calculation. The original logic used the lesser of requested and actual size without accounting for partial mapping offset. Stable kernel fixes recalculate start and end addresses, then derive total mapped size from their difference.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions with the drm/i915 GEM path present. The source lists affected Linux version ranges and multiple stable fix commits, but does not provide distribution-by-distribution exposure details.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. A Project Zero issue is referenced, but the bundle does not establish public exploitation, exploit maturity, or remote attackability.

Researcher notes

Key uncertainty is impact. The advisory says the bug can cause page-fault access, but does not state confidentiality, integrity, availability, privilege escalation, or attack preconditions. Validate by code lineage and backport presence, not by version strings alone.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes or backports.
  • Review Debian LTS and appliance vendor advisories for packaged kernel status.
  • Prioritize systems with Intel i915 graphics enabled or exposed to untrusted local users.
  • If no vendor package is available, monitor vendor guidance before custom kernel changes.

Validation and detection

  • Inventory kernel versions against the affected and fixed versions in vendor advisories.
  • Confirm installed kernels include one of the referenced stable fix commits or backports.
  • Check whether drm/i915 is enabled or loaded on potentially affected Linux systems.
  • Document exceptions where systems are not running affected kernels or i915 paths.
Prepared
Confidence
medium
Sources
12

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-2024-42259 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
3Timeline events
3ADP providers
13Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc58305af1835095ddc25ee6f548ac05915e66ac5, c58305af1835095ddc25ee6f548ac05915e66ac5, c58305af1835095ddc25ee6f548ac05915e66ac5, c58305af1835095ddc25ee6f548ac05915e66ac5, c58305af1835095ddc25ee6f548ac05915e66ac5, c58305af1835095ddc25ee6f548ac05915e66ac5, c58305af1835095ddc25ee6f548ac05915e66ac5, c58305af1835095ddc25ee6f548ac05915e66ac5unaffected
LinuxLinux4.9, 0, 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.106, 6.6.46, 6.10.5, 6.11affected
Weakness

CWE details

No CWE listed

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