CVE-2024-26858 Affecting kernel-64k-debug 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-KERNEL64KDEBUG-8326806
- published 4 Nov 2024
- disclosed 17 Jul 2024
Introduced: 17 Jul 2024
CVE-2024-26858 Open this link in a new tabHow to fix?
Upgrade AlmaLinux:9
kernel-64k-debug
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
package and not the kernel-64k-debug
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/mlx5e: Use a memory barrier to enforce PTP WQ xmit submission tracking occurs after populating the metadata_map
Just simply reordering the functions mlx5e_ptp_metadata_map_put and mlx5e_ptpsq_track_metadata in the mlx5e_txwqe_complete context is not good enough since both the compiler and CPU are free to reorder these two functions. If reordering does occur, the issue that was supposedly fixed by 7e3f3ba97e6c ("net/mlx5e: Track xmit submission to PTP WQ after populating metadata map") will be seen. This will lead to NULL pointer dereferences in mlx5e_ptpsq_mark_ts_cqes_undelivered in the NAPI polling context due to the tracking list being populated before the metadata map.
References
- https://errata.almalinux.org/9/ALSA-2024-4583.html
- https://access.redhat.com/security/cve/CVE-2024-26858
- https://access.redhat.com/errata/RHSA-2024:4583
- https://git.kernel.org/stable/c/936ef086161ab89a7f38f7a0761d6a3063c3277e
- https://git.kernel.org/stable/c/b7cf07586c40f926063d4d09f7de28ff82f62b2a
- https://git.kernel.org/stable/c/d1f71615dbb305f14f3b756cce015d70d8667549