CVE-2026-72156

fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header()

N/A
Published: August 15, 2026 at 05:53 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header() mpf_ops_parse_header() reads header_size from the bitstream at MPF_HEADER_SIZE_OFFSET (24). When header_size is zero, the expression *(buf + header_size - 1) reads one byte before the buffer start. Since initial_header_size is set to 71 in mpf_ops, the fpga-mgr core guarantees the buffer is large enough to reach MPF_HEADER_SIZE_OFFSET. The only real gap is the zero header_size case, which cannot be resolved by providing a larger buffer, so return -EINVAL.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.0 ≤ v < 6.1.1786.0 ≤ v < 6.12.976.0 ≤ v < 6.18.406.0 ≤ v < 6.6.1456.0 ≤ v < 7.1.56.0 ≤ v < 7.25f8d4a9008307e0bf210906948953386935d361c6.0
Vendor states this is fixed in 0d3766fecd9b2db39a18b48021c15c522997ec25 (fixed)
Vendor states this is fixed in 3da8eaf5469eda2353b72038d644fabddb848ce1 (fixed)
Vendor states this is fixed in 43a1974da6bc7ce8f4d1dc1d03d56997428c29c3 (fixed)
Vendor states this is fixed in a1baee24df72ec8fd1d6925c1d5162ffff4ee3bf (fixed)
Vendor states this is fixed in c9ef79e34bc1eac4fd59051e5c7b96a74e59d46f (fixed)
Vendor states this is fixed in e45ec24d8e986d79a8e07f49a816c414ad283622 (fixed)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card