Answer in brief
CVE-2025-68768 records a Unknown severity vulnerability in inet: frags: flush pending skbs in fqdir_pre_exit(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d5dd88794a13c2f24cce31abad7a0a6c5e0ed2db <22ee4010866da81aeee08e1ea3fddbe418feb212 || >=d5dd88794a13c2f24cce31abad7a0a6c5e0ed2db <543555954b1ee8d1903a7020324efb41b0c97428 || >=d5dd88794a13c2f24cce31abad7a0a6c5e0ed2db <c70df25214ac9b32b53e18e6ae3b8f073ffa6903 || >=d5dd88794a13c2f24cce31abad7a0a6c5e0ed2db <006a5035b495dec008805df249f92c22c89c3d2e | 22ee4010866da81aeee08e1ea3fddbe418feb212, 543555954b1ee8d1903a7020324efb41b0c97428, c70df25214ac9b32b53e18e6ae3b8f073ffa6903, 006a5035b495dec008805df249f92c22c89c3d2e |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Jan 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.