|
Bugzilla – Full Text Bug Listing |
| Summary: | 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() | ||
|---|---|---|---|
| Product: | [Novell Products] SUSE Security Incidents | Reporter: | SMASH SMASH <smash_bz> |
| Component: | Incidents | Assignee: | Security Team bot <security-team> |
| Status: | RESOLVED FIXED | QA Contact: | Security Team bot <security-team> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | jlee, thomas.leroy, tiwai |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| URL: | https://smash.suse.de/issue/394724/ | ||
| Whiteboard: | |||
| Found By: | Security Response Team | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
SMASH SMASH
2024-02-22 08:36:06 UTC
ksmbd only built on stable, which is already fixed. So I guess we're good 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. (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 (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). |