CVE-2026-64097
Last modified
CVE-2026-64097 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate GPIO pin LUT table size before iterating [Why&How] The GPIO pin table parsers in get_gpio_i2c_info() and bios_parser_get_gpio_pin_info() derive an element count from the VBIOS table_header.structuresize field, then iterate over gpio_pin[] entries. However, GET_IMAGE() only validates that the table header itself fits within the BIOS image. If the VBIOS reports a structuresize larger than the actual mapped data, the loop reads past the end of the BIOS image, causing an out-of-bounds read. Fix this by calling bios_get_image() to validate that the full claimed structuresize is accessible within the BIOS image before entering the loop in both functions. (cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3). EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate GPIO pin LUT table size before iterating [Why&How] The GPIO pin table parsers in get_gpio_i2c_info() and bios_parser_get_gpio_pin_info() derive an element count from the VBIOS table_header.structuresize field, then iterate over gpio_pin[] entries. However, GET_IMAGE() only validates that the table header itself fits within the BIOS image. If the VBIOS reports a structuresize larger than the actual mapped data, the loop reads past the end of the BIOS image, causing an out-of-bounds read. Fix this by calling bios_get_image() to validate that the full claimed structuresize is accessible within the BIOS image before entering the loop in both functions. (cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.15, < 6.1.175 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.142 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.92 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.34 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.11 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64097?
How severe is CVE-2026-64097?
How do I fix CVE-2026-64097?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64091In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64092In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64093In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64094In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64095In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64096In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64098In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64099In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-6410@fastify/static versions 8.0.0 through 9.1.0 allow path trav…5.3
- CVE-2026-64100In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64101In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64102In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-64097?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
