SECUFOCUSNOW
Home›CVE index›CVE-2022-50756
Review reviewHigh

CVE-2022-50756

Linux

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...

CVSS
7.8
EPSS
0.17%
7.11% percentile
CISA KEV
Not listed
Published
2025.12.24
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.17%
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux
Affected versions
>= 943e942e6266f22babee5efeb00f8f672fbff5bd < dfb6d54893d544151e7f480bc44cfe7823f5ad23, >= 943e942e6266f22babee5efeb00f8f672fbff5bd < 9141144b37f30e3e7fa024bcfa0a13011e546ba9, >= 943e942e6266f22babee5efeb00f8f672fbff5bd < e1777b4286e526c58b4ee699344b0ad85aaf83a0, >= 943e942e6266f22babee5efeb00f8f672fbff5bd < b1814724e0d7162bdf4799f2d565381bc2251c63, >= 943e942e6266f22babee5efeb00f8f672fbff5bd < c89a529e823d51dd23c7ec0c047c7a454a428541, >= 4.18
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available