Loading vulnerability…
CVE-2021-47609 is an out-of-bounds write in the Linux kernel ARM SCPI generic power-domain driver, introduced in Linux 4.8. The driver copied an SCPI device name obtained from a device-tree node into the fixed-size scpi_pd->name buffer without enforcing bounds. A device name of up to 30 characters could overflow the destination. The upstream fix replaces the fixed name-buffer handling with dynamically allocated storage using devm_kasprintf.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel ARM SCPI driver string-overflow flaw.
A string-overflow vulnerability in the Linux kernel ARM SCPI (System Control and Power Interface) generic power-domain driver.
A Linux-kernel firmware ARM SCPI genpd-driver out-of-bounds write caused by insufficient bounds checking when copying an SCPI device name from a device-tree node. The remediation dynamically allocates the name buffer using devm_kasprintf. Red Hat rates it Low severity with CVSS 6.7; NVD rates it 7.8.
A Linux kernel buffer-overflow vulnerability in the ARM SCPI generic power-domain (genpd) driver (drivers/firmware/scpi_pm_domain.c). An overly long SCPI device name from a device-tree node could overflow the fixed scpi_pd->name buffer because bounds checks were absent.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.