{"id":"CVE-2026-90123","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nirqchip/ast2700-intc: Avoid allocating in the irq_domain activate() callback\n\nThe interrupt core calls the irq_domain_activate() callback from\n__setup_irq() with desc->…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nirqchip/ast2700-intc: Avoid allocating in the irq_domain activate() callback\n\nThe interrupt core calls the irq_domain_activate() callback from\n__setup_irq() with desc->…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 07825e41519abb8ac13d6d1c553af47f57775f6b < f2f0da11648616e47419dca93610f6c0d70ec00b","Linux >= 07825e41519abb8ac13d6d1c553af47f57775f6b < b76eee9c2157223aa4aac42ceebb563288e078aa","Linux 7.2"],"published":"2026-09-17","updated":"2026-09-17","sourceUpdated":"2026-09-17T17:17:04.540","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-90123","references":[{"url":"https://git.kernel.org/stable/c/b76eee9c2157223aa4aac42ceebb563288e078aa","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/f2f0da11648616e47419dca93610f6c0d70ec00b","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-17T16:21:47.883Z","epss":0.00189,"epssPercentile":0.088,"slug":"CVE-2026-90123","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nirqchip/ast2700-intc: Avoid allocating in the irq_domain activate() callback\n\nThe interrupt core calls the irq_domain_activate() callback from\n__setup_irq() with desc->lock held and interrupts disabled. Both\naspeed_intc1_irq_domain_activate() and aspeed_intc0_resolve_route() test a\ncompatible string with fwnode_device_is_compatible().\n\nfwnode_device_is_compatible() invokes fwnode_property_match_string(), which\nallocates with GFP_KERNEL. That's obviously not possible with interrupts\ndisabled and a raw spinlock held.\n\nBoth call sites are only ever handed OF nodes, so use\nof_device_is_compatible() instead: it walks the property in place and does\nnot allocate.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}