---
title: "CVE-2026-90341: Linux kernel firmware coreboot - Memory Bounds Validation"
description: "Linux kernel firmware coreboot contains a memory bounds validation vulnerability caused by improper size and header checks in coreboot_table_probe, letting attackers cause out-of-bounds memory mapping, exploit requires crafted firmware tables."
url: https://panop.io/threat-heartbeat/CVE-2026-90341/
---

# CVE-2026-90341 Linux kernel firmware coreboot - Memory Bounds Validation

Linux kernel firmware coreboot contains a memory bounds validation vulnerability caused by improper size and header checks in coreboot\_table\_probe, letting attackers cause out-of-bounds memory mapping, exploit requires crafted firmware tables.

CVSS base score 7.7 /10

High

CISA KEV

Not listed

Public exploit

None known

EPSS

0.19% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-90341)

## Details

Type

Memory Bounds Validation

Impact

Information Disclosure, Denial Of Service

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Published

17 September 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version with coreboot table bounds validation fixes.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-90341](https://nvd.nist.gov/vuln/detail/CVE-2026-90341)
- [https://git.kernel.org/stable/c/88027241c1d2c3213bac937a1c2cb89a5775a413](https://git.kernel.org/stable/c/88027241c1d2c3213bac937a1c2cb89a5775a413)
- [https://git.kernel.org/stable/c/a58a57a1076f8c5dae0327e3710899478c3be901](https://git.kernel.org/stable/c/a58a57a1076f8c5dae0327e3710899478c3be901)
- [https://git.kernel.org/stable/c/d848fac90c6f0566e7b93066b0b86024f65f395e](https://git.kernel.org/stable/c/d848fac90c6f0566e7b93066b0b86024f65f395e)
- [https://git.kernel.org/stable/c/e82f260a74dea8cdd7857f2cc66f73d0da522bb3](https://git.kernel.org/stable/c/e82f260a74dea8cdd7857f2cc66f73d0da522bb3)
- [https://git.kernel.org/stable/c/f79f621215a0944c4a0e1b3b86b99e433ae8c527](https://git.kernel.org/stable/c/f79f621215a0944c4a0e1b3b86b99e433ae8c527)
- [https://git.kernel.org/stable/c/fd93859ecfa5b6495a6863c18fd923a7666def26](https://git.kernel.org/stable/c/fd93859ecfa5b6495a6863c18fd923a7666def26)
- [https://git.kernel.org/stable/c/2d98a3b89394f283f054a4a54587c14ee89acaf9](https://git.kernel.org/stable/c/2d98a3b89394f283f054a4a54587c14ee89acaf9)
- [https://git.kernel.org/stable/c/3cca0d6dd4c2636d2514234233cb02db76621607](https://git.kernel.org/stable/c/3cca0d6dd4c2636d2514234233cb02db76621607)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)