Vulnerability · Published Dec 24, 2025 · Assigned by Linux
CVE-2022-50756nvme-pci: fix mempool alloc size
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix mempool alloc size Convert the max size to bytes to match the units of the divisor that calculates the worst-case number of PRP entries. The result is used to determine how many PRP Lists are required. The code was previously rounding this to 1 list, but we can require 2 in the worst case. In that scenario, the driver would corrupt memory beyond the size provided by the mempool. While unlikely to occur (you'd need a 4MB in exactly 127 phys segments on a queue that doesn't support SGLs), this memory corruption has been observed by kfence.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:8 | bpftool | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-abi-stablelists | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-core | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-cross-headers | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-debug | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-debug-core | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-debug-devel | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-debug-modules | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-debug-modules-extra | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-devel | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-doc | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-headers | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-modules | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-modules-extra | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-rt | 4.18.0-553.171.1.rt7.512.el8_10 | ALSA-2026:75746 |
| AlmaLinux:8 | kernel-rt-core | 4.18.0-553.171.1.rt7.512.el8_10 | ALSA-2026:75746 |
| AlmaLinux:8 | kernel-rt-debug | 4.18.0-553.171.1.rt7.512.el8_10 | ALSA-2026:75746 |
| AlmaLinux:8 | kernel-rt-debug-core | 4.18.0-553.171.1.rt7.512.el8_10 | ALSA-2026:75746 |
| AlmaLinux:8 | kernel-rt-debug-devel | 4.18.0-553.171.1.rt7.512.el8_10 | ALSA-2026:75746 |
| AlmaLinux:8 | kernel-rt-debug-modules | 4.18.0-553.171.1.rt7.512.el8_10 | ALSA-2026:75746 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | 4.18.0-553.171.1.rt7.512.el8_10 | ALSA-2026:75746 |
| AlmaLinux:8 | kernel-rt-devel | 4.18.0-553.171.1.rt7.512.el8_10 | ALSA-2026:75746 |
| AlmaLinux:8 | kernel-rt-modules | 4.18.0-553.171.1.rt7.512.el8_10 | ALSA-2026:75746 |
| AlmaLinux:8 | kernel-rt-modules-extra | 4.18.0-553.171.1.rt7.512.el8_10 | ALSA-2026:75746 |
| AlmaLinux:8 | kernel-tools | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-tools-libs | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-tools-libs-devel | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-zfcpdump | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-zfcpdump-core | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-zfcpdump-devel | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-zfcpdump-modules | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | kernel-zfcpdump-modules-extra | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | perf | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| AlmaLinux:8 | python3-perf | 4.18.0-553.171.1.el8_10 | ALSA-2026:75747 |
| Debian:12 | linux | 6.1.4-1 | DEBIAN-CVE-2022-50756 |
| Debian:13 | linux | 6.1.4-1 | DEBIAN-CVE-2022-50756 |
| Debian:14 | linux | 6.1.4-1 | DEBIAN-CVE-2022-50756 |
| Rocky Linux:8 | kernel | 0:4.18.0-553.171.1.el8_10 | RLSA-2026:75747 |
| Rocky Linux:8 | kernel-rt | 0:4.18.0-553.171.1.rt7.512.el8_10 | RLSA-2026:75746 |
| Ubuntu:22.04:LTS | linux | 5.15.0-69.76 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1033.37 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1035.42 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1035.42.1 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1031.38 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1030.35 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1017.22 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1027.30 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1027.32 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1030.35 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-69.76 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1023.23 | UBUNTU-CVE-2022-50756 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1032.38 | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1026.28 | UBUNTU-CVE-2022-50756 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2022-50756 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2022-50756 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 943e942e6266f22babee5efeb00f8f672fbff5bd – before dfb6d54893d544151e7f480bc44cfe7823f5ad23943e942e6266f22babee5efeb00f8f672fbff5bd – before 9141144b37f30e3e7fa024bcfa0a13011e546ba9943e942e6266f22babee5efeb00f8f672fbff5bd – before e1777b4286e526c58b4ee699344b0ad85aaf83a0943e942e6266f22babee5efeb00f8f672fbff5bd – before b1814724e0d7162bdf4799f2d565381bc2251c63943e942e6266f22babee5efeb00f8f672fbff5bd – before c89a529e823d51dd23c7ec0c047c7a454a428541 |
| Linux | Linux | 4.18 |
References
- https://git.kernel.org/stable/c/dfb6d54893d544151e7f480bc44cfe7823f5ad23
- https://git.kernel.org/stable/c/9141144b37f30e3e7fa024bcfa0a13011e546ba9
- https://git.kernel.org/stable/c/e1777b4286e526c58b4ee699344b0ad85aaf83a0
- https://git.kernel.org/stable/c/b1814724e0d7162bdf4799f2d565381bc2251c63
- https://git.kernel.org/stable/c/c89a529e823d51dd23c7ec0c047c7a454a428541