Bug 2388958 (CVE-2023-4130)
| Summary: | CVE-2023-4130 kernel: ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea() | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | rhel-process-autobot, watson-tool-maintainers |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
In the Linux kernel, a flaw was found in the KSMBD server implementation when handling FILE_FULL_EA_INFORMATION requests. The issue arises in the smb2_set_ea() function, where multiple smb2_ea_info buffers are processed using the NextEntryOffset field. KSMBD incorrectly validated the length of the next extended attribute (EA) buffer using the next offset instead of the actual buffer length (buf_len). Since next represents the offset of the current EA rather than the remaining buffer size, this mistake could allow an out-of-bounds access when parsing subsequent entries. This vulnerability could potentially lead to memory corruption or denial of service when processing malicious SMB requests.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
OSIDB Bzimport
2025-08-16 14:01:18 UTC
|