Bug 1226726 (CVE-2024-38593)

Summary: VUL-0: CVE-2024-38593: kernel: net: micrel: fix receiving the timestamp in the frame for lan8841
Product: [Novell Products] SUSE Security Incidents Reporter: SMASH SMASH <smash_bz>
Component: IncidentsAssignee: Security Team bot <security-team>
Status: RESOLVED INVALID QA Contact: Security Team bot <security-team>
Severity: Normal    
Priority: P3 - Medium CC: camila.matos, gabriel.bertazi
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://smash.suse.de/issue/411376/
Whiteboard: CVSSv3.1:SUSE:CVE-2024-38593:5.5:(AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Found By: Security Response Team Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description SMASH SMASH 2024-06-21 10:26:14 UTC 
In the Linux kernel, the following vulnerability has been resolved:

net: micrel: Fix receiving the timestamp in the frame for lan8841

The blamed commit started to use the ptp workqueue to get the second
part of the timestamp. And when the port was set down, then this
workqueue is stopped. But if the config option NETWORK_PHY_TIMESTAMPING
is not enabled, then the ptp_clock is not initialized so then it would
crash when it would try to access the delayed work.
So then basically by setting up and then down the port, it would crash.
The fix consists in checking if the ptp_clock is initialized and only
then cancel the delayed work.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-38593
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-38593.mbox
https://git.kernel.org/stable/c/3ddf170e4a604f5d4d9459a36993f5e92b53e8b0
https://git.kernel.org/stable/c/3fd4282d5f25c3c97fef3ef0b89b82ef4e2bc975
https://git.kernel.org/stable/c/64a47cf634ae44e92be24ebc982410841093bd7b
https://git.kernel.org/stable/c/aea27a92a41dae14843f92c79e9e42d8f570105c
https://www.cve.org/CVERecord?id=CVE-2024-38593
https://bugzilla.redhat.com/show_bug.cgi?id=2293380