{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89744 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89744 is a high-severity denial of service vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89744 and fix it if it is affected.\n\nWhat it is: CVE-2026-89744 is a high-severity denial of service vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89744 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-89744/ (Markdown: https://insights.sbomify.com/CVE-2026-89744/index.md)","id":"CVE-2026-89744","markdown":"https://insights.sbomify.com/CVE-2026-89744/index.md","name":"CVE-2026-89744","record":{"aliases":["AZL-100527","BELL-CVE-2026-89744","DEBIAN-CVE-2026-89744","GHSA-m8jp-qpwv-wm5j","UBUNTU-CVE-2026-89744"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"An attacker can cause a denial of service in the Linux kernel by triggering an infinite loop in device property iteration logic.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndevice property: fix infinite loop in fwnode_for_each_child_node()\n\nWhen iterate over children of a fwnode that has a secondary fwnode,\nfwnode_get_next_child_node() can enter an infinite loop if the secondary\nfwnode has more than one child.\n\n                       Parent        Child\n      (Primary fwnode)   FWa:   {FWa1, FWa2, FWa3}\n    (Secondary fwnode)   FWb:   {FWb1, FWb2}\n\nIn this case:\n\n ┌─\u003e fwnode_get_next_child_node(FWa, FWa1)\n │    - fwnode_call_ptr_op(FWa, get_next_child_node, FWa1) returns FWa2\n │\n │   ...\n │\n │   fwnode_get_next_child_node(FWa, FWa3)\n │    - fwnode_call_ptr_op(FWa, get_next_child_node, FWa3) returns NULL\n │    - fwnode_call_ptr_op(FWb, get_next_child_node, FWa3) returns FWb1\n │\n │   fwnode_get_next_child_node(FWa, FWb1)\n │    - fwnode_call_ptr_op(FWa, get_next_child_node, FWb1) returns FWa1\n └────┘\n\nThis cause fwnode_for_each_child_node() to loop indefinitely, reapeatedly\noutput {FWa1, FWa2, FWa3, FWb1, FWa1, ...}.\n\nThe root cause is that when the current child (FWb1) belongs to the\nsecondary fwnode, calling get_next_child_node() on the parimary fwnode\nincorrectly returns the first child (FWa1) again instead of NULL.\n\nFix this by dynamically checking the parent fwnode of the current child\nbefore calling get_next_child_node(). This approach follows the pattern\nestablished in commit b5b41ab6b0c1 (\"device property: Check\nfwnode-\u003esecondary in fwnode_graph_get_next_endpoint()\").","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"device property: fix infinite loop in fwnode_for_each_child_node()","id":"CVE-2026-89744","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"debugfs: Fix lockdown check for mmap_prepare","id":"CVE-2026-89745"},"packages":[],"prev":{"headline":"misc: nsm: bound the device-reported response length","id":"CVE-2026-89743"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An attacker can cause a denial of service in the Linux kernel by triggering an infinite loop in device property iteration logic.","url":"https://insights.sbomify.com/CVE-2026-89744/"}