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

Published Sep 5, 2025
·
Updated

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

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

When the length of the string written to setftracefilter exceeds FTRACEBUFFMAX, 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: showstack+0x34/0x50 (C) dumpstacklvl+0xa0/0x158 printaddressdescription.constprop.0+0x88/0x398 printreport+0xb0/0x280 kasanreport+0xa4/0xf0 asanreportload1noabort+0x20/0x30 strsep+0x18c/0x1b0 ftraceprocessregex.isra.0+0x100/0x2d8 ftraceregexrelease+0x484/0x618 fput+0x364/0xa58 fput+0x28/0x40 taskworkrun+0x154/0x278 donotifyresume+0x1f0/0x220 el0svc+0xec/0xf0 el0t64synchandler+0xa0/0xe8 el0t64sync+0x1ac/0x1b0

The reason is that tracegetuser will fail when processing a string longer than FTRACEBUFFMAX, but not set the end of parser->buffer to 0. Then an OOB access will be triggered in ftraceregexrelease-> ftraceprocessregex->strsep->strpbrk. We can solve this problem by limiting access to parser->buffer when tracegetuser failed.

Affected Software

19 affected componentsFixes available
Linux Kernel
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.96.2-1
Linux Linux kernel>=4.4.269<4.5
Linux Linux kernel>=4.9.269<4.10
Linux Linux kernel>=4.14.233<4.15
Linux Linux kernel>=4.19.191<4.20
Linux Linux kernel>=5.4.118<5.5
Linux Linux kernel>=5.10.36<5.10.241
Linux Linux kernel>=5.11.20<5.12
Linux Linux kernel>=5.12.3<5.15.190
Linux Linux kernel>=5.16<6.1.149
Linux Linux kernel>=6.2<6.6.103
Linux Linux kernel>=6.7<6.12.44
Linux Linux kernel>=6.13<6.16.4
Linux Linux kernel=6.17-rc1
Linux Linux kernel=6.17-rc2
Debian Debian Linux=11.0
Microsoft cbl2 kernel 5.15.186.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Apply the described fix: when trace_get_user fails while processing a string, ensure ftrace_regex_release/ftrace_process_regex limits access to parser->buffer and that the buffer end is correctly handled (i.e., avoid OOB by not reading past parser->buffer when the string length exceeds FTRACE_BUFF_MAX).

    Linux kernel ftrace Limit access to parser->buffer when trace_get_user failed = enabled

Event History

Sep 5, 2025
CVE Published
via MITRE·05:20 PM
Data Sourced
via MITRE·05:20 PM
DescriptionSeverity
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 7, 2025
Data Sourced
via Microsoft·01:14 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-39683?

CVE-2025-39683 is classified as a medium severity vulnerability due to its potential impact on the Linux kernel's stability.

2

How do I fix CVE-2025-39683?

To fix CVE-2025-39683, update your Linux kernel to a version that includes the patch for this vulnerability.

3

What does CVE-2025-39683 affect?

CVE-2025-39683 affects the Linux kernel, specifically the tracing subsystem related to ftrace filtering.

4

Can CVE-2025-39683 lead to system crashes?

Yes, CVE-2025-39683 can potentially lead to system crashes if the KASAN alarm is triggered due to excess string length.

5

How can I determine if my system is vulnerable to CVE-2025-39683?

You can determine if your system is vulnerable to CVE-2025-39683 by checking the kernel version and consulting security advisories for the necessary patches.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203