CVE-2026-72158: fpga: dfl: add bounds check in dfh_get_param_size()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 012683accbb7d2bcf1264f2a0ecd6aa1dcea4d68, 3b622aa447cf26104f96a8be39539367863bc6b6, 9e8bc49f91f3f81d957c4f1c1f09fe94e2f88f6a.
Low priority for now. Upgrade to Linux Linux 012683accbb7d2bcf1264f2a0ecd6aa1dcea4d68, 3b622aa447cf26104f96a8be39539367863bc6b6, 9e8bc49f91f3f81d957c4f1c1f09fe94e2f88f6a or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: fpga: dfl: add bounds check in dfh_get_param_size() dfh_get_param_size() can return a parameter size larger than the feature region because the loop bounds check is evaluated before incrementing size. If the EOP (End of Parameters) bit is set in the same iteration, the inflated size is returned without re-validation against max. This can cause create_feature_instance() to call memcpy_fromio() with a size exceeding the ioremap'd region when a malicious FPGA device provides crafted DFHv1 parameter headers. Add a bounds check after the size increment to ensure the accumulated size never exceeds the feature boundary.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.3affected
- 4747ab89b4a652f835494fcf8342aaa0efb9b0fd and later · before b2f6220e929b2a43605331d0139e65dc1640c05caffected · git
- 4747ab89b4a652f835494fcf8342aaa0efb9b0fd and later · before 3b622aa447cf26104f96a8be39539367863bc6b6affected · git
- 4747ab89b4a652f835494fcf8342aaa0efb9b0fd and later · before 012683accbb7d2bcf1264f2a0ecd6aa1dcea4d68affected · git
- 4747ab89b4a652f835494fcf8342aaa0efb9b0fd and later · before f3df5386e3bb54626c117bd85e0158d45fb4aea9affected · git
- 4747ab89b4a652f835494fcf8342aaa0efb9b0fd and later · before 9e8bc49f91f3f81d957c4f1c1f09fe94e2f88f6aaffected · git
- before 6.3not affected · semver
- 6.6.145 and later · up to and including 6.6.*not affected · semver
- 6.12.97 and later · up to and including 6.12.*not affected · semver
- 6.18.40 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72155Aug 15, 2026 · mtd: spi-nor: swp: Improve locking user experience0Monitor
- ← EarlierCVE-2026-72156Aug 15, 2026 · fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header()0Monitor
- Later →CVE-2026-72159Aug 15, 2026 · ocfs2: reject non-inline dinodes with i_size and zero i_clusters0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 012683accbb7d2bcf1264f2a0ecd6aa1dcea4d68 | Vendor (CNA) |
| Linux Linux | 3b622aa447cf26104f96a8be39539367863bc6b6 | Vendor (CNA) |
| Linux Linux | 9e8bc49f91f3f81d957c4f1c1f09fe94e2f88f6a | Vendor (CNA) |
| Linux Linux | b2f6220e929b2a43605331d0139e65dc1640c05c | Vendor (CNA) |
| Linux Linux | f3df5386e3bb54626c117bd85e0158d45fb4aea9 | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.