bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send()
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 0.3%
exploitation probability
0.3%top 81% of all CVEs
observed exploitation
nono source reports it
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.
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/8b65eaeae88d4e9f999e806e196dd887b90bfed9https://git.kernel.org/stable/c/a9b9741854a9fe9df948af49ca5514e0ed0429dfhttps://git.kernel.org/stable/c/ca6660c956242623b4cfe9be2a1abc67907c44bfhttps://git.kernel.org/stable/c/cde177fa235cd36f981012504a6376315bac03c9https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html