https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 22:06:30 +0000 https://vulnerability.circl.lu/vuln/cve-2026-90176 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: Do not skip lock checks for single-byte ranges</p> <p>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.</p> <p>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.</p> <p>Remove the shortcut. The truncate size == inode-&gt;i_size case is already handled by only calling check_lock_range() when the new size differs from the current file size.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: Do not skip lock checks for single-byte ranges</p> <p>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.</p> <p>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.</p> <p>Remove the shortcut. The truncate size == inode-&gt;i_size case is already handled by only calling check_lock_range() when the new size differs from the current file size.</p> https://vulnerability.circl.lu/vuln/cve-2026-90176