CVE-2025-68240
Last modified
CVE-2025-68240 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: nilfs2: avoid having an active sc_timer before freeing sci Because kthread_stop did not stop sc_task properly and returned -EINTR, the sc_timer was not properly closed, ultimately causing the problem [1] reported by syzbot when freeing sci due to the sc_timer not being closed. Because the thread sc_task main function nilfs_segctor_thread() returns 0 when it succeeds, when the return value of kthread_stop() is not 0 in nilfs_segctor_destroy(), we believe that it has not properly closed sc_timer. We use timer_shutdown_sync() to sync wait for sc_timer to shutdown, and set the value of sc_task to NULL under the protection of lock sc_state_lock, so as to avoid the issue caused by sc_timer not being properly shutdowned. [1] ODEBUG: free active (active state 0) object: 00000000dacb411a object type: timer_list hint: nilfs_construction_timeout Call trace: nilfs_segctor_destroy fs/nilfs2/segment.c:2811 [inline] nilfs_detach_log_writer+0x668/0x8cc fs/nilfs2/segment.c:2877 nilfs_put_super+0x4c/0x12c fs/nilfs2/super.c:509. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: nilfs2: avoid having an active sc_timer before freeing sci Because kthread_stop did not stop sc_task properly and returned -EINTR, the sc_timer was not properly closed, ultimately causing the problem [1] reported by syzbot when freeing sci due to the sc_timer not being closed. Because the thread sc_task main function nilfs_segctor_thread() returns 0 when it succeeds, when the return value of kthread_stop() is not 0 in nilfs_segctor_destroy(), we believe that it has not properly closed sc_timer. We use timer_shutdown_sync() to sync wait for sc_timer to shutdown, and set the value of sc_task to NULL under the protection of lock sc_state_lock, so as to avoid the issue caused by sc_timer not being properly shutdowned. [1] ODEBUG: free active (active state 0) object: 00000000dacb411a object type: timer_list hint: nilfs_construction_timeout Call trace: nilfs_segctor_destroy fs/nilfs2/segment.c:2811 [inline] nilfs_detach_log_writer+0x668/0x8cc fs/nilfs2/segment.c:2877 nilfs_put_super+0x4c/0x12c fs/nilfs2/super.c:509
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 3f66cc261ccb54a8e4d8d5aa51c389c19453b00c, < 36049e81dc7f077e0e24d5b9688a7458beacef8f; >= 3f66cc261ccb54a8e4d8d5aa51c389c19453b00c, < 2f65799e2a736d556d306440c4e1e8906736117a; >= 3f66cc261ccb54a8e4d8d5aa51c389c19453b00c, < 9a6b60cb147d53968753a34805211d2e5e08c027 |
| Linux | Linux | 6.12 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-68240?
How severe is CVE-2025-68240?
How do I fix CVE-2025-68240?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-68235In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68236In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68237In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68238In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68239In the Linux kernel, the following vulnerability has been re…
- CVE-2025-6824A vulnerability classified as critical has been found in TOT…7.5
- CVE-2025-68241In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2025-68242In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68243In the Linux kernel, the following vulnerability has been re…7
- CVE-2025-68244In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68245In the Linux kernel, the following vulnerability has been re…
- CVE-2025-68246In the Linux kernel, the following vulnerability has been re…7.5
Are you affected by CVE-2025-68240?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
