Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50756

nvme-pci: fix mempool alloc size

High7.8EPSS 0.20%
Published
Updated
Reserved
Assigned by
Linux

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50756, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 943e942e6266f22babee5efeb00f8f672fbff5bd – < dfb6d54893d544151e7f480bc44cfe7823f5ad23
    • affected 943e942e6266f22babee5efeb00f8f672fbff5bd – < 9141144b37f30e3e7fa024bcfa0a13011e546ba9
    • affected 943e942e6266f22babee5efeb00f8f672fbff5bd – < e1777b4286e526c58b4ee699344b0ad85aaf83a0
    • affected 943e942e6266f22babee5efeb00f8f672fbff5bd – < b1814724e0d7162bdf4799f2d565381bc2251c63
    • affected 943e942e6266f22babee5efeb00f8f672fbff5bd – < c89a529e823d51dd23c7ec0c047c7a454a428541
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.87 – ≤ 5.15.*
    • unaffected 6.0.17 – ≤ 6.0.*
    • unaffected 6.1.3 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References (5)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50756 badge
[![CVE-2022-50756](https://trackcve.app/badge/CVE-2022-50756.svg)](https://trackcve.app/cve/CVE-2022-50756)

Record last updated .