Skip to main content
VulnerabilityPublished Updated

CVE-2025-39829: Linux kernel · trace/fgraph: Fix the warning caused by missing unregister notifier

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-39829· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium · fixed in edede7a6dcd7435395cf757d053974aaab6ab1c2 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.15.5
Patch
Available – fixed in edede7a6dcd7435395cf757d053974aaab6ab1c2, aa977309397fe2438801b1ca1ce7bc4106d8e985, 3cfa337c1adceda1632aefee4c3562440446ce51 +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 4a2b8dda3f8705880ec7408135645602d5590f51, < edede7a6dcd7435395cf757d053974aaab6ab1c2
Fixed in
  • edede7a6dcd7435395cf757d053974aaab6ab1c2
LinuxLinuxAffected
  • ≥ 4a2b8dda3f8705880ec7408135645602d5590f51, < aa977309397fe2438801b1ca1ce7bc4106d8e985
Fixed in
  • aa977309397fe2438801b1ca1ce7bc4106d8e985
LinuxLinuxAffected
  • ≥ 4a2b8dda3f8705880ec7408135645602d5590f51, < 3cfa337c1adceda1632aefee4c3562440446ce51
Fixed in
  • 3cfa337c1adceda1632aefee4c3562440446ce51
LinuxLinuxAffected
  • ≥ 4a2b8dda3f8705880ec7408135645602d5590f51, < 2a2deb9f8df70480050351ac27041f19bb9e718b
Fixed in
  • 2a2deb9f8df70480050351ac27041f19bb9e718b
LinuxLinuxAffected
  • ≥ 4a2b8dda3f8705880ec7408135645602d5590f51, < 000aa47a51233fd38a629b029478e0278e1e9fbe
Fixed in
  • 000aa47a51233fd38a629b029478e0278e1e9fbe
LinuxLinuxAffected
  • =2.6.30
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: trace/fgraph: Fix the warning caused by missing unregister notifier This warning was triggered during testing on v6.16: notifier callback ftrace_suspend_notifier_call already registered WARNING: CPU: 2 PID: 86 at kernel/notifier.c:23 notifier_chain_register+0x44/0xb0 ... Call Trace: <TASK> blocking_notifier_chain_register+0x34/0x60 register_ftrace_graph+0x330/0x410 ftrace_profile_write+0x1e9/0x340 vfs_write+0xf8/0x420 ? filp_flush+0x8a/0xa0 ? filp_close+0x1f/0x30 ? do_dup2+0xaf/0x160 ksys_write+0x65/0xe0 do_syscall_64+0xa4/0x260 entry_SYSCALL_64_after_hwframe+0x77/0x7f When writing to the function_profile_enabled interface, the notifier was not unregistered after start_graph_tracing failed, causing a warning the next time function_profile_enabled was written. Fixed by adding unregister_pm_notifier in the exception path.

References

Community reviews

Loading reviews…