bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 8b65eaeae88d4e9f999e806e196dd887b90bfed9, Kernel a9b9741854a9fe9df948af49ca5514e0ed0429df, Kernel ca6660c956242623b4cfe9be2a1abc67907c44bf and 1 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.17, >=8fa4219dba8e621aa1e78dfa7eeab10f55acb3c0 <8b65eaeae88d4e9f999e806e196dd887b90bfed9, >=8fa4219dba8e621aa1e78dfa7eeab10f55acb3c0 <a9b9741854a9fe9df948af49ca5514e0ed0429df, >=8fa4219dba8e621aa1e78dfa7eeab10f55acb3c0 <ca6660c956242623b4cfe9be2a1abc67907c44bf, >=8fa4219dba8e621aa1e78dfa7eeab10f55acb3c0 <cde177fa235cd36f981012504a6376315bac03c9 | 8b65eaeae88d4e9f999e806e196dd887b90bfed9, a9b9741854a9fe9df948af49ca5514e0ed0429df, ca6660c956242623b4cfe9be2a1abc67907c44bf, cde177fa235cd36f981012504a6376315bac03c9 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket