CVE-2025-68768 Details
Description
In the Linux kernel, the following vulnerability has been resolved: inet: frags: flush pending skbs in fqdir_pre_exit() We have been seeing occasional deadlocks on pernet_ops_rwsem since September in NIPA. The stuck task was usually modprobe (often loading a driver like ipvlan), trying to take the lock as a Writer. lockdep does not track readers for rwsems so the read wasn't obvious from the reports. On closer inspection the Reader holding the lock was conntrack looping forever in nf_conntrack_cleanup_net_list(). Based on past experience with occasional NIPA crashes I looked thru the tests which run before the crash and noticed that the crash follows ip_defrag.sh. An immediate red flag. Scouring thru (de)fragmentation queues reveals skbs sitting around, holding conntrack references. The problem is that since conntrack depends on nf_defrag_ipv6, nf_defrag_ipv6 will load first. Since nf_defrag_ipv6 loads first its netns exit hooks run _after_ conntrack's netns exit hook. Flush all fragment queue SKBs during fqdir_pre_exit() to release conntrack references before conntrack cleanup runs. Also flush the queues in timer expiry handlers when they discover fqdir->dead is set, in case packet sneaks in while we're running the pre_exit flush. The commit under Fixes is not exactly the culprit, but I think previously the timer firing would eventually unblock the spinning conntrack.
A deadlock vulnerability has been identified in the Linux kernel's connection tracking system, specifically within the networking component that handles IP fragmentation. This issue arises because the connection tracking module can become stuck, preventing it from releasing network resources, which can lead to system hangs. The deadlock occurs when the IP defragmentation process leaves behind fragmented packets that are not properly cleaned up, causing the connection tracking system to loop indefinitely while trying to process these remnants. The problem is exacerbated by the order in which network modules are loaded and unloaded, particularly with IPv6 defragmentation, which can interfere with the normal operation of connection tracking. This vulnerability affects the Linux kernel stable tree.
The vulnerability has been addressed in a commit that flushes the fragmentation queues during the network namespace exit process, ensuring that all pending fragmented packets are properly handled before the connection tracking system is cleaned up. Users can apply this patch to their kernel to resolve the issue.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Jan 13, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/006a5035b495dec008805df249f92c22c89c3d2e | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/22ee4010866da81aeee08e1ea3fddbe418feb212 | kernel.org | |
| https://git.kernel.org/stable/c/543555954b1ee8d1903a7020324efb41b0c97428 | kernel.org | |
| https://git.kernel.org/stable/c/c70df25214ac9b32b53e18e6ae3b8f073ffa6903 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 19, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 9, 2026 | CVE Modified | kernel.org |
| Jan 13, 2026 | New CVE Received | kernel.org |
Volerion