scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 10663ebec0ad5c78493a0dd34c9ee4d73d7ca0df, Kernel 577a942df3de2666f6947bdd3a5c9e8d30073424 and Kernel c7dc74ab7975c9b96284abfe4cca756d75fa4604.
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI If lpfc_issue_els_flogi() fails and returns non-zero status, the node reference count is decremented to trigger the release of the nodelist structure. However, if there is a prior registration or dev-loss-evt work pending, the node may be released prematurely. When dev-loss-evt completes, the released node is referenced causing a use-after-free null pointer dereference. Similarly, when processing non-zero ELS PLOGI completion status in lpfc_cmpl_els_plogi(), the ndlp flags are checked for a transport registration before triggering node removal. If dev-loss-evt work is pending, the node may be released prematurely and a subsequent call to lpfc_dev_loss_tmo_handler() results in a use after free ndlp dereference. Add test for pending dev-loss before decrementing the node reference count for FLOGI, PLOGI, PRLI, and ADISC handling.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.11, >=52edb2caf675684acf2140a125de4774c691fecd <10663ebec0ad5c78493a0dd34c9ee4d73d7ca0df, >=52edb2caf675684acf2140a125de4774c691fecd <577a942df3de2666f6947bdd3a5c9e8d30073424, >=52edb2caf675684acf2140a125de4774c691fecd <c7dc74ab7975c9b96284abfe4cca756d75fa4604 | 10663ebec0ad5c78493a0dd34c9ee4d73d7ca0df, 577a942df3de2666f6947bdd3a5c9e8d30073424, c7dc74ab7975c9b96284abfe4cca756d75fa4604 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket