CVE-2024-40919: bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send()
In the Linux kernel, the following vulnerability has been resolved:
bnxten: Adjust logging of firmware messages in case of released token in hwrmsend()
In case of token is released due to token->state == BNXTHWRMDEFERRED, released token (set to NULL) is used in log messages. This issue is expected to be prevented by HWRMERRCODEPFUNAVAILABLE 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-40919?
The severity of CVE-2024-40919 has not been explicitly rated but it pertains to logging issues in the Linux kernel that should be monitored due to potential implications.
How do I fix CVE-2024-40919?
To fix CVE-2024-40919, upgrade to the patched kernel versions provided by your distribution, such as 6.1.95 or later for Red Hat, or the specified versions for Debian.
Which systems are affected by CVE-2024-40919?
CVE-2024-40919 affects various versions of the Linux kernel, particularly those prior to the specified patched versions from Red Hat and Debian.
What does CVE-2024-40919 involve?
CVE-2024-40919 involves issues related to the adjustment of logging for firmware messages in the BNXT_EN driver within the Linux kernel.
Is CVE-2024-40919 potentially exploitable?
CVE-2024-40919 involves logging behavior rather than a direct security exploit, but it’s advisable to apply patches to maintain system integrity.