Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2024-40906

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Always stop health timer during driver removal Currently, if teardown_hca fails to execute during driver removal, mlx…

Published Jul 12, 2024CWE-416EPSS 0.30%

Overview

CVE-2024-40906 is a high-severity vulnerability. It was published on July 12, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

net/mlx5: Always stop health timer during driver removal

Currently, if teardown_hca fails to execute during driver removal, mlx5

does not stop the health timer. Afterwards, mlx5 continue with driver

teardown. This may lead to a UAF bug, which results in page fault

Oops[1], since the health timer invokes after resources were freed.

Hence, stop the health monitor even if teardown_hca fails.

[1]

mlx5_core 0000:18:00.0: E-Switch: Unload vfs: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)

mlx5_core 0000:18:00.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)

mlx5_core 0000:18:00.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)

mlx5_core 0000:18:00.0: E-Switch: cleanup

mlx5_core 0000:18:00.0: wait_func:1155:(pid 1967079): TEARDOWN_HCA(0x103) timeout. Will cause a leak of a command resource

mlx5_core 0000:18:00.0: mlx5_function_close:1288:(pid 1967079): tear_down_hca fail

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/6ccada6ffb42e0ac75e3db06d41baf5a7f483f8aRefgit.kernel.org/stable/c/c8b3f38d2dae0397944814d691a419c451f9906fRefgit.kernel.org/stable/c/e6777ae0bf6fd5bc626bb051c8c93e3c8198a3f8Refgit.kernel.org/stable/c/e7d4485d47839f4d1284592ae242c4e65b2810a9Refgit.kernel.org/stable/c/6ccada6ffb42e0ac75e3db06d41baf5a7f483f8aRefgit.kernel.org/stable/c/c8b3f38d2dae0397944814d691a419c451f9906fRefgit.kernel.org/stable/c/e6777ae0bf6fd5bc626bb051c8c93e3c8198a3f8Refgit.kernel.org/stable/c/e7d4485d47839f4d1284592ae242c4e65b2810a9Reflists.debian.org/debian-lts-announce/2025/01/msg00001.html

How CyberStrike helps

Frequently asked questions

What is CVE-2024-40906?

CVE-2024-40906 is a high-severity vulnerability. It was published on July 12, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2024-40906?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2024-40906?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2024-40906?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2024-40906 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2024

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999