CVE-2025-21865 Vulnerability Analysis & Exploit Details

CVE-2025-21865
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2025-21865 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-21865 Details

Status: Analyzed

Last updated: 🕘 13 Mar 2025, 21:13 UTC
Originally published on: 🕙 12 Mar 2025, 10:15 UTC

Time between publication and last update: 1 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2025-21865 Vulnerability Summary

CVE-2025-21865: In the Linux kernel, the following vulnerability has been resolved: gtp: Suppress list corruption splat in gtp_net_exit_batch_rtnl(). Brad Spengler reported the list_del() corruption splat in gtp_net_exit_batch_rtnl(). [0] Commit eb28fd76c0a0 ("gtp: Destroy device along with udp socket's netns dismantle.") added the for_each_netdev() loop in gtp_net_exit_batch_rtnl() to destroy devices in each netns as done in geneve and ip tunnels. However, this could trigger ->dellink() twice for the same device during ->exit_batch_rtnl(). Say we have two netns A & B and gtp device B that resides in netns B but whose UDP socket is in netns A. 1. cleanup_net() processes netns A and then B. 2. gtp_net_exit_batch_rtnl() finds the device B while iterating netns A's gn->gtp_dev_list and calls ->dellink(). [ device B is not yet unlinked from netns B as unregister_netdevice_many() has not been called. ] 3. gtp_net_exit_batch_rtnl() finds the device B while iterating netns B's for_each_netdev() and calls ->dellink(). gtp_dellink() cleans up the device's hash table, unlinks the dev from gn->gtp_dev_list, and calls unregister_netdevice_queue(). Basically, calling gtp_dellink() multiple times is fine unless CONFIG_DEBUG_LIST is enabled. Let's remove for_each_netdev() in gtp_net_exit_batch_rtnl() and delegate the destruction to default_device_exit_batch() as done in bareudp. [0]: list_del corruption, ffff8880aaa62c00->next (autoslab_size_M_dev_P_net_core_dev_11127_8_1328_8_S_4096_A_64_n_139+0xc00/0x1000 [slab object]) is LIST_POISON1 (ffffffffffffff02) (prev is 0xffffffffffffff04) kernel BUG at lib/list_debug.c:58! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 1 UID: 0 PID: 1804 Comm: kworker/u8:7 Tainted: G T 6.12.13-grsec-full-20250211091339 #1 Tainted: [T]=RANDSTRUCT Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: netns cleanup_net RIP: 0010:[<ffffffff84947381>] __list_del_entry_valid_or_report+0x141/0x200 lib/list_debug.c:58 Code: c2 76 91 31 c0 e8 9f b1 f7 fc 0f 0b 4d 89 f0 48 c7 c1 02 ff ff ff 48 89 ea 48 89 ee 48 c7 c7 e0 c2 76 91 31 c0 e8 7f b1 f7 fc <0f> 0b 4d 89 e8 48 c7 c1 04 ff ff ff 48 89 ea 48 89 ee 48 c7 c7 60 RSP: 0018:fffffe8040b4fbd0 EFLAGS: 00010283 RAX: 00000000000000cc RBX: dffffc0000000000 RCX: ffffffff818c4054 RDX: ffffffff84947381 RSI: ffffffff818d1512 RDI: 0000000000000000 RBP: ffff8880aaa62c00 R08: 0000000000000001 R09: fffffbd008169f32 R10: fffffe8040b4f997 R11: 0000000000000001 R12: a1988d84f24943e4 R13: ffffffffffffff02 R14: ffffffffffffff04 R15: ffff8880aaa62c08 RBX: kasan shadow of 0x0 RCX: __wake_up_klogd.part.0+0x74/0xe0 kernel/printk/printk.c:4554 RDX: __list_del_entry_valid_or_report+0x141/0x200 lib/list_debug.c:58 RSI: vprintk+0x72/0x100 kernel/printk/printk_safe.c:71 RBP: autoslab_size_M_dev_P_net_core_dev_11127_8_1328_8_S_4096_A_64_n_139+0xc00/0x1000 [slab object] RSP: process kstack fffffe8040b4fbd0+0x7bd0/0x8000 [kworker/u8:7+netns 1804 ] R09: kasan shadow of process kstack fffffe8040b4f990+0x7990/0x8000 [kworker/u8:7+netns 1804 ] R10: process kstack fffffe8040b4f997+0x7997/0x8000 [kworker/u8:7+netns 1804 ] R15: autoslab_size_M_dev_P_net_core_dev_11127_8_1328_8_S_4096_A_64_n_139+0xc08/0x1000 [slab object] FS: 0000000000000000(0000) GS:ffff888116000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000748f5372c000 CR3: 0000000015408000 CR4: 00000000003406f0 shadow CR4: 00000000003406f0 Stack: 0000000000000000 ffffffff8a0c35e7 ffffffff8a0c3603 ffff8880aaa62c00 ffff8880aaa62c00 0000000000000004 ffff88811145311c 0000000000000005 0000000000000001 ffff8880aaa62000 fffffe8040b4fd40 ffffffff8a0c360d Call Trace: <TASK> [<ffffffff8a0c360d>] __list_del_entry_valid include/linux/list.h:131 [inline] fffffe8040b4fc28 [<ffffffff8a0c360d>] __list_del_entry include/linux/list.h:248 [inline] fffffe8040b4fc28 [<ffffffff8a0c360d>] list_del include/linux/list.h:262 [inl ---truncated---

Assessing the Risk of CVE-2025-21865

Access Complexity Graph

The exploitability of CVE-2025-21865 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-21865

CVE-2025-21865 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-21865, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-21865, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2025-21865 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2025-21865 poses no threat to data integrity.
  • Availability: High
    CVE-2025-21865 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.042% (probability of exploit)

EPSS Percentile: 5.08% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 94.92% of others.

CVE-2025-21865 References

External References

CWE Common Weakness Enumeration

CWE-787

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.1.127:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1.127:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1.128:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1.128:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1.129:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1.129:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.74:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.74:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.75:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.75:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.76:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.76:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.77:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.77:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.78:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.78:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.79:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.79:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.4.290:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.4.290:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.10.234:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.10.234:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.177:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.177:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14:rc3:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-21865: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-25225 – A privilege escalation vulnerability in the Hikashop component versions 1.0.0-5.1.3 for Joomla allows authenticated attackers (administrator) to es...
  • CVE-2025-2323 – A vulnerability was found in 274056675 springboot-openai-chatgpt e84f6f5. It has been declared as problematic. This vulnerability affects the funct...
  • CVE-2025-2322 – A vulnerability was found in 274056675 springboot-openai-chatgpt e84f6f5. It has been classified as critical. This affects an unknown part of the f...
  • CVE-2025-2321 – A vulnerability was found in 274056675 springboot-openai-chatgpt e84f6f5 and classified as critical. Affected by this issue is some unknown functio...
  • CVE-2025-2025 – The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability...