Skip to content
Heist/ feed
Back to feed
HighFix available

drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise

Type: advisorySources: OSV

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)

Products
Kernel
Affected versions
Not specified
Fixed versions
6.18.16, 6.19.6
CVEs
CVE-2026-43280
Confirmed fixed CVEs
Not specified
Updated in this feed
5 Nov 2026, 00:55 UTC · Revision 1

Source evidence

drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise

core-osv · Original source

Published 6 May 2026, 11:29 UTC

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)

osv:CVE-2026-43280

Kernel

Fixed versions: 6.18.16, 6.19.6

Complete source record
{
  "id": "f533d884f628cf48205362d1b7430cd1e20ffe43bf832a0b41815de2de906baa",
  "url": "https://osv.dev/vulnerability/CVE-2026-43280",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise",
    "summary": "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)",
    "evidence": "osv:CVE-2026-43280",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.18.16",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.19.6",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2026-43280",
      "aliases": [
        "CVE-2026-43280"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "ada7486c5668db542a7d361268df931aca5b726a"
                },
                {
                  "fixed": "ffba51100ff61792fefbae11ca38ac1987a818dd"
                },
                {
                  "fixed": "79f52655567a6471ff3d0d6325ede91bb14461f4"
                },
                {
                  "fixed": "fbbe32618e97eff81577a01eb7d9adcd64a216d7"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43280.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.18.0"
                },
                {
                  "fixed": "6.18.16"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "6.19.6"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43280.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:41.076584564Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/79f52655567a6471ff3d0d6325ede91bb14461f4",
        "https://git.kernel.org/stable/c/fbbe32618e97eff81577a01eb7d9adcd64a216d7",
        "https://git.kernel.org/stable/c/ffba51100ff61792fefbae11ca38ac1987a818dd",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43280.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-43280",
        "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/2026/43xxx/CVE-2026-43280.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-43280",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 508757,
  "published_at": "2026-05-06T11:29:01.562+00:00"
}