In the Linux kernel, the following vulnerability has been resolved: iomap: adjust read range correctly for non-block-aligned positions… (CVE-2025-68794)
A critical vulnerability in the Linux kernel's iomap subsystem involves incorrect handling of read ranges for non-block-aligned positions. The function iomap_adjust_read_range() incorrectly assumes block alignment, leading to underflow in length calculations and returning invalid read positions. This flaw can cause incorrect data reads and potentially compromise confidentiality, integrity, and availability of the system. The issue was identified through syzbot testing and affects the erofs filesystem. A fix has been implemented to correctly account for block offsets when calculating bytes to skip for uptodate blocks.
AI Analysis
Technical Summary
The Linux kernel vulnerability CVE-2025-68794 arises from the iomap_adjust_read_range() function's assumption that read positions and lengths are block-aligned, which is not always true. This leads to skipping too many bytes for uptodate blocks, causing underflow in length and returning read positions beyond the folio boundary. This incorrect calculation can result in reading invalid data ranges, impacting system confidentiality, integrity, and availability. The vulnerability was discovered via syzbot testing on the erofs filesystem. The patch corrects the calculation by incorporating the block offset when determining how many bytes to skip for uptodate blocks.
Potential Impact
The vulnerability can cause the Linux kernel to return incorrect read positions and lengths, potentially leading to exposure of unintended data, data corruption, or system instability. The CVSS v3.1 vector indicates network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, and high impact on confidentiality, integrity, and availability, classifying this as a critical security issue.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel to correctly handle non-block-aligned read ranges in iomap_adjust_read_range(). Users and administrators should apply the official Linux kernel updates that include this patch. Since this is not a cloud service, manual patching is required. Patch status is not explicitly stated in the provided data; therefore, verify with the official Linux kernel advisories for the exact fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: iomap: adjust read range correctly for non-block-aligned positions… (CVE-2025-68794)
Description
A critical vulnerability in the Linux kernel's iomap subsystem involves incorrect handling of read ranges for non-block-aligned positions. The function iomap_adjust_read_range() incorrectly assumes block alignment, leading to underflow in length calculations and returning invalid read positions. This flaw can cause incorrect data reads and potentially compromise confidentiality, integrity, and availability of the system. The issue was identified through syzbot testing and affects the erofs filesystem. A fix has been implemented to correctly account for block offsets when calculating bytes to skip for uptodate blocks.
CVSS v3.1
Score 9.8critical
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability CVE-2025-68794 arises from the iomap_adjust_read_range() function's assumption that read positions and lengths are block-aligned, which is not always true. This leads to skipping too many bytes for uptodate blocks, causing underflow in length and returning read positions beyond the folio boundary. This incorrect calculation can result in reading invalid data ranges, impacting system confidentiality, integrity, and availability. The vulnerability was discovered via syzbot testing on the erofs filesystem. The patch corrects the calculation by incorporating the block offset when determining how many bytes to skip for uptodate blocks.
Potential Impact
The vulnerability can cause the Linux kernel to return incorrect read positions and lengths, potentially leading to exposure of unintended data, data corruption, or system instability. The CVSS v3.1 vector indicates network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, and high impact on confidentiality, integrity, and availability, classifying this as a critical security issue.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel to correctly handle non-block-aligned read ranges in iomap_adjust_read_range(). Users and administrators should apply the official Linux kernel updates that include this patch. Since this is not a cloud service, manual patching is required. Patch status is not explicitly stated in the provided data; therefore, verify with the official Linux kernel advisories for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3c24-c79w-qw24
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-68794"]
- Database Specific Severity
- CRITICAL
- Cvss Version
- 3.1
Threat ID: 6a6b72d19c2644c7f84773b0
Added to database: 07/30/2026, 15:50:41 UTC
Last enriched: 07/30/2026, 19:08:55 UTC
Last updated: 09/10/2026, 19:38:45 UTC
Views: 10
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.