Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50756: nvme-pci: fix mempool alloc size

Noroxi assessment

Priority: Monitor (action score 31/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 9141144b37f30e3e7fa024bcfa0a13011e546ba9, b1814724e0d7162bdf4799f2d565381bc2251c63, c89a529e823d51dd23c7ec0c047c7a454a428541.

Low priority for now. Upgrade to Linux Linux 9141144b37f30e3e7fa024bcfa0a13011e546ba9, b1814724e0d7162bdf4799f2d565381bc2251c63, c89a529e823d51dd23c7ec0c047c7a454a428541 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: 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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Dec 24, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2022-50756

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

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

—

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

    • 4.18affected
    • 943e942e6266f22babee5efeb00f8f672fbff5bd and later · before dfb6d54893d544151e7f480bc44cfe7823f5ad23affected · git
    • 943e942e6266f22babee5efeb00f8f672fbff5bd and later · before 9141144b37f30e3e7fa024bcfa0a13011e546ba9affected · git
    • 943e942e6266f22babee5efeb00f8f672fbff5bd and later · before e1777b4286e526c58b4ee699344b0ad85aaf83a0affected · git
    • 943e942e6266f22babee5efeb00f8f672fbff5bd and later · before b1814724e0d7162bdf4799f2d565381bc2251c63affected · git
    • 943e942e6266f22babee5efeb00f8f672fbff5bd and later · before c89a529e823d51dd23c7ec0c047c7a454a428541affected · git
    • before 4.18not affected · semver
    • 5.10.163 and later · up to and including 5.10.*not affected · semver
    • 5.15.87 and later · up to and including 5.15.*not affected · semver
    • 6.0.17 and later · up to and including 6.0.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10

+71

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-50750Dec 24, 2025 · drm/panel/panel-sitronix-st7701: Remove panel on DSI attach failure
    31Monitor
  • ← EarlierCVE-2022-50755Dec 24, 2025 · udf: Avoid double brelse() in udf_rename()
    31Monitor
  • Later →CVE-2022-50780Dec 24, 2025 · net: fix UAF issue in nfqnl_nf_hook_drop() when ops_init() failed
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux9141144b37f30e3e7fa024bcfa0a13011e546ba9Vendor (CNA)
Linux Linuxb1814724e0d7162bdf4799f2d565381bc2251c63Vendor (CNA)
Linux Linuxc89a529e823d51dd23c7ec0c047c7a454a428541Vendor (CNA)
Linux Linuxdfb6d54893d544151e7f480bc44cfe7823f5ad23Vendor (CNA)
Linux Linuxe1777b4286e526c58b4ee699344b0ad85aaf83a0Vendor (CNA)
almalinux:bpftool4.18.0-553.171.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.171.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules-extra0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo-common-x86_640:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-devel0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)

+10

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 researchers

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

No nightly-computed relations.

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records