Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98126smb/client: validate new EOF for zero range

Description

In the Linux kernel, the following vulnerability has been resolved: smb/client: validate new EOF for zero range When FALLOC_FL_ZERO_RANGE is used without FALLOC_FL_KEEP_SIZE, smb3_zero_range() may extend EOF without checking RLIMIT_FSIZE, allowing the file to grow beyond the caller's file-size limit. Fix this by calling inode_newsize_ok() before sending the zero-range request when the operation would extend EOF. Reproducer, using a file on a CIFS mount: bash -c ' FILE=/mnt/cifs/repro trap "" SIGXFSZ ulimit -f 3072 truncate -s 2M "$FILE" fallocate --zero-range -o 0 -l 4M "$FILE" echo "fallocate rc=$?" stat -c "file size=%s" "$FILE" ' Before this change, the operation succeeds despite the 3 MiB limit: fallocate rc=0 file size=4194304 After this change, fallocate fails and leaves the file at 2 MiB.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 26 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-98126, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 72c419d9b073628d3b5b0b2fc787b724f1a8c726 – < 5fbd8848f2e25c8163896ec52863df2305a3bb63
    • affected 72c419d9b073628d3b5b0b2fc787b724f1a8c726 – < 3673f057b64abfa957e8ae84448db69369a5091a
    • affected 72c419d9b073628d3b5b0b2fc787b724f1a8c726 – < 06a4f9049cb6dc319bceec2dc813ba89add8b828
    • affected 72c419d9b073628d3b5b0b2fc787b724f1a8c726 – < f320ca20c273a26cd779bdb2b2e4b076a95c76f6
    • affected 72c419d9b073628d3b5b0b2fc787b724f1a8c726 – < 88972e35750792e717af287dc71f42a03b5cbce4
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98126 badge
[![CVE-2026-98126](https://cveledger.app/badge/CVE-2026-98126.svg)](https://cveledger.app/cve/CVE-2026-98126)

Record last updated .