firewire: core: fix memory leak in error path of build_tree()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3038e353cfaf548eb94f02b172b9dbe412abd24c · < 05bfb1327dc5fb61528bab31cd8f0c1e4bddec23| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
firewire: core: fix memory leak in error path of build_tree()
In the error path of build_tree(), node instances can remain in the local linked list when the function returns.
Whenever an invalid value is detected in the self ID sequence, each allocated node instance is either an entry in the linked list or an entry in the ports array of its parent node. Therefore, the allocate node instances can be safely released by traversing the linked list from its head.
Release the remaining node instances with for_each_fw_node() before returning to the caller.
From the CVE record · Linux
The FireWire core’s build_tree() function can leak allocated node instances when it encounters an invalid self ID sequence and returns through an error path. The input does not establish whether an attacker can trigger this condition or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the FireWire core should check whether their kernel includes this fix; affected versions are not specified.