Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2025-39683

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: tracing: Limit access to parser->buffer when trace_get_user failed When the length of the string written to set_ftrace_filter e…

Published Sep 5, 2025CWE-125EPSS 0.18%

Overview

CVE-2025-39683 is a high-severity vulnerability. It was published on September 5, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

tracing: Limit access to parser->buffer when trace_get_user failed

When the length of the string written to set_ftrace_filter exceeds

FTRACE_BUFF_MAX, the following KASAN alarm will be triggered:

BUG: KASAN: slab-out-of-bounds in strsep+0x18c/0x1b0

Read of size 1 at addr ffff0000d00bd5ba by task ash/165

CPU: 1 UID: 0 PID: 165 Comm: ash Not tainted 6.16.0-g6bcdbd62bd56-dirty

Hardware name: linux,dummy-virt (DT)

Call trace:

show_stack+0x34/0x50 (C)

dump_stack_lvl+0xa0/0x158

print_address_description.constprop.0+0x88/0x398

print_report+0xb0/0x280

kasan_report+0xa4/0xf0

__asan_report_load1_noabort+0x20/0x30

strsep+0x18c/0x1b0

ftrace_process_regex.isra.0+0x100/0x2d8

ftrace_regex_release+0x484/0x618

__fput+0x364/0xa58

____fput+0x28/0x40

task_work_run+0x154/0x278

do_notify_resume+0x1f0/0x220

el0_svc+0xec/0xf0

el0t_64_sync_handler+0xa0/0xe8

el0t_64_sync+0x1ac/0x1b0

The reason is that trace_get_user will fa

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/3079517a5ba80901fe828a06998da64b9b8749beRefgit.kernel.org/stable/c/418b448e1d7470da9d4d4797f71782595ee69c49Refgit.kernel.org/stable/c/41b838420457802f21918df66764b6fbf829d330Refgit.kernel.org/stable/c/58ff8064cb4c7eddac4da1a59da039ead586950aRefgit.kernel.org/stable/c/6a909ea83f226803ea0e718f6e88613df9234d58Refgit.kernel.org/stable/c/b842ef39c2ad6156c13afdec25ecc6792a9b67b9Refgit.kernel.org/stable/c/d0c68045b8b0f3737ed7bd6b8c83b7887014adeeReflists.debian.org/debian-lts-announce/2025/10/msg00007.htmlReflists.debian.org/debian-lts-announce/2025/10/msg00008.htmlRefcert-portal.siemens.com/productcert/html/ssa-032379.html

How CyberStrike helps

Frequently asked questions

What is CVE-2025-39683?

CVE-2025-39683 is a high-severity vulnerability. It was published on September 5, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-39683?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-39683?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-39683?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-39683 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999