CVE-2024-40919 bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send()
A null pointer dereference in the bnxt_en network driver can cause a kernel crash when firmware messages are logged with a released token.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-40919?
CVE-2024-40919 is a medium-severity vulnerability in Linux kernel, published on 12 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
In the Linux kernel, the following vulnerability has been resolved:
bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send()
In case of token is released due to token->state == BNXT_HWRM_DEFERRED, released token (set to NULL) is used in log messages. This issue is expected to be prevented by HWRM_ERR_CODE_PF_UNAVAILABLE error code. But this error code is returned by recent firmware. So some firmware may not return it. This may lead to NULL pointer dereference. Adjust this issue by adding token pointer check.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Weakness: CWE-476
Which versions are affected by CVE-2024-40919?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2024-40919?
Apply the vendor's patch.
Is CVE-2024-40919 being exploited?
There is no known exploitation of CVE-2024-40919 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as BELL-CVE-2024-40919, DEBIAN-CVE-2024-40919, GHSA-mr4m-76gc-52jc, UBUNTU-CVE-2024-40919.