Skip to main content
VulnerabilityPublished Updated

CVE-2025-39813: Linux kernel · ftrace: Fix potential warning in trace_printk_seq during ftrace_dump

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in fbd4cf7ee4db65ef36796769fe978e9eba6f0de4 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:35 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in fbd4cf7ee4db65ef36796769fe978e9eba6f0de4, f299353e7ccbcc5c2ed8993c48fbe7609cbe729a, e80ff23ba8bdb0f41a1afe2657078e4097d13a9a +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ d769041f865330034131525ee6a7f72eb4af2a24, < fbd4cf7ee4db65ef36796769fe978e9eba6f0de4
Fixed in
  • fbd4cf7ee4db65ef36796769fe978e9eba6f0de4
LinuxLinuxAffected
  • ≥ d769041f865330034131525ee6a7f72eb4af2a24, < f299353e7ccbcc5c2ed8993c48fbe7609cbe729a
Fixed in
  • f299353e7ccbcc5c2ed8993c48fbe7609cbe729a
LinuxLinuxAffected
  • ≥ d769041f865330034131525ee6a7f72eb4af2a24, < e80ff23ba8bdb0f41a1afe2657078e4097d13a9a
Fixed in
  • e80ff23ba8bdb0f41a1afe2657078e4097d13a9a
LinuxLinuxAffected
  • ≥ d769041f865330034131525ee6a7f72eb4af2a24, < ced94e137e6cd5e79c65564841d3b7695d0f5fa3
Fixed in
  • ced94e137e6cd5e79c65564841d3b7695d0f5fa3
LinuxLinuxAffected
  • ≥ d769041f865330034131525ee6a7f72eb4af2a24, < a6f0f8873cc30fd4543b09adf03f7f51d293f0e6
Fixed in
  • a6f0f8873cc30fd4543b09adf03f7f51d293f0e6
LinuxLinuxAffected
  • ≥ d769041f865330034131525ee6a7f72eb4af2a24, < 4013aef2ced9b756a410f50d12df9ebe6a883e4a
Fixed in
  • 4013aef2ced9b756a410f50d12df9ebe6a883e4a

AI-suggested

A fix is available and has been applied in the Linux kernel source code as indicated by the fixed commit versions. Users and administrators should update to a Linux kernel version that includes these fixes to prevent the race condition and associated warnings. No additional mitigation steps are required beyond applying the official fix.

Description

A race condition in the Linux kernel's ftrace subsystem could trigger a warning (WARN_ON_ONCE) during concurrent calls to ftrace_dump_one() and reading from trace_pipe. This occurs because the ring buffer data may be consumed by other readers between checks, causing an unpopulated iterator sequence and triggering the warning. The issue has been fixed by moving the trace_printk_seq() call to ensure the iterator sequence is properly populated before use.

References

Community reviews

Loading reviews…