CVE-2025-21883

Advisory lineage Upstream: 0 Downstream: 30
Analyzed
Published: 27 Mar 2025, 14:57
Last modified:11 May 2026, 21:08

Vulnerability Summary

Overall Risk (default)
medium
31/100
CVSS Score
7.8 HIGH
v3.1 (nvd)
EPSS Score
0.01% LOW
0% probability -0.02%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

27 Mar 2025, 14:57
Published
Vulnerability first disclosed
11 May 2026, 21:08
Last Modified
Vulnerability information updated

Description

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

CVSS Metrics

  • v3.1•HIGH•Score: 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.01%• Percentile: 2%

Techniques & Countermeasures

  • CWE-416•Use After Free

    The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Affected Systems

  • linux•linux

    ≥ 8cd8a6b17d275a45e3722d0215f6115b687c8c3e, < 3c01102bec9592928e6b155da41cfcd5d25a2066 | ≥ 8cd8a6b17d275a45e3722d0215f6115b687c8c3e, < a4880583f88deba63504ce1c8287a70d39c01378 | ≥ 8cd8a6b17d275a45e3722d0215f6115b687c8c3e, < 34393fd78d7183a007eaf0090966ebedcc29bd57 | ≥ 8cd8a6b17d275a45e3722d0215f6115b687c8c3e, < 79990cf5e7aded76d0c092c9f5ed31eb1c75e02c | 6.4

  • linux•linux_kernel

    ≥ 6.4, < 6.6.81 | ≥ 6.7, < 6.12.18 | ≥ 6.13, < 6.13.6 | 6.14:rc1 | 6.14:rc2 | 6.14:rc3 | 6.14:rc4

References (4)