Loading vulnerability…
CVE-2026-45878 is a bounds-checking vulnerability in the Linux kernel drm/amdkfd debug address-watch functionality. The address-watch clear interface accepts watch_id as an unsigned 32-bit integer, while helper functions handle it as a signed int. Values larger than INT_MAX can become negative in helper logic, bypassing validation and causing undefined bit shifts. The unchecked identifier is subsequently used as an array index in kfd_dbg_trap_clear_dev_address_watch(), potentially writing outside the process-device watch_points array. The fix validates identifiers against MAX_WATCH_ADDRESSES in both set and clear paths before use and uses BIT(watch_id) for bit operations.
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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Incorrect watch_id bounds checking in the Linux kernel AMD KFD driver's debug address-watch functionality.
A vulnerability covered by the Miracle Linux kernel package update. Individual technical details and exploit availability are not specified.
A vulnerability addressed by the AlmaLinux 9 kernel update; no vulnerability-specific technical details are supplied.
A specific vulnerability affecting AlmaLinux 10 kernel-related packages; the content provides no further technical details beyond listing it in the advisory.
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.