CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable
Noroxi assessment
Priority: Monitor (action score 0/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.20% (FIRST EPSS).
- Fixed version: Linux Linux 4099b98203d6b33d990586542fa5beee408032a3, 40c8ee40e48a2c82c762539952ed8fc0571db5bf, 7e3c96010ade29bb340a5bdce8675f50c7f59001.
Low priority for now. Upgrade to Linux Linux 4099b98203d6b33d990586542fa5beee408032a3, 40c8ee40e48a2c82c762539952ed8fc0571db5bf, 7e3c96010ade29bb340a5bdce8675f50c7f59001 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: ftrace: Fix softlockup in ftrace_module_enable A soft lockup was observed when loading amdgpu module. If a module has a lot of tracable functions, multiple calls to kallsyms_lookup can spend too much time in RCU critical section and with disabled preemption, causing kernel panic. This is the same issue that was fixed in commit d0b24b4e91fc ("ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY kernels") and commit 42ea22e754ba ("ftrace: Add cond_resched() to ftrace_graph_set_hash()"). Fix it the same way by adding cond_resched() in ftrace_module_enable.
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
—
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
- 4.5affected
- b7ffffbb46f205e7727a18bcc7a46c3c2b534f7c and later · before a1dd0abd741a8111260676da729825d6c1461a71affected · git
- b7ffffbb46f205e7727a18bcc7a46c3c2b534f7c and later · before e81e6d6d99b16dae11adbeda5c996317942a940caffected · git
- b7ffffbb46f205e7727a18bcc7a46c3c2b534f7c and later · before 40c8ee40e48a2c82c762539952ed8fc0571db5bfaffected · git
- b7ffffbb46f205e7727a18bcc7a46c3c2b534f7c and later · before 7e3c96010ade29bb340a5bdce8675f50c7f59001affected · git
- b7ffffbb46f205e7727a18bcc7a46c3c2b534f7c and later · before 4099b98203d6b33d990586542fa5beee408032a3affected · git
- before 4.5not affected · semver
- 6.1.159 and later · up to and including 6.1.*not affected · semver
- 6.6.117 and later · up to and including 6.6.*not affected · semver
- 6.12.58 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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.159-1 | 6.1.159-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.8-1 | 6.17.8-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.27.1.160000.2.8 | 6.12.0-160000.27.1.160000.2.8 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-azure | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-zfcpdump | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.27.1 | 6.12.0-160000.27.1 |
| SUSE:Linux Micro 6.2 | kernel-default-base | before 6.12.0-160000.27.1.160000.2.8 | 6.12.0-160000.27.1.160000.2.8 |
+4
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68171Dec 16, 2025 · x86/fpu: Ensure XFD state on signal delivery31Monitor
- ← EarlierCVE-2025-68172Dec 16, 2025 · crypto: aspeed - fix double free caused by devm0Monitor
- Later →CVE-2025-68174Dec 16, 2025 · amd/amdkfd: enhance kfd process check in switch partition31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4099b98203d6b33d990586542fa5beee408032a3 | Vendor (CNA) |
| Linux Linux | 40c8ee40e48a2c82c762539952ed8fc0571db5bf | Vendor (CNA) |
| Linux Linux | 7e3c96010ade29bb340a5bdce8675f50c7f59001 | Vendor (CNA) |
| Linux Linux | a1dd0abd741a8111260676da729825d6c1461a71 | Vendor (CNA) |
| Linux Linux | e81e6d6d99b16dae11adbeda5c996317942a940c | Vendor (CNA) |
| debian:linux | 6.1.159-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.27.1.160000.2.8 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.27.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.27.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-azure | 6.12.0-160000.27.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.27.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.27.1.160000.2.8 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.27.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.12.0-160000.27.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.27.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.27.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-rt | 6.12.0-160000.27.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.27.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-syms | 6.12.0-160000.27.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.12.0-160000.27.1 · SUSE:Linux Enterprise Server 16.0 | Package 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.
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 researchersFinders, 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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.