nexthop: Initialize extack in remove_nh_grp_entry()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 833a1065eeb14437a9a0dfa9dad06ea09894e0b5 · < d80677ad7aa5bebfccfd58caa4852b65abe70561| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nexthop: Initialize extack in remove_nh_grp_entry()
remove_nh_grp_entry() prints the extack message when a listener fails to replace the reduced nexthop group. However, extack is not initialized and listeners are not required to set a message when returning an error. Neither netdevsim nor mlxsw do so when an allocation fails, resulting in the dereference of an uninitialized stack pointer.
Fix by zero-initializing extack, as was done in commit 6347c5314cee ("nexthop: initialize extack in nh_res_bucket_migrate()").
From the CVE record · Linux
The Linux kernel's remove_nh_grp_entry() uses an uninitialized extack pointer if a listener fails to replace a reduced nexthop group without setting an error message. An allocation failure in netdevsim or mlxsw can cause this condition. The input does not specify whether triggering it requires network access, authentication, or user interaction.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.