CVE-2024-26858
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Analyzed
Affected
- Linux Kernel < 6.6
- Linux Kernel < 6.6.22
- Linux Kernel < 6.7.10
- Linux Kernel 6.8
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-26858.md and follow it. Check whether this project is affected by CVE-2024-26858. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/936ef086161ab89a7f38f7a0761d6a3063c3277e
- https://git.kernel.org/stable/c/b7cf07586c40f926063d4d09f7de28ff82f62b2a
- https://git.kernel.org/stable/c/d1f71615dbb305f14f3b756cce015d70d8667549
- https://git.kernel.org/stable/c/936ef086161ab89a7f38f7a0761d6a3063c3277e
- https://git.kernel.org/stable/c/b7cf07586c40f926063d4d09f7de28ff82f62b2a
- https://git.kernel.org/stable/c/d1f71615dbb305f14f3b756cce015d70d8667549
References
- https://git.kernel.org/stable/c/936ef086161ab89a7f38f7a0761d6a3063c3277e
- https://git.kernel.org/stable/c/b7cf07586c40f926063d4d09f7de28ff82f62b2a
- https://git.kernel.org/stable/c/d1f71615dbb305f14f3b756cce015d70d8667549
- https://git.kernel.org/stable/c/936ef086161ab89a7f38f7a0761d6a3063c3277e
- https://git.kernel.org/stable/c/b7cf07586c40f926063d4d09f7de28ff82f62b2a
- https://git.kernel.org/stable/c/d1f71615dbb305f14f3b756cce015d70d8667549