Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-39914: tracing: Silence warning when chunk allocation fails in trace_pid_write

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1262bda871dace8c6efae25f3b6a2d34f6f06d54, 7583a73c53f1d1ae7a39b130eb7190a11f0a902f, 793338906ff57d8c683f44fe48ca99d49c8782a7; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1.

Low priority for now. Upgrade to Linux Linux 1262bda871dace8c6efae25f3b6a2d34f6f06d54, 7583a73c53f1d1ae7a39b130eb7190a11f0a902f, 793338906ff57d8c683f44fe48ca99d49c8782a7; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: tracing: Silence warning when chunk allocation fails in trace_pid_write Syzkaller trigger a fault injection warning: WARNING: CPU: 1 PID: 12326 at tracepoint_add_func+0xbfc/0xeb0 Modules linked in: CPU: 1 UID: 0 PID: 12326 Comm: syz.6.10325 Tainted: G U 6.14.0-rc5-syzkaller #0 Tainted: [U]=USER Hardware name: Google Compute Engine/Google Compute Engine RIP: 0010:tracepoint_add_func+0xbfc/0xeb0 kernel/tracepoint.c:294 Code: 09 fe ff 90 0f 0b 90 0f b6 74 24 43 31 ff 41 bc ea ff ff ff RSP: 0018:ffffc9000414fb48 EFLAGS: 00010283 RAX: 00000000000012a1 RBX: ffffffff8e240ae0 RCX: ffffc90014b78000 RDX: 0000000000080000 RSI: ffffffff81bbd78b RDI: 0000000000000001 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000001 R12: ffffffffffffffef R13: 0000000000000000 R14: dffffc0000000000 R15: ffffffff81c264f0 FS: 00007f27217f66c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b2e80dff8 CR3: 00000000268f8000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> tracepoint_probe_register_prio+0xc0/0x110 kernel/tracepoint.c:464 register_trace_prio_sched_switch include/trace/events/sched.h:222 [inline] register_pid_events kernel/trace/trace_events.c:2354 [inline] event_pid_write.isra.0+0x439/0x7a0 kernel/trace/trace_events.c:2425 vfs_write+0x24c/0x1150 fs/read_write.c:677 ksys_write+0x12b/0x250 fs/read_write.c:731 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f We can reproduce the warning by following the steps below: 1. echo 8 >> set_event_notrace_pid. Let tr->filtered_pids owns one pid and register sched_switch tracepoint. 2. echo ' ' >> set_event_pid, and perform fault injection during chunk allocation of trace_pid_list_alloc. Let pid_list with no pid and assign to tr->filtered_pids. 3. echo ' ' >> set_event_pid. Let pid_list is NULL and assign to tr->filtered_pids. 4. echo 9 >> set_event_pid, will trigger the double register sched_switch tracepoint warning. The reason is that syzkaller injects a fault into the chunk allocation in trace_pid_list_alloc, causing a failure in trace_pid_list_set, which may trigger double register of the same tracepoint. This only occurs when the system is about to crash, but to suppress this warning, let's add failure handling logic to trace_pid_list_set.

Published
Oct 1, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-39914

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.16affected
    • 8d6e90983ade25ec7925211ac31d9ccaf64b7edf and later · before 7583a73c53f1d1ae7a39b130eb7190a11f0a902faffected · git
    • 8d6e90983ade25ec7925211ac31d9ccaf64b7edf and later · before 1262bda871dace8c6efae25f3b6a2d34f6f06d54affected · git
    • 8d6e90983ade25ec7925211ac31d9ccaf64b7edf and later · before 88525accf16947ab459f8e91c27c8c53e1d612d7affected · git
    • 8d6e90983ade25ec7925211ac31d9ccaf64b7edf and later · before 793338906ff57d8c683f44fe48ca99d49c8782a7affected · git
    • 8d6e90983ade25ec7925211ac31d9ccaf64b7edf and later · before cd4453c5e983cf1fd5757e9acb915adb1e4602b6affected · git
    • before 5.16not affected · semver
    • 6.1.153 and later · up to and including 6.1.*not affected · semver
    • 6.6.107 and later · up to and including 6.6.*not affected · semver
    • 6.12.48 and later · up to and including 6.12.*not affected · semver
Affected versions · NVD (6)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernel5.16 and later · before 6.1.153
  • linux linux kernel6.2 and later · before 6.6.107
  • linux linux kernel6.7 and later · before 6.12.48
  • linux linux kernel6.13 and later · before 6.16.8
  • linux linux kernel6.17

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.153-16.1.153-1
Debian:13linuxbefore 6.12.48-16.12.48-1
Debian:14linuxbefore 6.16.8-16.16.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-39912Oct 1, 2025 · nfs/localio: restore creds before releasing pageio data
    22Monitor
  • ← EarlierCVE-2025-39913Oct 1, 2025 · tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork.
    31Monitor
  • Later →CVE-2025-39915Oct 1, 2025 · net: phy: transfer phy_config_inband() locking responsibility to phylink
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1262bda871dace8c6efae25f3b6a2d34f6f06d54Vendor (CNA)
Linux Linux7583a73c53f1d1ae7a39b130eb7190a11f0a902fVendor (CNA)
Linux Linux793338906ff57d8c683f44fe48ca99d49c8782a7Vendor (CNA)
Linux Linux88525accf16947ab459f8e91c27c8c53e1d612d7Vendor (CNA)
Linux Linuxcd4453c5e983cf1fd5757e9acb915adb1e4602b6Vendor (CNA)
azl3 kernel 6.6.104.2-4 on Azure Linux 3.06.6.112.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.153-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-31608205 days apartsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()
    39Monitor
  • CVE-2026-31609205 days apartsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()
    39Monitor
  • CVE-2026-43011212 days apartnet/x25: Fix potential double free of skb
    39Monitor
  • CVE-2026-43414219 days apartscsi: qla2xxx: Completely fix fcport double free
    39Monitor
  • CVE-2026-52993266 days aparttipc: fix double-free in tipc_buf_append()
    39Monitor
  • CVE-2026-63888291 days apartscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()
    39Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-415 · Double Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records