CVE-2025-22091 is an integer-overflow defect in the Linux kernel's RDMA mlx5 driver. Values returned by mlx5_umem_mkc_find_best_pgsz() were stored in unsigned int page_size variables although the selected mkey entity size can exceed the supported range of that type. When registering 4 GB of physically contiguous memory, the driver can select a 4 GB page size, which wraps to zero and reaches a WARN_ON() condition in mlx5_ib's alloc_cacheable_mr() path. The correction changes affected page_size variables to unsigned long.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel RDMA mlx5 driver page_size variable overflow flaw.
A Linux kernel RDMA/mlx5 page_size variable overflow vulnerability addressed by the Red Hat Enterprise Linux 10 kernel security update.
An integer-overflow flaw in the Linux kernel RDMA mlx5 driver. When registering 4GB of physically contiguous memory, the optimized memory-key page size may exceed the range of an unsigned int, overflow to zero, and trigger a kernel warning in alloc_cacheable_mr().
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.