CVE-2026-64097High· 7.8▾ TwilightIn 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() deri…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 42.9 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.1%
Last analysed / modified upstream
0.1% → 0.1%
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)
Linux >= ae79c310b1a6f97429a5784b65f125d9cc9c95b1 < 9900f6954be779011e7c2cd42addd87baf028bc5Linux >= ae79c310b1a6f97429a5784b65f125d9cc9c95b1 < fb30a3890d62fd50a95aef684faf64a307592e42Linux >= ae79c310b1a6f97429a5784b65f125d9cc9c95b1 < 67461e0c15335894cc5d3b84cda823bf8cbdc886Linux >= ae79c310b1a6f97429a5784b65f125d9cc9c95b1 < 7ca695b3122297b06a3ed605bbe1cd32c85d9f5aLinux >= ae79c310b1a6f97429a5784b65f125d9cc9c95b1 < f2a4827e980ba07de4391fa84d9c39a12726bdd7Linux >= ae79c310b1a6f97429a5784b65f125d9cc9c95b1 < 86d2b20644b11d21fe52c596e6e922b4590a3e3fLinux 4.15Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99100Nonewifi: p54: validate firmware record lengths
CVE-2024-38564High· 7.8bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE
CVE-2026-99092Noneriscv: patch: fix handling of bpf-jit execmem addresses
CVE-2026-99089NoneASoC: samsung: i2s: enable op_clk in probe to balance runtime PM
CVE-2026-99093Nonemm: don't schedule deferred kernel page table freeing while booting
CVE-2026-99088Nonenet: openvswitch: validate transport header presence in set_ipv6_addr