device property: set fwnode->secondary to NULL in fwnode_init()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 01bb86b380a306bd937c96da36f66429f3362137 · < f59e686c778cb41b8f7aa8fab2afd6a01afb3d47| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
device property: set fwnode->secondary to NULL in fwnode_init()
If a firmware node is allocated on the stack (for instance: temporary software node whose life-time we control) or on the heap - but using a non-zeroing allocation function - and initialized using fwnode_init(), its secondary pointer will contain uninitalized memory which likely will be neither NULL nor IS_ERR() and so may end up being dereferenced (for example: in dev_to_swnode()). Set fwnode->secondary to NULL on initialization.
From the CVE record · Linux
The Linux kernel’s fwnode_init() leaves the secondary pointer uninitialized when a firmware node is allocated on the stack or with a non-zeroing heap allocator. The pointer may later be dereferenced; the input does not establish how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their installations; affected versions are not specified.