drm/xe/migrate: don't overflow max copy size

{
  "id": "9322c660a677c2434d63c0bbcffa8a01aa1f62693143cef0135be68b0d151341",
  "url": "https://osv.dev/vulnerability/CVE-2025-39741",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "drm/xe/migrate: don't overflow max copy size",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: drm/xe/migrate: don't overflow max copy size With non-page aligned copy, we need to use 4 byte aligned pitch, however the size itself might still be close to our maximum of ~8M, and so the dimensions of the copy can easily exceed the S16_MAX limit of the copy command leading to the following assert: xe 0000:03:00.0: [drm] Assertion `size / pitch <= ((s16)(((u16)~0U) >> 1))` failed! platform: BATTLEMAGE subplatform: 1 graphics: Xe2_HPG 20.01 step A0 media: Xe2_HPM 13.01 step A1 tile: 0 VRAM 10.0 GiB GT: 0 type 1 WARNING: CPU: 23 PID: 10605 at drivers/gpu/drm/xe/xe_migrate.c:673 emit_copy+0x4b5/0x4e0 [xe] To fix this account for the pitch when calculating the number of current bytes to copy. (cherry picked from commit 8c2d61e0e916e077fda7e7b8e67f25ffe0f361fc)",
    "evidence": "osv:CVE-2025-39741",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.16.2",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2025-39741",
      "aliases": [
        "CVE-2025-39741"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "270172f64b114451876c1b68912653e72ab99f38"
                },
                {
                  "fixed": "7257cc6644d540130a46a61531a07a0517cace89"
                },
                {
                  "fixed": "4126cb327a2e3273c81fcef1c594c5b7b645c44c"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-39741.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.16.0"
                },
                {
                  "fixed": "6.16.2"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-39741.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:26.337432163Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/4126cb327a2e3273c81fcef1c594c5b7b645c44c",
        "https://git.kernel.org/stable/c/7257cc6644d540130a46a61531a07a0517cace89",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/39xxx/CVE-2025-39741.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-39741",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/39xxx/CVE-2025-39741.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-39741",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 493045,
  "published_at": "2025-09-11T16:52:15.353+00:00"
}