Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50679: i40e: Fix DMA mappings leak

Noroxi assessment

Priority: Monitor (action score 0/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.24% (FIRST EPSS).
  • Fixed version: Linux Linux 5f499596dfa3db9b3172645b6de9e1096a669c95, 94a171c982b8a8137a00721c1e62bc2713435bca, aae425efdfd1b1d8452260a3cb49344ebf20b1f5.

Low priority for now. Upgrade to Linux Linux 5f499596dfa3db9b3172645b6de9e1096a669c95, 94a171c982b8a8137a00721c1e62bc2713435bca, aae425efdfd1b1d8452260a3cb49344ebf20b1f5 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: i40e: Fix DMA mappings leak During reallocation of RX buffers, new DMA mappings are created for those buffers. steps for reproduction: while : do for ((i=0; i<=8160; i=i+32)) do ethtool -G enp130s0f0 rx $i tx $i sleep 0.5 ethtool -g enp130s0f0 done done This resulted in crash: i40e 0000:01:00.1: Unable to allocate memory for the Rx descriptor ring, size=65536 Driver BUG WARNING: CPU: 0 PID: 4300 at net/core/xdp.c:141 xdp_rxq_info_unreg+0x43/0x50 Call Trace: i40e_free_rx_resources+0x70/0x80 [i40e] i40e_set_ringparam+0x27c/0x800 [i40e] ethnl_set_rings+0x1b2/0x290 genl_family_rcv_msg_doit.isra.15+0x10f/0x150 genl_family_rcv_msg+0xb3/0x160 ? rings_fill_reply+0x1a0/0x1a0 genl_rcv_msg+0x47/0x90 ? genl_family_rcv_msg+0x160/0x160 netlink_rcv_skb+0x4c/0x120 genl_rcv+0x24/0x40 netlink_unicast+0x196/0x230 netlink_sendmsg+0x204/0x3d0 sock_sendmsg+0x4c/0x50 __sys_sendto+0xee/0x160 ? handle_mm_fault+0xbe/0x1e0 ? syscall_trace_enter+0x1d3/0x2c0 __x64_sys_sendto+0x24/0x30 do_syscall_64+0x5b/0x1a0 entry_SYSCALL_64_after_hwframe+0x65/0xca RIP: 0033:0x7f5eac8b035b Missing register, driver bug WARNING: CPU: 0 PID: 4300 at net/core/xdp.c:119 xdp_rxq_info_unreg_mem_model+0x69/0x140 Call Trace: xdp_rxq_info_unreg+0x1e/0x50 i40e_free_rx_resources+0x70/0x80 [i40e] i40e_set_ringparam+0x27c/0x800 [i40e] ethnl_set_rings+0x1b2/0x290 genl_family_rcv_msg_doit.isra.15+0x10f/0x150 genl_family_rcv_msg+0xb3/0x160 ? rings_fill_reply+0x1a0/0x1a0 genl_rcv_msg+0x47/0x90 ? genl_family_rcv_msg+0x160/0x160 netlink_rcv_skb+0x4c/0x120 genl_rcv+0x24/0x40 netlink_unicast+0x196/0x230 netlink_sendmsg+0x204/0x3d0 sock_sendmsg+0x4c/0x50 __sys_sendto+0xee/0x160 ? handle_mm_fault+0xbe/0x1e0 ? syscall_trace_enter+0x1d3/0x2c0 __x64_sys_sendto+0x24/0x30 do_syscall_64+0x5b/0x1a0 entry_SYSCALL_64_after_hwframe+0x65/0xca RIP: 0033:0x7f5eac8b035b This was caused because of new buffers with different RX ring count should substitute older ones, but those buffers were freed in i40e_configure_rx_ring and reallocated again with i40e_alloc_rx_bi, thus kfree on rx_bi caused leak of already mapped DMA. Fix this by reallocating ZC with rx_bi_zc struct when BPF program loads. Additionally reallocate back to rx_bi when BPF program unloads. If BPF program is loaded/unloaded and XSK pools are created, reallocate RX queues accordingly in XSP_SETUP_XSK_POOL handler.

—No exploit Fix available
Published
Dec 9, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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

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

    • 5.8affected
    • be1222b585fdc410b8c1dbcc57dd03a00f04eff5 and later · before ed5baf3d0a33caaca4cd4073ebb0854cc77a616daffected · git
    • be1222b585fdc410b8c1dbcc57dd03a00f04eff5 and later · before 94a171c982b8a8137a00721c1e62bc2713435bcaaffected · git
    • be1222b585fdc410b8c1dbcc57dd03a00f04eff5 and later · before 5f499596dfa3db9b3172645b6de9e1096a669c95affected · git
    • be1222b585fdc410b8c1dbcc57dd03a00f04eff5 and later · before aae425efdfd1b1d8452260a3cb49344ebf20b1f5affected · git
    • before 5.8not affected · semver
    • 5.10.152 and later · up to and including 5.10.*not affected · semver
    • 5.15.76 and later · up to and including 5.15.*not affected · semver
    • 6.0.6 and later · up to and including 6.0.*not affected · semver
    • 6.1 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.6-16.0.6-1
Red Hat:rhel_aus:8.4::baseosbpftoolbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseosbpftool-debuginfobefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernelbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-abi-stablelistsbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-corebefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debugbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-corebefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-debuginfobefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-develbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-modulesbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debug-modules-extrabefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debuginfobefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-develbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-docbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-modulesbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-modules-extrabefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-toolsbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-tools-debuginfobefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseoskernel-tools-libsbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseosperfbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseosperf-debuginfobefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4
Red Hat:rhel_aus:8.4::baseospython3-perfbefore 0:4.18.0-305.114.1.el8_40:4.18.0-305.114.1.el8_4

+10

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-50676Dec 9, 2025 · net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks()
    30Monitor
  • ← EarlierCVE-2022-50678Dec 9, 2025 · wifi: brcmfmac: fix invalid address access when enabling SCAN log level
    0Monitor
  • Later →CVE-2023-53820Dec 9, 2025 · loop: loop_set_status_from_info() check before assignment
    0Monitor

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 Linux5f499596dfa3db9b3172645b6de9e1096a669c95Vendor (CNA)
Linux Linux94a171c982b8a8137a00721c1e62bc2713435bcaVendor (CNA)
Linux Linuxaae425efdfd1b1d8452260a3cb49344ebf20b1f5Vendor (CNA)
Linux Linuxed5baf3d0a33caaca4cd4073ebb0854cc77a616dVendor (CNA)
debian:linux6.0.6-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-305.114.1.el8_4 · Red Hat:rhel_aus:8.4::baseosPackage 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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. Fix✗ → ✓

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

References

Show all references (3 more)

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

All records