bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
In the Linux kernel's bnxt_en driver, a released token can be used in firmware-message logging, potentially causing a NULL pointer dereference. This can occur when a token is deferred and the firmware does not return the error code expected to prevent the issue. The input does not specify attacker access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the bnxt_en driver should check their versions; affected versions are not specified.