In the Linux kernel, the following vulnerability has been resolved: fpga: dfl-afu: validate DMA mapping length in afu_dma_map_region()… (CVE-2026-64280)
A vulnerability in the Linux kernel's FPGA driver (dfl-afu) was resolved by adding validation for DMA mapping length in the afu_dma_map_region() function. The issue involved accepting a 64-bit length from userspace without an upper bound check, leading to potential integer truncation when converting the length to a page count. This could cause improper handling of DMA mapping requests.
AI Analysis
Technical Summary
The Linux kernel's dfl-afu driver accepted a 64-bit length parameter from userspace via the DFL_FPGA_PORT_DMA_MAP ioctl without validating an upper bound. This length was shifted to calculate the number of pages (npages) and passed as an int to pin_user_pages_fast(), causing implicit truncation if the length was very large. The vulnerability was addressed by validating the map.length at the ioctl entry point and rejecting requests where the page count exceeds INT_MAX, preventing integer truncation and potential misuse of the DMA mapping.
Potential Impact
Improper validation of the DMA mapping length could lead to integer truncation, which may cause incorrect memory pinning behavior. This could potentially result in memory corruption or other unintended kernel behavior related to DMA operations in the FPGA driver. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to validate the DMA mapping length at the ioctl entry point, rejecting values whose page count exceeds INT_MAX. Users should update to a Linux kernel version that includes this fix once available. Patch status is not yet confirmed; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: fpga: dfl-afu: validate DMA mapping length in afu_dma_map_region()… (CVE-2026-64280)
Description
A vulnerability in the Linux kernel's FPGA driver (dfl-afu) was resolved by adding validation for DMA mapping length in the afu_dma_map_region() function. The issue involved accepting a 64-bit length from userspace without an upper bound check, leading to potential integer truncation when converting the length to a page count. This could cause improper handling of DMA mapping requests.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's dfl-afu driver accepted a 64-bit length parameter from userspace via the DFL_FPGA_PORT_DMA_MAP ioctl without validating an upper bound. This length was shifted to calculate the number of pages (npages) and passed as an int to pin_user_pages_fast(), causing implicit truncation if the length was very large. The vulnerability was addressed by validating the map.length at the ioctl entry point and rejecting requests where the page count exceeds INT_MAX, preventing integer truncation and potential misuse of the DMA mapping.
Potential Impact
Improper validation of the DMA mapping length could lead to integer truncation, which may cause incorrect memory pinning behavior. This could potentially result in memory corruption or other unintended kernel behavior related to DMA operations in the FPGA driver. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to validate the DMA mapping length at the ioctl entry point, rejecting values whose page count exceeds INT_MAX. Users should update to a Linux kernel version that includes this fix once available. Patch status is not yet confirmed; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-hj85-3f53-vrg4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64280"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420e9c2644c7f8086322
Added to database: 07/25/2026, 23:09:02 UTC
Last enriched: 07/25/2026, 23:39:20 UTC
Last updated: 07/26/2026, 05:00:32 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.