bnx2x: fix double free in bnx2x_init_firmware() error path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 94a78b79cb5f14c09a42522738d6694c6a1cdd20 · < 4d36e38e48340a1ccf92a98c7a22d07a954e5aa3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bnx2x: fix double free in bnx2x_init_firmware() error path
bnx2x_init_firmware() frees bp->init_ops, bp->init_data and bp->init_ops_offsets in its error path without setting them to NULL. The cleanup function bnx2x_release_firmware() frees the same three pointers unconditionally, so if init_firmware fails and release_firmware is later called (e.g. from __bnx2x_remove or through the function state machine), all three are freed a second time.
Set each pointer to NULL after kfree() in the error path so that the subsequent kfree(NULL) in bnx2x_release_firmware() is a safe no-op.
From the CVE record · Linux
The bnx2x_init_firmware() error path frees three pointers without clearing them, allowing bnx2x_release_firmware() to free them again if initialization fails and cleanup later runs. The input does not describe an attacker-controlled trigger or specify network access, authentication requirements, or user interaction.
Engineers running the Linux kernel with the bnx2x driver should check their systems; affected versions are not specified.