Bug 1226473 (ZDI-24-777) - VUL-0: ZDI-24-777: kernel: ksmbd: Out-Of-Bounds Read Information Disclosure Vulnerability
Summary: VUL-0: ZDI-24-777: kernel: ksmbd: Out-Of-Bounds Read Information Disclosure V...
Status: RESOLVED INVALID
Alias: ZDI-24-777
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Kernel Bugs
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/411019/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-18 09:32 UTC by SMASH SMASH
Modified: 2024-06-18 11:45 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-06-18 09:32:10 UTC
This vulnerability allows remote attackers to disclose sensitive information on affected installations of Linux Kernel. Authentication may or may not be required to exploit this vulnerability, depending upon configuration. Furthermore, only systems with ksmbd enabled are vulnerable.

The specific flaw exists within the parsing of SMB2 requests. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the kernel.

Fixed in Linux 6.5-rc7https://github.com/torvalds/linux/commit/5aa4fda5aa9c2a5a7bac67b4a12b089ab81fee3c

References:
https://www.zerodayinitiative.com/advisories/ZDI-24-777/
Comment 1 Andrea Mattiazzo 2024-06-18 09:33:14 UTC
Patch:
https://github.com/torvalds/linux/commit/5aa4fda5aa9c2a5a7bac67b4a12b089ab81fee3c

Closing since ksmbd is not enabled in SLE kernels and TW receive updates via bumps.
Comment 2 Marcus Meissner 2024-06-18 11:45:55 UTC
currently it could only leak the content of pdu->StructureSize2 into dmesg.

There likely is regular struct content in there, so I would not touch this further.