CVE-2025-38032 Vulnerability Analysis & Exploit Details

CVE-2025-38032
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2025-38032 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-38032 Details

Status: Analyzed

Last updated: 🕔 14 Nov 2025, 17:09 UTC
Originally published on: 🕙 18 Jun 2025, 10:15 UTC

Time between publication and last update: 149 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-38032 Vulnerability Summary

CVE-2025-38032: In the Linux kernel, the following vulnerability has been resolved: mr: consolidate the ipmr_can_free_table() checks. Guoyu Yin reported a splat in the ipmr netns cleanup path: WARNING: CPU: 2 PID: 14564 at net/ipv4/ipmr.c:440 ipmr_free_table net/ipv4/ipmr.c:440 [inline] WARNING: CPU: 2 PID: 14564 at net/ipv4/ipmr.c:440 ipmr_rules_exit+0x135/0x1c0 net/ipv4/ipmr.c:361 Modules linked in: CPU: 2 UID: 0 PID: 14564 Comm: syz.4.838 Not tainted 6.14.0 #1 Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:ipmr_free_table net/ipv4/ipmr.c:440 [inline] RIP: 0010:ipmr_rules_exit+0x135/0x1c0 net/ipv4/ipmr.c:361 Code: ff df 48 c1 ea 03 80 3c 02 00 75 7d 48 c7 83 60 05 00 00 00 00 00 00 5b 5d 41 5c 41 5d 41 5e e9 71 67 7f 00 e8 4c 2d 8a fd 90 <0f> 0b 90 eb 93 e8 41 2d 8a fd 0f b6 2d 80 54 ea 01 31 ff 89 ee e8 RSP: 0018:ffff888109547c58 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff888108c12dc0 RCX: ffffffff83e09868 RDX: ffff8881022b3300 RSI: ffffffff83e098d4 RDI: 0000000000000005 RBP: ffff888104288000 R08: 0000000000000000 R09: ffffed10211825c9 R10: 0000000000000001 R11: ffff88801816c4a0 R12: 0000000000000001 R13: ffff888108c13320 R14: ffff888108c12dc0 R15: fffffbfff0b74058 FS: 00007f84f39316c0(0000) GS:ffff88811b100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f84f3930f98 CR3: 0000000113b56000 CR4: 0000000000350ef0 Call Trace: <TASK> ipmr_net_exit_batch+0x50/0x90 net/ipv4/ipmr.c:3160 ops_exit_list+0x10c/0x160 net/core/net_namespace.c:177 setup_net+0x47d/0x8e0 net/core/net_namespace.c:394 copy_net_ns+0x25d/0x410 net/core/net_namespace.c:516 create_new_namespaces+0x3f6/0xaf0 kernel/nsproxy.c:110 unshare_nsproxy_namespaces+0xc3/0x180 kernel/nsproxy.c:228 ksys_unshare+0x78d/0x9a0 kernel/fork.c:3342 __do_sys_unshare kernel/fork.c:3413 [inline] __se_sys_unshare kernel/fork.c:3411 [inline] __x64_sys_unshare+0x31/0x40 kernel/fork.c:3411 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xa6/0x1a0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f84f532cc29 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f84f3931038 EFLAGS: 00000246 ORIG_RAX: 0000000000000110 RAX: ffffffffffffffda RBX: 00007f84f5615fa0 RCX: 00007f84f532cc29 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000040000400 RBP: 00007f84f53fba18 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f84f5615fa0 R15: 00007fff51c5f328 </TASK> The running kernel has CONFIG_IP_MROUTE_MULTIPLE_TABLES disabled, and the sanity check for such build is still too loose. Address the issue consolidating the relevant sanity check in a single helper regardless of the kernel configuration. Also share it between the ipv4 and ipv6 code.

Assessing the Risk of CVE-2025-38032

Access Complexity Graph

The exploitability of CVE-2025-38032 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-38032

CVE-2025-38032 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-38032, 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-38032, 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-38032 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2025-38032 poses no threat to data integrity.
  • Availability: High
    CVE-2025-38032 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2025-38032 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • 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:6.13.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14.8:*:*:*:*:*:*:*
  • 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.15:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15:rc7:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-38032: 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-13735 – Out-of-bounds Read vulnerability in ASR1903、ASR3901 in ASR Lapwing_Linux on Linux (nr_fw modules). This vulnerability is associated with program fi...
  • CVE-2025-9558 – There is a potential OOB Write vulnerability in the gen_prov_start function in pb_adv.c. The full length of the received data is copied into the li...
  • CVE-2025-9557 – ‭An out-of-bound write can lead to an arbitrary code execution. Even on devices with some form of memory protection, this can still lead to‬ ‭a cra...
  • CVE-2025-59820 – In KDE Krita before 5.2.13, loading a manipulated TGA file could result in a heap-based buffer overflow in plugins/impex/tga/kis_tga_import.cpp (ak...
  • CVE-2025-55174 – In KDE Skanpage before 25.08.0, an attempt at file overwrite can result in the contents of the new file at the beginning followed by the partial co...