CVE-2026-90176
CVE CVE-2026-90176EUVD EUVD-2026-81769Published 2026-09-17T16:07:02.000ZLast changed 2026-09-18T17:53:36.000ZCVSS 8.1
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 7.2.6; 6.6.120 <6.6.157; a6f4cfa3783804336491e0edcb250c25f9b59d33 <f751d6e39d4c937c45f8fedc66699aa7d2d52288; da29cd197246c85c0473259f1cad897d9d28faea <993e0158331d37c04da18efe551b5e1e35fb3078; patch: 6.12.110; 6.18.3 <6.18.52; 5d510ac31626ed157d2182149559430350cf2104 <07a9e289ff7edcc004f58952405f8a65c4e37512; 6.1.160 <6.1.188; 571204e4758a528fbd67330bd4b0dfbdafb33dd8 <84c2d8e807ac489f5c91769293fb15dfdae8bae8; patch: 6.6.157; 6.19; patch: 0; 6.12.64 <6.12.110; patch: 6.18.52; 5d510ac31626ed157d2182149559430350cf2104 <d40c24634fe077a0dc91fd11fccf44ce12b454d5; patch: 6.1.188; patch: 7.3-rc1; 52fcbb92e0d3acfd1448b2a43b6595d540da5295 <a89cc145832e81c32199d4ca2e1ea8bd51ed601d
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.