CVE-2024-42066 (GCVE-0-2024-42066)

Vulnerability from cvelistv5 – Published: 2024-07-29 15:52 – Updated: 2026-08-05 11:35
VLAI
Title
drm/xe: Fix potential integer overflow in page size calculation
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix potential integer overflow in page size calculation Explicitly cast tbo->page_alignment to u64 before bit-shifting to prevent overflow when assigning to min_page_size.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2024-09-10 16:19 UTC
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: dd08ebf6c3525a7ea2186e636df064ea47281987 , < 79d54ddf0e292b810887994bb04709c5ac0e1531 (git)
Affected: dd08ebf6c3525a7ea2186e636df064ea47281987 , < 4f4fcafde343a54465f85a2909fc684918507a4b (git)
Create a notification for this product.
Linux Linux Affected: 6.8
Unaffected: 0 , < 6.8 (semver)
Unaffected: 6.9.8 , ≤ 6.9.* (semver)
Unaffected: 6.10 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T04:54:31.373Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/79d54ddf0e292b810887994bb04709c5ac0e1531"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/4f4fcafde343a54465f85a2909fc684918507a4b"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-42066",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-09-10T16:19:59.323646Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-09-11T17:32:55.779Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/xe/xe_ttm_vram_mgr.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "79d54ddf0e292b810887994bb04709c5ac0e1531",
              "status": "affected",
              "version": "dd08ebf6c3525a7ea2186e636df064ea47281987",
              "versionType": "git"
            },
            {
              "lessThan": "4f4fcafde343a54465f85a2909fc684918507a4b",
              "status": "affected",
              "version": "dd08ebf6c3525a7ea2186e636df064ea47281987",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/xe/xe_ttm_vram_mgr.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.8"
            },
            {
              "lessThan": "6.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.9.*",
              "status": "unaffected",
              "version": "6.9.8",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.10",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.9.8",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.10",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe: Fix potential integer overflow in page size calculation\n\nExplicitly cast tbo-\u003epage_alignment to u64 before bit-shifting to\nprevent overflow when assigning to min_page_size."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The code is reached only through the DRM_IOCTL_XE_GEM_CREATE ioctl on the local /dev/dri/renderD* node, which drives TTM BO validation into xe_ttm_vram_mgr_new(). There is no remote or network-facing path into the xe VRAM manager.\nAC:L - The triggering sequence is a single deterministic ioctl with no race window, no memory-layout dependency, and no reliance on victim state. Per the guidance, the absence of any attacker-controlled race or unpredictable precondition in the call sequence makes this Low.\nPR:L - The ioctl is DRM_RENDER_ALLOW, so it needs neither DRM master nor any capability \u2014 an ordinary local account with render-node access (default for desktop sessions via logind, and for apps on Android/embedded GPU stacks) suffices. Real root is not required.\nUI:N - The attacker performs the GEM create ioctl entirely on their own; no victim must open a file, mount a filesystem, or take any other action.\nS:U - The truncated min_page_size affects VRAM buddy allocation inside the same kernel security authority that already manages the requesting process\u0027s buffers. No IOMMU, hypervisor, or sandbox boundary is crossed.\nC:H - A nonzero truncated min_page_size yields a VRAM allocation under-aligned relative to the hardware\u0027s 64K page requirement, so GPU page-table entries can cover VRAM belonging to other buffer objects, exposing another client\u0027s GPU memory contents. Treated as High per the guidance that memory-safety defects leveragable for disclosure score H.\nI:H - The same under-aligned mapping is writable by the GPU, allowing writes past the intended buffer into neighbouring VRAM belonging to other contexts, which is an out-of-bounds write primitive in device memory. Out-of-bounds writes score High.\nA:H - Truncation of the shift to exactly zero lands in WARN_ON(min_page_size \u003c mm-\u003echunk_size), producing a kernel warning that panics outright on the panic_on_warn configurations common in hardened, CI, and cloud kernels; corrupted VRAM mappings also produce GPU hangs and resets. Any kernel crash or hang scores High."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:35:24.979Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/79d54ddf0e292b810887994bb04709c5ac0e1531"
        },
        {
          "url": "https://git.kernel.org/stable/c/4f4fcafde343a54465f85a2909fc684918507a4b"
        }
      ],
      "title": "drm/xe: Fix potential integer overflow in page size calculation",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-42066",
    "datePublished": "2024-07-29T15:52:30.984Z",
    "dateReserved": "2024-07-29T15:50:41.167Z",
    "dateUpdated": "2026-08-05T11:35:24.979Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-42066",
      "date": "2026-11-19",
      "epss": "0.00218",
      "percentile": "0.12429"
    },
    "microsoft_vex": {
      "current_release_date": "2026-11-05T14:57:23.000Z",
      "cve": "CVE-2024-42066",
      "id": "msrc_CVE-2024-42066",
      "initial_release_date": "2025-09-03T21:47:12.000Z",
      "product_status:under_investigation": "28",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "drm/xe: Fix potential integer overflow in page size calculation",
      "url": "https://msrc.microsoft.com/csaf/vex/2025/msrc_cve-2024-42066.json",
      "version": "21"
    },
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-11-07T10:45:16+00:00",
      "cve": "CVE-2024-42066",
      "id": "CVE-2024-42066",
      "initial_release_date": "2024-07-29T00:00:00+00:00",
      "product_status:known_not_affected": "199",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: drm/xe: Fix potential integer overflow in page size calculation",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-42066.json",
      "version": "3"
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "providerMetadata": {
              "dateUpdated": "2024-08-02T04:54:31.373Z",
              "orgId": "af854a3a-2127-422b-91ae-364da2661108",
              "shortName": "CVE"
            },
            "references": [
              {
                "tags": [
                  "x_transferred"
                ],
                "url": "https://git.kernel.org/stable/c/79d54ddf0e292b810887994bb04709c5ac0e1531"
              },
              {
                "tags": [
                  "x_transferred"
                ],
                "url": "https://git.kernel.org/stable/c/4f4fcafde343a54465f85a2909fc684918507a4b"
              }
            ],
            "title": "CVE Program Container"
          },
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2024-42066",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2024-09-10T16:19:59.323646Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2024-09-11T12:42:13.586Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "defaultStatus": "unaffected",
              "product": "Linux",
              "programFiles": [
                "drivers/gpu/drm/xe/xe_ttm_vram_mgr.c"
              ],
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "vendor": "Linux",
              "versions": [
                {
                  "lessThan": "79d54ddf0e292b810887994bb04709c5ac0e1531",
                  "status": "affected",
                  "version": "dd08ebf6c3525a7ea2186e636df064ea47281987",
                  "versionType": "git"
                },
                {
                  "lessThan": "4f4fcafde343a54465f85a2909fc684918507a4b",
                  "status": "affected",
                  "version": "dd08ebf6c3525a7ea2186e636df064ea47281987",
                  "versionType": "git"
                }
              ]
            },
            {
              "defaultStatus": "affected",
              "product": "Linux",
              "programFiles": [
                "drivers/gpu/drm/xe/xe_ttm_vram_mgr.c"
              ],
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "vendor": "Linux",
              "versions": [
                {
                  "status": "affected",
                  "version": "6.8"
                },
                {
                  "lessThan": "6.8",
                  "status": "unaffected",
                  "version": "0",
                  "versionType": "semver"
                },
                {
                  "lessThanOrEqual": "6.9.*",
                  "status": "unaffected",
                  "version": "6.9.8",
                  "versionType": "semver"
                },
                {
                  "lessThanOrEqual": "*",
                  "status": "unaffected",
                  "version": "6.10",
                  "versionType": "original_commit_for_fix"
                }
              ]
            }
          ],
          "cpeApplicability": [
            {
              "nodes": [
                {
                  "cpeMatch": [
                    {
                      "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "6.9.8",
                      "versionStartIncluding": "6.8",
                      "vulnerable": true
                    },
                    {
                      "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                      "versionEndExcluding": "6.10",
                      "versionStartIncluding": "6.8",
                      "vulnerable": true
                    }
                  ],
                  "negate": false,
                  "operator": "OR"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe: Fix potential integer overflow in page size calculation\n\nExplicitly cast tbo-\u003epage_alignment to u64 before bit-shifting to\nprevent overflow when assigning to min_page_size."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 7.8,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
                "version": "3.1"
              },
              "scenarios": [
                {
                  "lang": "en",
                  "value": "AV:L - The code is reached only through the DRM_IOCTL_XE_GEM_CREATE ioctl on the local /dev/dri/renderD* node, which drives TTM BO validation into xe_ttm_vram_mgr_new(). There is no remote or network-facing path into the xe VRAM manager.\nAC:L - The triggering sequence is a single deterministic ioctl with no race window, no memory-layout dependency, and no reliance on victim state. Per the guidance, the absence of any attacker-controlled race or unpredictable precondition in the call sequence makes this Low.\nPR:L - The ioctl is DRM_RENDER_ALLOW, so it needs neither DRM master nor any capability \u2014 an ordinary local account with render-node access (default for desktop sessions via logind, and for apps on Android/embedded GPU stacks) suffices. Real root is not required.\nUI:N - The attacker performs the GEM create ioctl entirely on their own; no victim must open a file, mount a filesystem, or take any other action.\nS:U - The truncated min_page_size affects VRAM buddy allocation inside the same kernel security authority that already manages the requesting process\u0027s buffers. No IOMMU, hypervisor, or sandbox boundary is crossed.\nC:H - A nonzero truncated min_page_size yields a VRAM allocation under-aligned relative to the hardware\u0027s 64K page requirement, so GPU page-table entries can cover VRAM belonging to other buffer objects, exposing another client\u0027s GPU memory contents. Treated as High per the guidance that memory-safety defects leveragable for disclosure score H.\nI:H - The same under-aligned mapping is writable by the GPU, allowing writes past the intended buffer into neighbouring VRAM belonging to other contexts, which is an out-of-bounds write primitive in device memory. Out-of-bounds writes score High.\nA:H - Truncation of the shift to exactly zero lands in WARN_ON(min_page_size \u003c mm-\u003echunk_size), producing a kernel warning that panics outright on the panic_on_warn configurations common in hardened, CI, and cloud kernels; corrupted VRAM mappings also produce GPU hangs and resets. Any kernel crash or hang scores High."
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-05T11:35:24.979Z",
            "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "shortName": "Linux"
          },
          "references": [
            {
              "url": "https://git.kernel.org/stable/c/79d54ddf0e292b810887994bb04709c5ac0e1531"
            },
            {
              "url": "https://git.kernel.org/stable/c/4f4fcafde343a54465f85a2909fc684918507a4b"
            }
          ],
          "title": "drm/xe: Fix potential integer overflow in page size calculation",
          "x_generator": {
            "engine": "bippy-1.2.0"
          }
        }
      },
      "cveMetadata": {
        "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "assignerShortName": "Linux",
        "cveId": "CVE-2024-42066",
        "datePublished": "2024-07-29T15:52:30.984Z",
        "dateReserved": "2024-07-29T15:50:41.167Z",
        "dateUpdated": "2026-08-05T11:35:24.979Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.