PatchSiren cyber security CVE debrief
CVE-2026-98126 Linux CVE debrief
A vulnerability in the Linux kernel's SMB client implementation could allow a file to grow beyond a caller's file-size limit when using the FALLOC_FL_ZERO_RANGE operation without FALLOC_FL_KEEP_SIZE. This occurs because the code does not check the RLIMIT_FSIZE before extending the file size. The issue is resolved by calling inode_newsize_ok() before sending the zero-range request when the operation would extend the end of the file.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-25
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-25
- Advisory updated
- 2026-09-25
Who should care
Defenders responsible for Linux kernel systems, particularly those using SMB client functionality, should assess exposure and prioritize patching to prevent potential file size limit bypasses.
Why it matters
A vulnerability in the Linux kernel's SMB client could allow files to grow beyond a caller's file-size limit, potentially impacting systems relying on file size limits for security or operational purposes.
- Verify file size limits are enforced for SMB client operations
- Assess exposure of Linux kernel systems to potential file size limit bypasses
- Prioritize patching for environments where file size limits are critical
Technical summary
The Linux kernel's SMB client implementation does not properly validate new EOF for zero range operations, potentially allowing files to grow beyond a caller's file-size limit. This issue is addressed by adding a call to inode_newsize_ok() before extending the file size. Affected systems could be exposed to potential file size limit bypasses, impacting systems relying on file size limits for security or operational purposes. Defenders should prioritize verifying and applying patches for Linux kernel versions affected by this vulnerability, particularly in environments where file size limits are critical.
Defensive priority
Defenders should prioritize verifying and applying patches for Linux kernel versions affected by this vulnerability, particularly in environments where file size limits are critical.
Recommended defensive actions
- Verify and apply patches for Linux kernel versions affected by this vulnerability
- Review file size limits and ensure inode_newsize_ok() checks are in place
- Monitor for potential file size limit bypass attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and associated source references provide details on the vulnerability, including a description of the issue, a reproducer, and links to relevant kernel commits. This vulnerability affects Linux kernel versions and could allow files to grow beyond a caller's file-size limit when using the FALLOC_FL_ZERO_RANGE operation without FALLOC_FL_KEEP_SIZE. Defenders should verify file size limits are enforced for SMB client operations and assess exposure of Linux kernel systems to potential file size limit bypasses. The issue is
Sources and references
Verified primary and authoritative sources
-
CVE-2026-98126 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-98126
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-98126 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-98126
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/06a4f9049cb6dc319bceec2dc813ba89add8b828
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/3673f057b64abfa957e8ae84448db69369a5091a
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/88972e35750792e717af287dc71f42a03b5cbce4
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/f320ca20c273a26cd779bdb2b2e4b076a95c76f6
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.