CVE-2022-49963 (GCVE-0-2022-49963)

Vulnerability from cvelistv5 – Published: 2025-06-18 11:00 – Updated: 2026-08-05 08:56
VLAI
Title
drm/i915/ttm: fix CCS handling
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/i915/ttm: fix CCS handling Crucible + recent Mesa seems to sometimes hit: GEM_BUG_ON(num_ccs_blks > NUM_CCS_BLKS_PER_XFER) And it looks like we can also trigger this with gem_lmem_swapping, if we modify the test to use slightly larger object sizes. Looking closer it looks like we have the following issues in migrate_copy(): - We are using plain integer in various places, which we can easily overflow with a large object. - We pass the entire object size (when the src is lmem) into emit_pte() and then try to copy it, which doesn't work, since we only have a few fixed sized windows in which to map the pages and perform the copy. With an object > 8M we therefore aren't properly copying the pages. And then with an object > 64M we trigger the GEM_BUG_ON(num_ccs_blks > NUM_CCS_BLKS_PER_XFER). So it looks like our copy handling for any object > 8M (which is our CHUNK_SZ) is currently broken on DG2. Testcase: igt@gem_lmem_swapping (cherry picked from commit 8676145eb2f53a9940ff70910caf0125bd8a4bc2)
Assigner
Impacted products
Vendor Product Version
Linux Linux Affected: da0595ae91da837929a00470ab40546090e5b9ae , < 97434cb55bd884bd268626ec41489f79b261b2d4 (git)
Affected: da0595ae91da837929a00470ab40546090e5b9ae , < 8d905254162965c8e6be697d82c7dbf5d08f574d (git)
Create a notification for this product.
Linux Linux Affected: 5.19
Unaffected: 0 , < 5.19 (semver)
Unaffected: 5.19.8 , ≤ 5.19.* (semver)
Unaffected: 6.0 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/i915/gt/intel_migrate.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "97434cb55bd884bd268626ec41489f79b261b2d4",
              "status": "affected",
              "version": "da0595ae91da837929a00470ab40546090e5b9ae",
              "versionType": "git"
            },
            {
              "lessThan": "8d905254162965c8e6be697d82c7dbf5d08f574d",
              "status": "affected",
              "version": "da0595ae91da837929a00470ab40546090e5b9ae",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/i915/gt/intel_migrate.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.19"
            },
            {
              "lessThan": "5.19",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.19.*",
              "status": "unaffected",
              "version": "5.19.8",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.19.8",
                  "versionStartIncluding": "5.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.0",
                  "versionStartIncluding": "5.19",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/ttm: fix CCS handling\n\nCrucible + recent Mesa seems to sometimes hit:\n\nGEM_BUG_ON(num_ccs_blks \u003e NUM_CCS_BLKS_PER_XFER)\n\nAnd it looks like we can also trigger this with gem_lmem_swapping, if we\nmodify the test to use slightly larger object sizes.\n\nLooking closer it looks like we have the following issues in\nmigrate_copy():\n\n  - We are using plain integer in various places, which we can easily\n    overflow with a large object.\n\n  - We pass the entire object size (when the src is lmem) into\n    emit_pte() and then try to copy it, which doesn\u0027t work, since we\n    only have a few fixed sized windows in which to map the pages and\n    perform the copy. With an object \u003e 8M we therefore aren\u0027t properly\n    copying the pages. And then with an object \u003e 64M we trigger the\n    GEM_BUG_ON(num_ccs_blks \u003e NUM_CCS_BLKS_PER_XFER).\n\nSo it looks like our copy handling for any object \u003e 8M (which is our\nCHUNK_SZ) is currently broken on DG2.\n\nTestcase: igt@gem_lmem_swapping\n(cherry picked from commit 8676145eb2f53a9940ff70910caf0125bd8a4bc2)"
        }
      ],
      "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 bug is reached via i915 GEM ioctls on a local DRM render node (GEM_CREATE_EXT of lmem-only objects plus TTM eviction into intel_context_migrate_copy), not via network packet processing.\nAC:L - An attacker can reliably create Flat-CCS lmem objects larger than CHUNK_SZ (8M) and force lmem pressure to trigger eviction; the failure is deterministic once migrate_copy runs on such an object, as shown by gem_lmem_swapping and Mesa/Crucible hits.\nPR:L - Triggering requires only unprivileged access to /dev/dri/renderD* (DRM_RENDER_ALLOW for GEM_CREATE_EXT and related ioctls), not root or init-namespace capabilities.\nUI:N - The attacker opens the render node and allocates/evicts their own objects; no separate victim action is required.\nS:U - Impact stays within the host kernel/GPU driver authority (migration PPGTT corruption and GEM buffer corruption), not a guest-to-host or IOMMU-boundary escape.\nC:H - Oversized blits past the fixed 8M windows can read the migrate VM\u2019s self-mapped PTE region and adjacent mappings into attacker-readable smem backup pages, and can mishandle CCS/metadata during eviction of other clients\u2019 buffers under memory pressure.\nI:H - The same oversized XY copy can write past the destination window into the migration page tables and leave incomplete/incorrect main and CCS copies, corrupting GPU PTEs and buffer contents with no CCS-capable CPU memcpy fallback.\nA:H - Out-of-bounds GTT access and invalid CCS transfer sizing can hang or wedge the GPU (and trip GEM_BUG_ON on debug builds), denying GPU service to the system."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T08:56:54.694Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/97434cb55bd884bd268626ec41489f79b261b2d4"
        },
        {
          "url": "https://git.kernel.org/stable/c/8d905254162965c8e6be697d82c7dbf5d08f574d"
        }
      ],
      "title": "drm/i915/ttm: fix CCS handling",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-49963",
    "datePublished": "2025-06-18T11:00:24.021Z",
    "dateReserved": "2025-06-18T10:57:27.384Z",
    "dateUpdated": "2026-08-05T08:56:54.694Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2022-49963",
      "date": "2026-08-12",
      "epss": "0.00189",
      "percentile": "0.08735"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2022-49963\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-06-18T11:15:23.570\",\"lastModified\":\"2026-08-04T10:18:01.137\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/i915/ttm: fix CCS handling\\n\\nCrucible + recent Mesa seems to sometimes hit:\\n\\nGEM_BUG_ON(num_ccs_blks \u003e NUM_CCS_BLKS_PER_XFER)\\n\\nAnd it looks like we can also trigger this with gem_lmem_swapping, if we\\nmodify the test to use slightly larger object sizes.\\n\\nLooking closer it looks like we have the following issues in\\nmigrate_copy():\\n\\n  - We are using plain integer in various places, which we can easily\\n    overflow with a large object.\\n\\n  - We pass the entire object size (when the src is lmem) into\\n    emit_pte() and then try to copy it, which doesn\u0027t work, since we\\n    only have a few fixed sized windows in which to map the pages and\\n    perform the copy. With an object \u003e 8M we therefore aren\u0027t properly\\n    copying the pages. And then with an object \u003e 64M we trigger the\\n    GEM_BUG_ON(num_ccs_blks \u003e NUM_CCS_BLKS_PER_XFER).\\n\\nSo it looks like our copy handling for any object \u003e 8M (which is our\\nCHUNK_SZ) is currently broken on DG2.\\n\\nTestcase: igt@gem_lmem_swapping\\n(cherry picked from commit 8676145eb2f53a9940ff70910caf0125bd8a4bc2)\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm/i915/ttm: correcci\u00f3n del manejo de CCS Crucible + Mesa reciente parece a veces afectar: GEM_BUG_ON(num_ccs_blks \u0026gt; NUM_CCS_BLKS_PER_XFER) Y parece que tambi\u00e9n podemos activar esto con gem_lmem_swapping, si modificamos la prueba para usar tama\u00f1os de objeto ligeramente mayores. Mirando m\u00e1s de cerca, parece que tenemos los siguientes problemas en migration_copy(): - Estamos usando un entero simple en varios lugares, que podemos desbordar f\u00e1cilmente con un objeto grande. - Pasamos el tama\u00f1o completo del objeto (cuando el src es lmem) a emit_pte() y luego intentamos copiarlo, lo cual no funciona, ya que solo tenemos unas pocas ventanas de tama\u00f1o fijo en las que mapear las p\u00e1ginas y realizar la copia. Con un objeto \u0026gt; 8M, por lo tanto, no estamos copiando correctamente las p\u00e1ginas. Y luego, con un objeto \u0026gt; 64M, activamos GEM_BUG_ON(num_ccs_blks \u0026gt; NUM_CCS_BLKS_PER_XFER). Por lo tanto, parece que nuestra gesti\u00f3n de copias para cualquier objeto \u0026gt; 8M (que es nuestro CHUNK_SZ) est\u00e1 actualmente inactiva en DG2. Caso de prueba: igt@gem_lmem_swapping (seleccionado de el commit 8676145eb2f53a9940ff70910caf0125bd8a4bc2)\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/gpu/drm/i915/gt/intel_migrate.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"da0595ae91da837929a00470ab40546090e5b9ae\",\"lessThan\":\"97434cb55bd884bd268626ec41489f79b261b2d4\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"da0595ae91da837929a00470ab40546090e5b9ae\",\"lessThan\":\"8d905254162965c8e6be697d82c7dbf5d08f574d\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/gpu/drm/i915/gt/intel_migrate.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"5.19\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"5.19\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.19.8\",\"lessThanOrEqual\":\"5.19.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.0\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.19\",\"versionEndExcluding\":\"5.19.8\",\"matchCriteriaId\":\"9E795B3E-4D62-43FD-B109-481E9CF5C069\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.0:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"E8BD11A3-8643-49B6-BADE-5029A0117325\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.0:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"5F0AD220-F6A9-4012-8636-155F1B841FAD\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.0:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"A46498B3-78E1-4623-AAE1-94D29A42BE4E\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/8d905254162965c8e6be697d82c7dbf5d08f574d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/97434cb55bd884bd268626ec41489f79b261b2d4\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-08-04T19:41:44+00:00",
      "cve": "CVE-2022-49963",
      "id": "CVE-2022-49963",
      "initial_release_date": "2022-01-01T00:00:00+00:00",
      "product_status:known_affected": "156",
      "product_status:known_not_affected": "118",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: drm/i915/ttm: fix CCS handling",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2022/cve-2022-49963.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-08-05T01:12:07Z",
      "cve": "CVE-2022-49963",
      "id": "CVE-2022-49963",
      "initial_release_date": "2025-06-19T03:45:27Z",
      "product_status:known_affected": "369",
      "product_status:known_not_affected": "347",
      "product_status:recommended": "92",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2022-49963",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2022-49963.json",
      "version": "30"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…