CVE-2026-90176
HighIn 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.
CVSS 3.1 score
8.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Affected versions
Linux kernel versions
6.1.160,
6.6.120,
6.12.64,
6.18.3,
6.19
and later are affected. Fixed in
6.1.188,
6.6.157,
6.12.110,
6.18.52,
7.2.6,
7.3-rc1
and their respective stable series.
References
6 totalFrequently asked questions
-
What is CVE-2026-90176?
CVE-2026-90176 is a High severity Linux kernel vulnerability with a CVSS score of 8.1 out of 10 . It affects Linux kernel versions from 6.1.160 onward and has been patched in 6.1.188, 6.6.157, 6.12.110 and others. CVE-2026-90176 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2026-90176?
CVE-2026-90176 has a CVSS score of 8.1 out of 10, rated High severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. -
Is there a patch available for CVE-2026-90176?
Yes. CVE-2026-90176 has been patched. Fixed versions include 6.1.188, 6.6.157, 6.12.110 and others. If you are running Linux kernel 6.1.160 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-90176 actively exploited?
No. CVE-2026-90176 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.