Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-21883: ice: Fix deinitializing VF in error path

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 34393fd78d7183a007eaf0090966ebedcc29bd57, 3c01102bec9592928e6b155da41cfcd5d25a2066, 79990cf5e7aded76d0c092c9f5ed31eb1c75e02c.

Low priority for now. Upgrade to Linux Linux 34393fd78d7183a007eaf0090966ebedcc29bd57, 3c01102bec9592928e6b155da41cfcd5d25a2066, 79990cf5e7aded76d0c092c9f5ed31eb1c75e02c 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: ice: Fix deinitializing VF in error path If ice_ena_vfs() fails after calling ice_create_vf_entries(), it frees all VFs without removing them from snapshot PF-VF mailbox list, leading to list corruption. Reproducer: devlink dev eswitch set $PF1_PCI mode switchdev ip l s $PF1 up ip l s $PF1 promisc on sleep 1 echo 1 > /sys/class/net/$PF1/device/sriov_numvfs sleep 1 echo 1 > /sys/class/net/$PF1/device/sriov_numvfs Trace (minimized): list_add corruption. next->prev should be prev (ffff8882e241c6f0), but was 0000000000000000. (next=ffff888455da1330). kernel BUG at lib/list_debug.c:29! RIP: 0010:__list_add_valid_or_report+0xa6/0x100 ice_mbx_init_vf_info+0xa7/0x180 [ice] ice_initialize_vf_entry+0x1fa/0x250 [ice] ice_sriov_configure+0x8d7/0x1520 [ice] ? __percpu_ref_switch_mode+0x1b1/0x5d0 ? __pfx_ice_sriov_configure+0x10/0x10 [ice] Sometimes a KASAN report can be seen instead with a similar stack trace: BUG: KASAN: use-after-free in __list_add_valid_or_report+0xf1/0x100 VFs are added to this list in ice_mbx_init_vf_info(), but only removed in ice_free_vfs(). Move the removing to ice_free_vf_entries(), which is also being called in other places where VFs are being removed (including ice_free_vfs() itself).

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Mar 27, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 11th percentile

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%

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-2025-21883

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.

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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.4 and later · before 6.6.81
  • linux linux kernel6.7 and later · before 6.12.18
  • linux linux kernel6.13 and later · before 6.13.6
  • linux linux kernel6.14

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

    • 6.4affected
    • 8cd8a6b17d275a45e3722d0215f6115b687c8c3e and later · before 3c01102bec9592928e6b155da41cfcd5d25a2066affected · git
    • 8cd8a6b17d275a45e3722d0215f6115b687c8c3e and later · before a4880583f88deba63504ce1c8287a70d39c01378affected · git
    • 8cd8a6b17d275a45e3722d0215f6115b687c8c3e and later · before 34393fd78d7183a007eaf0090966ebedcc29bd57affected · git
    • 8cd8a6b17d275a45e3722d0215f6115b687c8c3e and later · before 79990cf5e7aded76d0c092c9f5ed31eb1c75e02caffected · git
    • before 6.4not affected · semver
    • 6.6.81 and later · up to and including 6.6.*not affected · semver
    • 6.12.18 and later · up to and including 6.12.*not affected · semver
    • 6.13.6 and later · up to and including 6.13.*not affected · semver
    • 6.14 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
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.19.1.el10_06.12.0-55.19.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.19.1.el10_06.12.0-55.19.1.el10_0
AlmaLinux:9kernelbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64kbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-corebefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-debugbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-develbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-corebefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-cross-headersbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-debugbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-debug-corebefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-debug-develbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-570.23.1.el9_65.14.0-570.23.1.el9_6

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-21879Mar 27, 2025 · btrfs: fix use-after-free on inode when scanning root during em shrinking
    31Monitor
  • ← EarlierCVE-2025-21882Mar 27, 2025 · net/mlx5: Fix vport QoS cleanup on error
    22Monitor
  • Later →CVE-2025-21891Mar 27, 2025 · ipvlan: ensure network headers are in skb linear part
    22Monitor

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 Linux34393fd78d7183a007eaf0090966ebedcc29bd57Vendor (CNA)
Linux Linux3c01102bec9592928e6b155da41cfcd5d25a2066Vendor (CNA)
Linux Linux79990cf5e7aded76d0c092c9f5ed31eb1c75e02cVendor (CNA)
Linux Linuxa4880583f88deba63504ce1c8287a70d39c01378Vendor (CNA)
almalinux:kernel5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-570.23.1.el9_6 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.19-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-570.23.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:5.14.0-570.23.1.el9_6 · Rocky Linux:9Package 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.

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.

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)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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

All records