CVE-2024-38593 Affecting kernel-64k-debug-devel-matched package, versions <0:5.14.0-427.26.1.el9_4
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-ALMALINUX9-KERNEL64KDEBUGDEVELMATCHED-8329449
- published 4 Nov 2024
- disclosed 17 Jul 2024
Introduced: 17 Jul 2024
CVE-2024-38593 Open this link in a new tabHow to fix?
Upgrade AlmaLinux:9 kernel-64k-debug-devel-matched to version 0:5.14.0-427.26.1.el9_4 or higher.
This issue was patched in ALSA-2024:4583.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-64k-debug-devel-matched package and not the kernel-64k-debug-devel-matched package as distributed by AlmaLinux.
See How to fix? for AlmaLinux:9 relevant fixed versions and status.
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
- https://errata.almalinux.org/9/ALSA-2024-4583.html
- https://access.redhat.com/security/cve/CVE-2024-38593
- https://access.redhat.com/errata/RHSA-2024:4583
- 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