net: hsr: free learned nodes on device setup failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 81ba6afd6e6443d2bf4bf40f16df1f1f91c603f8 · < 7f16289b91eb316f170a6bd22d32e6c632f6a5b6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: hsr: free learned nodes on device setup failure
hsr_dev_finalize() can fail after a lower-device RX handler has already been registered (slave A is added before the failable slave B and interlink adds). RX handlers run in softirq regardless of the master's state, so frames received in that window can learn dynamic nodes into node_db, and the error unwind never releases them.
Free both owned dynamic databases in the unwind, mirroring hsr_dellink(). proxy_node_db is provably empty on every current error exit (only interlink RX feeds it, and the interlink add is the last failable step) and is freed for symmetry. The order is safe: hsr_del_port() unregisters each RX handler with synchronize_net() before hsr_del_nodes() runs, which removes remaining entries with list_del_rcu() and defers their release with call_rcu() for readers already under RCU.
From the CVE record · Linux
The Linux kernel’s HSR device setup can fail after an RX handler has been registered, leaving learned nodes in memory. If frames arrive during that window, the failure path does not release those nodes.
Engineers running Linux kernels that use HSR should check their kernel versions; affected versions were not provided.