Bug 1220183 (CVE-2023-52441) - VUL-0: CVE-2023-52441: kernel-source,kernel-source-azure,kernel-source-rt: In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix out of bounds in init_smb2_rsp_hdr()
Summary: VUL-0: CVE-2023-52441: kernel-source,kernel-source-azure,kernel-source-rt: In...
Status: RESOLVED FIXED
Alias: CVE-2023-52441
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/394724/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-22 08:36 UTC by SMASH SMASH
Modified: 2024-02-23 09:02 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-02-22 08:36:06 UTC 
In the Linux kernel, the following vulnerability has been resolved:

ksmbd: fix out of bounds in init_smb2_rsp_hdr()

If client send smb2 negotiate request and then send smb1 negotiate
request, init_smb2_rsp_hdr is called for smb1 negotiate request since
need_neg is set to false. This patch ignore smb1 packets after ->need_neg
is set to false.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52441
https://www.cve.org/CVERecord?id=CVE-2023-52441
https://git.kernel.org/stable/c/330d900620dfc9893011d725b3620cd2ee0bc2bc
https://git.kernel.org/stable/c/536bb492d39bb6c080c92f31e8a55fe9934f452b
https://git.kernel.org/stable/c/5c0df9d30c289d6b9d7d44e2a450de2f8e3cf40b
https://git.kernel.org/stable/c/aa669ef229ae8dd779da9caa24e254964545895f
Comment 1 Thomas Leroy 2024-02-22 08:37:03 UTC 
ksmbd only built on stable, which is already fixed. So I guess we're good
Comment 2 Joey Lee 2024-02-23 05:34:55 UTC 
I checked SLE11-SP4-LTSS, SLE15-SP5, SLE15-SP6. We did NOT enable CONFIG_SMB_SERVER since long time ago.

And, stable (Tumbleweed) kernel set CONFIG_SMB_SERVER=m, but ksmbd is NOT in supported.config.

So, this CVE of ksmbd does not affect SLE/openSUSE. 

Reset assigner.
Comment 3 Thomas Leroy 2024-02-23 08:17:58 UTC 
(In reply to Joey Lee from comment #2)
> I checked SLE11-SP4-LTSS, SLE15-SP5, SLE15-SP6. We did NOT enable
> CONFIG_SMB_SERVER since long time ago.
> 
> And, stable (Tumbleweed) kernel set CONFIG_SMB_SERVER=m, but ksmbd is NOT in
> supported.config.
> 
> So, this CVE of ksmbd does not affect SLE/openSUSE. 
> 
> Reset assigner.

Thanks Joey, closing
Comment 4 Takashi Iwai 2024-02-23 09:02:25 UTC 
(In reply to Joey Lee from comment #2)
> I checked SLE11-SP4-LTSS, SLE15-SP5, SLE15-SP6. We did NOT enable
> CONFIG_SMB_SERVER since long time ago.
> 
> And, stable (Tumbleweed) kernel set CONFIG_SMB_SERVER=m, but ksmbd is NOT in
> supported.config.

FWIW, supported.conf on stable/master branches is just a placeholder, and it doesn't have any meaning, as those branches don't enable module splitting.
So, you can't judge with supported.conf for stable/master.

OTOH, those branches should receive the fix via the upstream tree now; especially after the change of the CVE assignment strategy for kernel, the fix is (more or less) guaranteed for the upstream (which is good for us, too).