CVE-2026-43280: drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: Add bounds check on patindex to prevent OOB kernel read in madvise
When user provides a bogus patindex value through the madvise IOCTL, the xepatindexgetcohmode() 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 madviseargsaresane() directly calls xepatindexgetcohmode(xe, args->patindex.val) without first checking if patindex is within [0, xe->pat.nentries).
Although xepatindexgetcohmode() has a WARNON to catch this in debug builds, it still performs the unsafe array access in production kernels.
v2(Matthew Auld) - Using arrayindexnospec() 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)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Restrict access to the affected madvise IOCTL interface so only trusted/authorized users can invoke it, reducing the ability to supply a bogus pat_index value that would trigger an out-of-bounds kernel read.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43280?
CVE-2026-43280 has been assigned a high severity level due to the potential for out-of-bounds kernel read operations.
How do I fix CVE-2026-43280?
To fix CVE-2026-43280, update to the latest version of the Linux kernel that includes the bounds check for pat_index.
What systems are affected by CVE-2026-43280?
CVE-2026-43280 specifically affects Linux kernel versions utilizing the drm/xe components.
Can CVE-2026-43280 be exploited remotely?
Exploitation of CVE-2026-43280 requires local access to the system, thus making remote exploitation unlikely.
What is the impact of CVE-2026-43280 on system security?
The impact of CVE-2026-43280 includes potential unauthorized access to sensitive kernel memory.