ftrace: Fix potential warning in trace_printk_seq during ftrace_dump
In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump When calling ftrace_dump_one() concurrently with reading trace_pipe, a WARN_ON_ONCE() in trace_printk_seq() can be triggered due to a race condition. The issue occurs because: CPU0 (ftrace_dump) CPU1 (reader) echo z > /proc/sysrq-trigger !trace_empty(&iter) trace_iterator_reset(&iter) <- len = size = 0 cat /sys/kernel/tracing/trace_pipe trace_find_next_entry_inc(&iter) __find_next_entry ring_buffer_empty_cpu <- all empty return NULL trace_printk_seq(&iter.seq) WARN_ON_ONCE(s->seq.len >= s->seq.size) In the context between trace_empty() and trace_find_next_entry_inc() during ftrace_dump, the ring buffer data was consumed by other readers. This caused trace_find_next_entry_inc to return NULL, failing to populate `iter.seq`. At this point, due to the prior trace_iterator_reset, both `iter.seq.len` and `iter.seq.size` were set to 0. Since they are equal, the WARN_ON_ONCE condition is triggered. Move the trace_printk_seq() into the if block that checks to make sure the return value of trace_find_next_entry_inc() is non-NULL in ftrace_dump_one(), ensuring the 'iter.seq' is properly populated before subsequent operations.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.242, 5.15.191, 5.4.298, 6.1.150, 6.12.45, 6.16.5, 6.6.104
- CVEs
- CVE-2025-39813
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 07:45 UTC · Revision 1
Source evidence
ftrace: Fix potential warning in trace_printk_seq during ftrace_dump
core-osv · Original sourcePublished 16 Sept 2025, 13:00 UTC
In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump When calling ftrace_dump_one() concurrently with reading trace_pipe, a WARN_ON_ONCE() in trace_printk_seq() can be triggered due to a race condition. The issue occurs because: CPU0 (ftrace_dump) CPU1 (reader) echo z > /proc/sysrq-trigger !trace_empty(&iter) trace_iterator_reset(&iter) <- len = size = 0 cat /sys/kernel/tracing/trace_pipe trace_find_next_entry_inc(&iter) __find_next_entry ring_buffer_empty_cpu <- all empty return NULL trace_printk_seq(&iter.seq) WARN_ON_ONCE(s->seq.len >= s->seq.size) In the context between trace_empty() and trace_find_next_entry_inc() during ftrace_dump, the ring buffer data was consumed by other readers. This caused trace_find_next_entry_inc to return NULL, failing to populate `iter.seq`. At this point, due to the prior trace_iterator_reset, both `iter.seq.len` and `iter.seq.size` were set to 0. Since they are equal, the WARN_ON_ONCE condition is triggered. Move the trace_printk_seq() into the if block that checks to make sure the return value of trace_find_next_entry_inc() is non-NULL in ftrace_dump_one(), ensuring the 'iter.seq' is properly populated before subsequent operations.
osv:CVE-2025-39813
Kernel
Fixed versions: 5.4.298, 5.10.242, 5.15.191, 6.1.150, 6.6.104, 6.12.45, 6.16.5
Complete source record
{
"id": "cba48d9e58da380c006090f5b858ab9818524f75ceadcc7bddb56d78cf67b2d6",
"url": "https://osv.dev/vulnerability/CVE-2025-39813",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "ftrace: Fix potential warning in trace_printk_seq during ftrace_dump",
"summary": "In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump When calling ftrace_dump_one() concurrently with reading trace_pipe, a WARN_ON_ONCE() in trace_printk_seq() can be triggered due to a race condition. The issue occurs because: CPU0 (ftrace_dump) CPU1 (reader) echo z > /proc/sysrq-trigger !trace_empty(&iter) trace_iterator_reset(&iter) <- len = size = 0 cat /sys/kernel/tracing/trace_pipe trace_find_next_entry_inc(&iter) __find_next_entry ring_buffer_empty_cpu <- all empty return NULL trace_printk_seq(&iter.seq) WARN_ON_ONCE(s->seq.len >= s->seq.size) In the context between trace_empty() and trace_find_next_entry_inc() during ftrace_dump, the ring buffer data was consumed by other readers. This caused trace_find_next_entry_inc to return NULL, failing to populate `iter.seq`. At this point, due to the prior trace_iterator_reset, both `iter.seq.len` and `iter.seq.size` were set to 0. Since they are equal, the WARN_ON_ONCE condition is triggered. Move the trace_printk_seq() into the if block that checks to make sure the return value of trace_find_next_entry_inc() is non-NULL in ftrace_dump_one(), ensuring the 'iter.seq' is properly populated before subsequent operations.",
"evidence": "osv:CVE-2025-39813",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.298",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.242",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.191",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.150",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.104",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.45",
"evidence": "/affected/1/ranges"
},
{
"value": "6.16.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-39813",
"aliases": [
"CVE-2025-39813"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "d769041f865330034131525ee6a7f72eb4af2a24"
},
{
"fixed": "f299353e7ccbcc5c2ed8993c48fbe7609cbe729a"
},
{
"fixed": "5ab0ec206deb99eb3baf8f1d7602aeaa91dbcc85"
},
{
"fixed": "a6f0f8873cc30fd4543b09adf03f7f51d293f0e6"
},
{
"fixed": "e80ff23ba8bdb0f41a1afe2657078e4097d13a9a"
},
{
"fixed": "28c8fb7ae2ad27d81c8de3c4fe608c509f6a18aa"
},
{
"fixed": "ced94e137e6cd5e79c65564841d3b7695d0f5fa3"
},
{
"fixed": "fbd4cf7ee4db65ef36796769fe978e9eba6f0de4"
},
{
"fixed": "4013aef2ced9b756a410f50d12df9ebe6a883e4a"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-39813.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "2.6.28"
},
{
"fixed": "5.4.298"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.242"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.191"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.150"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.104"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.45"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.16.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-39813.json"
}
}
],
"modified": "2026-10-28T02:30:26.677015314Z",
"provider": "osv",
"references": [
"https://cert-portal.siemens.com/productcert/html/ssa-032379.html",
"https://git.kernel.org/stable/c/28c8fb7ae2ad27d81c8de3c4fe608c509f6a18aa",
"https://git.kernel.org/stable/c/4013aef2ced9b756a410f50d12df9ebe6a883e4a",
"https://git.kernel.org/stable/c/5ab0ec206deb99eb3baf8f1d7602aeaa91dbcc85",
"https://git.kernel.org/stable/c/a6f0f8873cc30fd4543b09adf03f7f51d293f0e6",
"https://git.kernel.org/stable/c/ced94e137e6cd5e79c65564841d3b7695d0f5fa3",
"https://git.kernel.org/stable/c/e80ff23ba8bdb0f41a1afe2657078e4097d13a9a",
"https://git.kernel.org/stable/c/f299353e7ccbcc5c2ed8993c48fbe7609cbe729a",
"https://git.kernel.org/stable/c/fbd4cf7ee4db65ef36796769fe978e9eba6f0de4",
"https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html",
"https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/39xxx/CVE-2025-39813.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-39813",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/39xxx/CVE-2025-39813.json"
}
},
"related_cves": [
{
"value": "CVE-2025-39813",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 493470,
"published_at": "2025-09-16T13:00:14.846+00:00"
}