Skip to main content
VulnerabilityPublished Updated

CVE-2026-43280: Linux kernel · Out-of-bounds Read

Source GCVE Database

0
Authoritative record:CVE-2026-43280· High 7.1

Not known to be exploited · CVSS 7.1 High · fixed in ffba51100ff61792fefbae11ca38ac1987a818dd : patch Linux kernel soon.

Data as of 27 Oct 2026, 00:07 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in ffba51100ff61792fefbae11ca38ac1987a818dd, fbbe32618e97eff81577a01eb7d9adcd64a216d7, 79f52655567a6471ff3d0d6325ede91bb14461f4
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to ffba51100ff61792fefbae11ca38ac1987a818dd, fbbe32618e97eff81577a01eb7d9adcd64a216d7 or 79f52655567a6471ff3d0d6325ede91bb14461f4.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ada7486c5668db542a7d361268df931aca5b726a, < ffba51100ff61792fefbae11ca38ac1987a818dd
Fixed in
  • ffba51100ff61792fefbae11ca38ac1987a818dd
LinuxLinuxAffected
  • ≥ ada7486c5668db542a7d361268df931aca5b726a, < fbbe32618e97eff81577a01eb7d9adcd64a216d7
Fixed in
  • fbbe32618e97eff81577a01eb7d9adcd64a216d7
LinuxLinuxAffected
  • ≥ ada7486c5668db542a7d361268df931aca5b726a, < 79f52655567a6471ff3d0d6325ede91bb14461f4
Fixed in
  • 79f52655567a6471ff3d0d6325ede91bb14461f4
LinuxLinuxAffected
  • =6.18
Fixed in–

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)

References

Community reviews

Loading reviews…