CVE-2026-98127
Last modified
CVE-2026-98127 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: smb/client: validate new EOF for insert range smb3_insert_range() does not check if the new file size (i_size + len) is valid. This allows FALLOC_FL_INSERT_RANGE to bypass RLIMIT_FSIZE, exceed s_maxbytes, or produce a size outside the loff_t range. Use check_add_overflow() to calculate the new EOF. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: smb/client: validate new EOF for insert range smb3_insert_range() does not check if the new file size (i_size + len) is valid. This allows FALLOC_FL_INSERT_RANGE to bypass RLIMIT_FSIZE, exceed s_maxbytes, or produce a size outside the loff_t range. Use check_add_overflow() to calculate the new EOF. Validate it with inode_newsize_ok() before modifying the file. Reproducer, using a file on a CIFS mount: bash -c ' FILE=/mnt/cifs/repro trap "" SIGXFSZ ulimit -f 3072 # RLIMIT_FSIZE = 3 MiB # A regular write is stopped at 3 MiB. dd if=/dev/zero of="$FILE" bs=1M count=4 status=none stat -c "size after write: %s" "$FILE" # Insert 2 MiB into a 2 MiB file. truncate -s 2M "$FILE" fallocate -i -o 0 -l 2M "$FILE" stat -c "size after insert: %s" "$FILE" ' Before this change, the regular write stops at the 3 MiB limit, but insert range grows the file to 4 MiB: dd: error writing '/mnt/cifs/repro': File too large size after write: 3145728 size after insert: 4194304 After this change, insert range also fails at the limit and leaves the 2 MiB file unchanged: dd: error writing '/mnt/cifs/repro': File too large size after write: 3145728 fallocate: fallocate failed: File too large size after insert: 2097152
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.13, < 6.6.160 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.111 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.53 | — |
| Linux | Linux Kernel | >= 6.19, < 7.2.7 | — |
| Linux | Linux Kernel | 7.3 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-98127?
How severe is CVE-2026-98127?
How do I fix CVE-2026-98127?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98121In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98122In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98123In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98124In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98125In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98126In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98128In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98129In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-9813FlowIntel up to version 3.3.0 contains a server-side request…9.9
- CVE-2026-98130In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-98131In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98132In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-98127?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
