CVE-2025-39813: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump
Published Sep 16, 2025
·Updated
ftrace: Fix potential warning in traceprintkseq during ftracedump
Affected Software
13 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.96.2-2
Linux Linux kernel>=2.6.28<5.4.298
Linux Linux kernel>=5.5<5.10.242
Linux Linux kernel>=5.11<5.15.191
Linux Linux kernel>=5.16<6.1.150
Linux Linux kernel>=6.2<6.6.104
Linux Linux kernel>=6.7<6.12.45
Linux Linux kernel>=6.13<6.16.5
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
Event History
Sep 16, 2025
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
Description
Data Sourced
via NVD·01:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 20, 2025
Data Sourced
via Microsoft·01:07 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:07 AM
DescriptionSeverity
Updated
via Microsoft·08:07 AM
SeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-39813?
CVE-2025-39813 is classified as a low severity vulnerability in the Linux kernel.
2
How does CVE-2025-39813 affect the Linux kernel?
CVE-2025-39813 affects the Linux kernel by introducing a potential warning in trace_printk_seq during concurrent operations.
3
How do I fix CVE-2025-39813?
To fix CVE-2025-39813, users should update to the latest stable version of the Linux kernel where this issue has been resolved.
4
What are the implications of CVE-2025-39813 on system performance?
The implications of CVE-2025-39813 on system performance include potential warnings which may affect the logging functionality during concurrent tracing.
5
Is CVE-2025-39813 limited to specific Linux kernel versions?
CVE-2025-39813 affects versions of the Linux kernel that utilize the ftrace subsystem, particularly where concurrent trace read and dump operations occur.