CVE-2024-40919: Linux kernel · NULL Pointer Dereference
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 29 Oct 2026, 22:52 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
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.
References
- nvd.nist.gov/vuln/detail/CVE-2024-40919 (opens in a new tab)
- git.kernel.org/stable/c/8b65eaeae88d4e9f999e806e196dd887b90bfed9 (opens in a new tab)
- git.kernel.org/stable/c/a9b9741854a9fe9df948af49ca5514e0ed0429df (opens in a new tab)
- git.kernel.org/stable/c/ca6660c956242623b4cfe9be2a1abc67907c44bf (opens in a new tab)
- git.kernel.org/stable/c/cde177fa235cd36f981012504a6376315bac03c9 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html (opens in a new tab)