smb: client: validate the whole DACL before rewriting it in cifsacl
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel ff0ca46b13b9ef6edbcd238a3b6caacfef8ba0e5, Kernel 8e47d297e7cf9a6029a0d38e7b22faba7d7aaf12, Kernel b78db9bddc84136f6a0bb49e8883cf200dfb87a8 and 10 more.
In the Linux kernel, the following vulnerability has been resolved: smb: client: validate the whole DACL before rewriting it in cifsacl build_sec_desc() and id_mode_to_cifs_acl() derive a DACL pointer from a server-supplied dacloffset and then use the incoming ACL to rebuild the chmod/chown security descriptor. The original fix only checked that the struct smb_acl header fits before reading dacl_ptr->size or dacl_ptr->num_aces. That avoids the immediate header-field OOB read, but the rewrite helpers still walk ACEs based on pdacl->num_aces with no structural validation of the incoming DACL body. A malicious server can return a truncated DACL that still contains a header, claims one or more ACEs, and then drive replace_sids_and_copy_aces() or set_chmod_dacl() past the validated extent while they compare or copy attacker-controlled ACEs. Factor the DACL structural checks into validate_dacl(), extend them to validate each ACE against the DACL bounds, and use the shared validator before the chmod/chown rebuild paths. parse_dacl() reuses the same validator so the read-side parser and write-side rewrite paths agree on what constitutes a well-formed incoming DACL.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 <ff0ca46b13b9ef6edbcd238a3b6caacfef8ba0e5, >=bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 <8e47d297e7cf9a6029a0d38e7b22faba7d7aaf12, >=bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 <b78db9bddc84136f6a0bb49e8883cf200dfb87a8, >=bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 <b8603d9ae6c9087662b098619996bc4a8064319d, >=bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 <c2abdebf72000a64603ced84d36ccbd164f11391, >=bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 <d92f3f0b22414e7515696a02224d0af55e3004a3, >=5.12 <7.0.2, =5.12, >=bc3e9dd9d104ca1b75644eab87b38ce8a924aef4 <0a8cf165566ba55a39fd0f4de172119dd646d39a | ff0ca46b13b9ef6edbcd238a3b6caacfef8ba0e5, 8e47d297e7cf9a6029a0d38e7b22faba7d7aaf12, b78db9bddc84136f6a0bb49e8883cf200dfb87a8, b8603d9ae6c9087662b098619996bc4a8064319d, c2abdebf72000a64603ced84d36ccbd164f11391, d92f3f0b22414e7515696a02224d0af55e3004a3, 7.0.2, 0a8cf165566ba55a39fd0f4de172119dd646d39a |
| linux-kernel: Kernel | >=5.12.0 <5.15.210, >=5.16.0 <6.1.176, >=6.13.0 <6.18.35, >=6.19.0 <7.0.2, >=6.2.0 <6.6.140, >=6.7.0 <6.12.86 | 5.15.210, 6.1.176, 6.18.35, 7.0.2, 6.6.140, 6.12.86 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket