CVE-2025-22091: RDMA/mlx5: Fix page_size variable overflow
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 01fd737776ca0f17a96d83cd7f0840ce130b9a02, 05b215d5e219c0228b9c7082ba9bcf176c576646, e0c09f639ca0e102f250df8787740c2013e9d1b3.
Low priority for now. Upgrade to Linux Linux 01fd737776ca0f17a96d83cd7f0840ce130b9a02, 05b215d5e219c0228b9c7082ba9bcf176c576646, e0c09f639ca0e102f250df8787740c2013e9d1b3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix page_size variable overflow Change all variables storing mlx5_umem_mkc_find_best_pgsz() result to unsigned long to support values larger than 31 and avoid overflow. For example: If we try to register 4GB of memory that is contiguous in physical memory, the driver will optimize the page_size and try to use an mkey with 4GB entity size. The 'unsigned int' page_size variable will overflow to '0' and we'll hit the WARN_ON() in alloc_cacheable_mr(). WARNING: CPU: 2 PID: 1203 at drivers/infiniband/hw/mlx5/mr.c:1124 alloc_cacheable_mr+0x22/0x580 [mlx5_ib] Modules linked in: mlx5_ib mlx5_core bonding ip6_gre ip6_tunnel tunnel6 ip_gre gre rdma_rxe rdma_ucm ib_uverbs ib_ipoib ib_umad rpcrdma ib_iser libiscsi scsi_transport_iscsi rdma_cm iw_cm ib_cm fuse ib_core [last unloaded: mlx5_core] CPU: 2 UID: 70878 PID: 1203 Comm: rdma_resource_l Tainted: G W 6.14.0-rc4-dirty #43 Tainted: [W]=WARN Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:alloc_cacheable_mr+0x22/0x580 [mlx5_ib] Code: 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 41 52 53 48 83 ec 30 f6 46 28 04 4c 8b 77 08 75 21 <0f> 0b 49 c7 c2 ea ff ff ff 48 8d 65 d0 4c 89 d0 5b 41 5a 41 5c 41 RSP: 0018:ffffc900006ffac8 EFLAGS: 00010246 RAX: 0000000004c0d0d0 RBX: ffff888217a22000 RCX: 0000000000100001 RDX: 00007fb7ac480000 RSI: ffff8882037b1240 RDI: ffff8882046f0600 RBP: ffffc900006ffb28 R08: 0000000000000001 R09: 0000000000000000 R10: 00000000000007e0 R11: ffffea0008011d40 R12: ffff8882037b1240 R13: ffff8882046f0600 R14: ffff888217a22000 R15: ffffc900006ffe00 FS: 00007fb7ed013340(0000) GS:ffff88885fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fb7ed1d8000 CR3: 00000001fd8f6006 CR4: 0000000000772eb0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> ? __warn+0x81/0x130 ? alloc_cacheable_mr+0x22/0x580 [mlx5_ib] ? report_bug+0xfc/0x1e0 ? handle_bug+0x55/0x90 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? alloc_cacheable_mr+0x22/0x580 [mlx5_ib] create_real_mr+0x54/0x150 [mlx5_ib] ib_uverbs_reg_mr+0x17f/0x2a0 [ib_uverbs] ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0xca/0x140 [ib_uverbs] ib_uverbs_run_method+0x6d0/0x780 [ib_uverbs] ? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs] ib_uverbs_cmd_verbs+0x19b/0x360 [ib_uverbs] ? walk_system_ram_range+0x79/0xd0 ? ___pte_offset_map+0x1b/0x110 ? __pte_offset_map_lock+0x80/0x100 ib_uverbs_ioctl+0xac/0x110 [ib_uverbs] __x64_sys_ioctl+0x94/0xb0 do_syscall_64+0x50/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7fb7ecf0737b Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 7d 2a 0f 00 f7 d8 64 89 01 48 RSP: 002b:00007ffdbe03ecc8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffdbe03edb8 RCX: 00007fb7ecf0737b RDX: 00007ffdbe03eda0 RSI: 00000000c0181b01 RDI: 0000000000000003 RBP: 00007ffdbe03ed80 R08: 00007fb7ecc84010 R09: 00007ffdbe03eed4 R10: 0000000000000009 R11: 0000000000000246 R12: 00007ffdbe03eed4 R13: 000000000000000c R14: 000000000000000c R15: 00007fb7ecc84150 </TASK>
- Published
- Apr 16, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-190
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.12 and later · before 6.12.23
- linux linux kernel6.13 and later · before 6.13.11
- linux linux kernel6.14 and later · before 6.14.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.12affected
- cef7dde8836ab09a3bfe96ada4f18ef2496eacc9 and later · before 01fd737776ca0f17a96d83cd7f0840ce130b9a02affected · git
- cef7dde8836ab09a3bfe96ada4f18ef2496eacc9 and later · before e0c09f639ca0e102f250df8787740c2013e9d1b3affected · git
- cef7dde8836ab09a3bfe96ada4f18ef2496eacc9 and later · before 05b215d5e219c0228b9c7082ba9bcf176c576646affected · git
- cef7dde8836ab09a3bfe96ada4f18ef2496eacc9 and later · before f0c2427412b43cdf1b7b0944749ea17ddb97d5a5affected · git
- before 6.12not affected · semver
- 6.12.23 and later · up to and including 6.12.*not affected · semver
- 6.13.11 and later · up to and including 6.13.*not affected · semver
- 6.14.2 and later · up to and including 6.14.*not affected · semver
- 6.15 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-55.24.1.el10_0 | 6.12.0-55.24.1.el10_0 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-55.24.1.el10_0 | 6.12.0-55.24.1.el10_0 |
| AlmaLinux:9 | kernel | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-570.30.1.el9_6 | 5.14.0-570.30.1.el9_6 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-22083Apr 16, 2025 · vhost-scsi: Fix handling of multiple calls to vhost_scsi_set_endpoint31Monitor
- ← EarlierCVE-2025-22090Apr 16, 2025 · x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()22Monitor
- Later →CVE-2025-22095Apr 16, 2025 · PCI: brcmstb: Fix error path after a call to regulator_bulk_get()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01fd737776ca0f17a96d83cd7f0840ce130b9a02 | Vendor (CNA) |
| Linux Linux | 05b215d5e219c0228b9c7082ba9bcf176c576646 | Vendor (CNA) |
| Linux Linux | e0c09f639ca0e102f250df8787740c2013e9d1b3 | Vendor (CNA) |
| Linux Linux | f0c2427412b43cdf1b7b0944749ea17ddb97d5a5 | Vendor (CNA) |
| almalinux:kernel | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-570.30.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 6.12.0-55.24.1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-doc | 6.12.0-55.24.1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.12.25-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:6.12.0-55.24.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| rocky linux:kernel | 0:6.12.0-55.24.1.el10_0 · Rocky Linux:10 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-31633373 days apartrxrpc: Fix integer overflow in rxgk_verify_response()39Monitor
- CVE-2026-31649373 days apartnet: stmmac: fix integer underflow in chain mode39Monitor
- CVE-2026-31659373 days apartbatman-adv: reject oversized global TT response buffers39Monitor
- CVE-2026-43341387 days apartnet/ipv6: ioam6: prevent schema length wraparound in trace fill39Monitor
- CVE-2026-46039406 days apartrxgk: Fix potential integer overflow in length check39Monitor
- CVE-2026-46325419 days apartRDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE39Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.