CVE-2026-90153

HIGHCVSS 8.1/10

Last modified

CVE-2026-90153 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ksmbd: bound smb_check_perm_dacl() ACE walks by DACL size smb_check_perm_dacl() validates that the DACL fits inside the NT security descriptor, but then bounds its two ACE walks by the remaining NTSD length (acl_size) rather than the DACL's declared size (pdacl_size). When pdacl->size is smaller than the trailing NTSD buffer, bytes after the declared DACL boundary - still inside the stored security descriptor - are parsed as ACEs during access checks. A crafted DACL can place an access-granting ACE beyond pdacl->size, and the current code accepts it during SMB2_CREATE access validation, while parse_dacl() and smb_inherit_dacl() stop at pdacl_size. Bound both ACE walks by pdacl_size to match the DACL boundary semantics used elsewhere in the server. Validation: - semantic KUnit harness shows the post-boundary ACE is selected before the fix and rejected (EACCES) after it - linux master (7.2-rc6), x86_64.

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: bound smb_check_perm_dacl() ACE walks by DACL size smb_check_perm_dacl() validates that the DACL fits inside the NT security descriptor, but then bounds its two ACE walks by the remaining NTSD length (acl_size) rather than the DACL's declared size (pdacl_size). When pdacl->size is smaller than the trailing NTSD buffer, bytes after the declared DACL boundary - still inside the stored security descriptor - are parsed as ACEs during access checks. A crafted DACL can place an access-granting ACE beyond pdacl->size, and the current code accepts it during SMB2_CREATE access validation, while parse_dacl() and smb_inherit_dacl() stop at pdacl_size. Bound both ACE walks by pdacl_size to match the DACL boundary semantics used elsewhere in the server. Validation: - semantic KUnit harness shows the post-boundary ACE is selected before the fix and rejected (EACCES) after it - linux master (7.2-rc6), x86_64

Metrics

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 8f0541186e9ad1b62accc9519cc2b7a7240272a7, < a2051ffe452afad52f580b85a3fd8851933b1e7c; >= 8f0541186e9ad1b62accc9519cc2b7a7240272a7, < a29f57a14c939586d84d7fd6a029bd1fd170098f; >= 8f0541186e9ad1b62accc9519cc2b7a7240272a7, < a4a307d149327dad5fb25187e1b03cebd1b04de6; >= 8f0541186e9ad1b62accc9519cc2b7a7240272a7, < 8e4f75e979c1d9a51b0a48ac33d0cfd5f039ec67; >= 8f0541186e9ad1b62accc9519cc2b7a7240272a7, < 79decd88dd3f0d42e7fb0689b1a7853bfa302459; cb69d4d6f709f87c94afa28ae64c501576692171; 6e8f4abf584253cbaa596ea4ad13110cf61cd4c9; 8e33102309bd6839b2e2e158f93a7b378cb4655d; >= 5.15.62, < 5.16; >= 5.18.18, < 5.19; >= 5.19.2, < 5.20
LinuxLinux6.0

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-90153?
In the Linux kernel, the following vulnerability has been resolved: ksmbd: bound smb_check_perm_dacl() ACE walks by DACL size smb_check_perm_dacl() validates that the DACL fits inside the NT security descriptor, but then bounds its two ACE walks by the remaining NTSD length (acl_size) rather than the DACL's declared size (pdacl_size). When pdacl->size is smaller than the trailing NTSD buffer, bytes after the declared DACL boundary - still inside the stored security descriptor - are parsed as ACEs during access checks. A crafted DACL can place an access-granting ACE beyond pdacl->size, and the current code accepts it during SMB2_CREATE access validation, while parse_dacl() and smb_inherit_dacl() stop at pdacl_size. Bound both ACE walks by pdacl_size to match the DACL boundary semantics used elsewhere in the server. Validation: - semantic KUnit harness shows the post-boundary ACE is selected before the fix and rejected (EACCES) after it - linux master (7.2-rc6), x86_64
How severe is CVE-2026-90153?
CVE-2026-90153 has a CVSS score of 8.1/10 (HIGH severity).
How do I fix CVE-2026-90153?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-90153?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST