CVE-2025-39887 Vulnerability Analysis & Exploit Details

CVE-2025-39887
Vulnerability Scoring

5.5
/10
Significant Risk

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

Status: Modified

Last updated: 🕗 14 Jan 2026, 20:16 UTC
Originally published on: 🕕 23 Sep 2025, 06:15 UTC

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

CVE-2025-39887: In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Fix null-ptr-deref in bitmap_parselist() A crash was observed with the following output: BUG: kernel NULL pointer dereference, address: 0000000000000010 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 2 UID: 0 PID: 92 Comm: osnoise_cpus Not tainted 6.17.0-rc4-00201-gd69eb204c255 #138 PREEMPT(voluntary) RIP: 0010:bitmap_parselist+0x53/0x3e0 Call Trace: <TASK> osnoise_cpus_write+0x7a/0x190 vfs_write+0xf8/0x410 ? do_sys_openat2+0x88/0xd0 ksys_write+0x60/0xd0 do_syscall_64+0xa4/0x260 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> This issue can be reproduced by below code: fd=open("/sys/kernel/debug/tracing/osnoise/cpus", O_WRONLY); write(fd, "0-2", 0); When user pass 'count=0' to osnoise_cpus_write(), kmalloc() will return ZERO_SIZE_PTR (16) and cpulist_parse() treat it as a normal value, which trigger the null pointer dereference. Add check for the parameter 'count'.

Assessing the Risk of CVE-2025-39887

Access Complexity Graph

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

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

CVE-2025-39887 References

External References

CWE Common Weakness Enumeration

CWE-476

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.16:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.16:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.16.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.16.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.16.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.16.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.16.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.16.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.16.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.16.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.16.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.16.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.16.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.16.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.16.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.16.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.17:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.17:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.17:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.17:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.17:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.17:rc5:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-39887: 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-2026-23039 – In the Linux kernel, the following vulnerability has been resolved: drm/gud: fix NULL fb and crtc dereferences on USB disconnect On disconnect dr...
  • CVE-2026-23038 – In the Linux kernel, the following vulnerability has been resolved: pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() In nfs4_ff_a...
  • CVE-2026-23037 – In the Linux kernel, the following vulnerability has been resolved: can: etas_es58x: allow partial RX URB allocation to succeed When es58x_alloc_...
  • CVE-2026-23036 – In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before iget_failed() in btrfs_read_locked_inode() In btrf...
  • CVE-2026-23035 – In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv mlx5e_priv is ...