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-90176ksmbd: Do not skip lock checks for single-byte ranges

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: Do not skip lock checks for single-byte ranges check_lock_range() uses inclusive ranges. Its callers pass the end offset as start + length - 1, so start == end represents a valid single-byte range rather than an empty range. The start == end shortcut therefore skips mandatory byte-range lock checks for one-byte reads, writes, copychunk operations and one-byte truncate ranges. A conflicting lock covering that byte is not checked and the operation is allowed to proceed. Remove the shortcut. The truncate size == inode->i_size case is already handled by only calling check_lock_range() when the new size differs from the current file size.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 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-90176, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVDNVD · Received3.1High8.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS (exploitation in 30 days)
0.50% · top 57% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 52fcbb92e0d3acfd1448b2a43b6595d540da5295 – < a89cc145832e81c32199d4ca2e1ea8bd51ed601d
    • affected da29cd197246c85c0473259f1cad897d9d28faea – < 993e0158331d37c04da18efe551b5e1e35fb3078
    • affected a6f4cfa3783804336491e0edcb250c25f9b59d33 – < f751d6e39d4c937c45f8fedc66699aa7d2d52288
    • affected 571204e4758a528fbd67330bd4b0dfbdafb33dd8 – < 84c2d8e807ac489f5c91769293fb15dfdae8bae8
    • affected 5d510ac31626ed157d2182149559430350cf2104 – < 07a9e289ff7edcc004f58952405f8a65c4e37512
    • affected 5d510ac31626ed157d2182149559430350cf2104 – < d40c24634fe077a0dc91fd11fccf44ce12b454d5
    • affected 6.1.160 – < 6.1.188
    • affected 6.6.120 – < 6.6.157
    • affected 6.12.64 – < 6.12.110
    • affected 6.18.3 – < 6.18.52
  • Linux · Linux

    • affected 6.19
    • unaffected < 6.19
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .