Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-39944: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp()

Noroxi assessment

Priority: Monitor (action score 31/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.15% (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 2786879aebf363806a13d41e8d5f99202ddd23d9, 5ca20bb7b4bde72110c3ae78423cbfdd0157aa36, d2cfefa14ce8137b17f99683f968bebf134b6a48.

Low priority for now. Upgrade to Linux Linux 2786879aebf363806a13d41e8d5f99202ddd23d9, 5ca20bb7b4bde72110c3ae78423cbfdd0157aa36, d2cfefa14ce8137b17f99683f968bebf134b6a48 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: octeontx2-pf: Fix use-after-free bugs in otx2_sync_tstamp() The original code relies on cancel_delayed_work() in otx2_ptp_destroy(), which does not ensure that the delayed work item synctstamp_work has fully completed if it was already running. This leads to use-after-free scenarios where otx2_ptp is deallocated by otx2_ptp_destroy(), while synctstamp_work remains active and attempts to dereference otx2_ptp in otx2_sync_tstamp(). Furthermore, the synctstamp_work is cyclic, the likelihood of triggering the bug is nonnegligible. A typical race condition is illustrated below: CPU 0 (cleanup) | CPU 1 (delayed work callback) otx2_remove() | otx2_ptp_destroy() | otx2_sync_tstamp() cancel_delayed_work() | kfree(ptp) | | ptp = container_of(...); //UAF | ptp-> //UAF This is confirmed by a KASAN report: BUG: KASAN: slab-use-after-free in __run_timer_base.part.0+0x7d7/0x8c0 Write of size 8 at addr ffff88800aa09a18 by task bash/136 ... Call Trace: <IRQ> dump_stack_lvl+0x55/0x70 print_report+0xcf/0x610 ? __run_timer_base.part.0+0x7d7/0x8c0 kasan_report+0xb8/0xf0 ? __run_timer_base.part.0+0x7d7/0x8c0 __run_timer_base.part.0+0x7d7/0x8c0 ? __pfx___run_timer_base.part.0+0x10/0x10 ? __pfx_read_tsc+0x10/0x10 ? ktime_get+0x60/0x140 ? lapic_next_event+0x11/0x20 ? clockevents_program_event+0x1d4/0x2a0 run_timer_softirq+0xd1/0x190 handle_softirqs+0x16a/0x550 irq_exit_rcu+0xaf/0xe0 sysvec_apic_timer_interrupt+0x70/0x80 </IRQ> ... Allocated by task 1: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x7f/0x90 otx2_ptp_init+0xb1/0x860 otx2_probe+0x4eb/0xc30 local_pci_probe+0xdc/0x190 pci_device_probe+0x2fe/0x470 really_probe+0x1ca/0x5c0 __driver_probe_device+0x248/0x310 driver_probe_device+0x44/0x120 __driver_attach+0xd2/0x310 bus_for_each_dev+0xed/0x170 bus_add_driver+0x208/0x500 driver_register+0x132/0x460 do_one_initcall+0x89/0x300 kernel_init_freeable+0x40d/0x720 kernel_init+0x1a/0x150 ret_from_fork+0x10c/0x1a0 ret_from_fork_asm+0x1a/0x30 Freed by task 136: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3a/0x60 __kasan_slab_free+0x3f/0x50 kfree+0x137/0x370 otx2_ptp_destroy+0x38/0x80 otx2_remove+0x10d/0x4c0 pci_device_remove+0xa6/0x1d0 device_release_driver_internal+0xf8/0x210 pci_stop_bus_device+0x105/0x150 pci_stop_and_remove_bus_device_locked+0x15/0x30 remove_store+0xcc/0xe0 kernfs_fop_write_iter+0x2c3/0x440 vfs_write+0x871/0xd70 ksys_write+0xee/0x1c0 do_syscall_64+0xac/0x280 entry_SYSCALL_64_after_hwframe+0x77/0x7f ... Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the delayed work item is properly canceled before the otx2_ptp is deallocated. This bug was initially identified through static analysis. To reproduce and test it, I simulated the OcteonTX2 PCI device in QEMU and introduced artificial delays within the otx2_sync_tstamp() function to increase the likelihood of triggering the bug.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Oct 4, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-39944

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

  • Stack 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

Affected versions

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

  • linux linux kernel6.1 and later · before 6.1.154
  • linux linux kernel6.2 and later · before 6.6.108
  • linux linux kernel6.7 and later · before 6.12.49
  • linux linux kernel6.13 and later · before 6.16.9
  • linux linux kernel6.17

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

    • 6.1affected
    • 2958d17a898416c6193431676f6130b68a2cb9fc and later · before 2786879aebf363806a13d41e8d5f99202ddd23d9affected · git
    • 2958d17a898416c6193431676f6130b68a2cb9fc and later · before d2cfefa14ce8137b17f99683f968bebf134b6a48affected · git
    • 2958d17a898416c6193431676f6130b68a2cb9fc and later · before ff27e23b311fed4d25e3852e27ba693416d4c7b3affected · git
    • 2958d17a898416c6193431676f6130b68a2cb9fc and later · before 5ca20bb7b4bde72110c3ae78423cbfdd0157aa36affected · git
    • 2958d17a898416c6193431676f6130b68a2cb9fc and later · before f8b4687151021db61841af983f1cb7be6915d4efaffected · git
    • before 6.1not affected · semver
    • 6.1.154 and later · up to and including 6.1.*not affected · semver
    • 6.6.108 and later · up to and including 6.6.*not affected · semver
    • 6.12.49 and later · up to and including 6.12.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:11linux-6.1before 6.1.158-1~deb11u16.1.158-1~deb11u1
Debian:12linuxbefore 6.1.158-16.1.158-1
Debian:13linuxbefore 6.12.57-16.12.57-1
Debian:14linuxbefore 6.16.9-16.16.9-1
openSUSE:Leap 15.6dtb-aarch64before 6.4.0-150600.23.81.16.4.0-150600.23.81.1
openSUSE:Leap 15.6kernel-64kbbefore 6.4.0-150600.23.81.36.4.0-150600.23.81.3
openSUSE:Leap 15.6kernel-azurebefore 6.4.0-150600.8.58.16.4.0-150600.8.58.1
openSUSE:Leap 15.6kernel-debugbefore 6.4.0-150600.23.81.36.4.0-150600.23.81.3
openSUSE:Leap 15.6kernel-defaultbefore 6.4.0-150600.23.81.36.4.0-150600.23.81.3
openSUSE:Leap 15.6kernel-default-basebefore 6.4.0-150600.23.81.3.150600.12.36.36.4.0-150600.23.81.3.150600.12.36.3
openSUSE:Leap 15.6kernel-docsbefore 6.4.0-150600.23.81.16.4.0-150600.23.81.1
openSUSE:Leap 15.6kernel-kvmsmallbefore 6.4.0-150600.23.81.36.4.0-150600.23.81.3
openSUSE:Leap 15.6kernel-obs-buildbefore 6.4.0-150600.23.81.36.4.0-150600.23.81.3
openSUSE:Leap 15.6kernel-obs-qabefore 6.4.0-150600.23.81.16.4.0-150600.23.81.1
openSUSE:Leap 15.6kernel-rtbefore 6.4.0-150600.10.61.16.4.0-150600.10.61.1
openSUSE:Leap 15.6kernel-rt_debugbefore 6.4.0-150600.10.61.16.4.0-150600.10.61.1
openSUSE:Leap 15.6kernel-sourcebefore 6.4.0-150600.23.81.26.4.0-150600.23.81.2
openSUSE:Leap 15.6kernel-source-azurebefore 6.4.0-150600.8.58.16.4.0-150600.8.58.1
openSUSE:Leap 15.6kernel-source-rtbefore 6.4.0-150600.10.61.16.4.0-150600.10.61.1
openSUSE:Leap 15.6kernel-symsbefore 6.4.0-150600.23.81.16.4.0-150600.23.81.1
openSUSE:Leap 15.6kernel-syms-azurebefore 6.4.0-150600.8.58.16.4.0-150600.8.58.1
openSUSE:Leap 15.6kernel-syms-rtbefore 6.4.0-150600.10.61.16.4.0-150600.10.61.1
openSUSE:Leap 15.6kernel-zfcpdumpbefore 6.4.0-150600.23.81.36.4.0-150600.23.81.3
openSUSE:Leap 16.0dtb-aarch64before 6.12.0-160000.8.16.12.0-160000.8.1

+61

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-39942Oct 4, 2025 · ksmbd: smbdirect: verify remaining_data_length respects max_fragmented_recv_size
    22Monitor
  • ← EarlierCVE-2025-39943Oct 4, 2025 · ksmbd: smbdirect: validate data_offset and data_length field of smb_direct_data_transfer
    28Monitor
  • Later →CVE-2025-39945Oct 4, 2025 · cnic: Fix use-after-free bugs in cnic_delete_task
    31Monitor

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 Linux2786879aebf363806a13d41e8d5f99202ddd23d9Vendor (CNA)
Linux Linux5ca20bb7b4bde72110c3ae78423cbfdd0157aa36Vendor (CNA)
Linux Linuxd2cfefa14ce8137b17f99683f968bebf134b6a48Vendor (CNA)
Linux Linuxf8b4687151021db61841af983f1cb7be6915d4efVendor (CNA)
Linux Linuxff27e23b311fed4d25e3852e27ba693416d4c7b3Vendor (CNA)
debian:linux6.1.158-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.158-1~deb11u1 · Debian:11Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.81.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.81.3 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.81.3 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.81.3 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.81.3.150600.12.36.3 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-docs6.4.0-150600.23.81.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-kvmsmall6.4.0-150600.23.81.3 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-build6.4.0-150600.23.81.3 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-qa6.4.0-150600.23.81.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source6.4.0-150600.23.81.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms6.4.0-150600.23.81.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-zfcpdump6.4.0-150600.23.81.3 · openSUSE:Leap 15.6Package registry (OSV)
suse:kernel-64kb6.4.0-150600.23.81.3 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-64kb6.4.0-150700.53.25.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-azure6.4.0-150600.8.58.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6Package registry (OSV)
suse:kernel-default6.4.0-150600.23.81.3 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-default6.4.0-150700.53.25.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-default-base6.4.0-150600.23.81.3.150600.12.36.3 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-default-base6.4.0-150700.53.25.1.150700.17.17.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-docs6.4.0-150600.23.81.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6Package registry (OSV)
suse:kernel-docs6.4.0-150700.53.25.2 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_181-150600.13.3.3 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7_Update_71-150700.15.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)

+9

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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

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

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

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

All records