Linux Kernel up to 6.6.151/6.12.103/6.18.44/7.1.8 Netfilter Conntrack nf_ct_l4proto_log_invalid deadlock

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.43- |
Summary
A vulnerability classified as critical was found in Linux Kernel up to 6.6.151/6.12.103/6.18.44/7.1.8. This vulnerability affects the function nf_ct_l4proto_log_invalid of the component Netfilter Conntrack. Executing a manipulation can lead to deadlock.
This vulnerability appears as CVE-2026-74624. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability classified as critical was found in Linux Kernel up to 6.6.151/6.12.103/6.18.44/7.1.8. This vulnerability affects the function nf_ct_l4proto_log_invalid of the component Netfilter Conntrack. The manipulation with an unknown input leads to a deadlock vulnerability. The CWE definition for the vulnerability is CWE-833. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. As an impact it is known to affect availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack: defer invalid log until after unlock TCP and SCTP conntrack paths can emit invalid-packet logs while ct->lock is still held. When invalid logging is routed to nfnetlink_log and conntrack export is enabled, the log path can re-enter conntrack netlink glue and dump the same conntrack again. Protocol attribute dumping may take ct->lock, so logging while holding that lock can deadlock. Defer the TCP invalid logs by storing only the minimal log context while ct->lock is held and emitting the log after unlocking. Also make the TCP timeout-lowering invalid path return whether a log is needed, then emit that log after unlocking. Do the same for the SCTP invalid state-transition log that can be reached while ct->lock is held. Add a lockdep assertion to nf_ct_l4proto_log_invalid() so future callers that log invalid conntracks while holding ct->lock are caught outside TCP and SCTP as well.
The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-74624 since 08/15/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/22/2026). The MITRE ATT&CK project declares the attack technique as T1499.
Upgrading to version 6.6.152, 6.12.104, 6.18.45 or 7.1.9 eliminates this vulnerability. Applying the patch 63853eb20bba4e00b7cd0b8cfc19337bbaaf5037/9480fcf70a5aa9d320088a01c95df0e5e6391f4a/0424186d570aa4d1ad17f516afb86bd9eaa4f42e/c0224327b7cbed9d3198e8dbec847281053dcd06/2d19b95c9723001f214f7a47d67b09f46238f200 is able to eliminate this problem.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 6.6.151
- 6.12.103
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.1.6
- 7.1.7
- 7.1.8
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: DeadlockCWE: CWE-833 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.6.152/6.12.104/6.18.45/7.1.9
Patch: 63853eb20bba4e00b7cd0b8cfc19337bbaaf5037/9480fcf70a5aa9d320088a01c95df0e5e6391f4a/0424186d570aa4d1ad17f516afb86bd9eaa4f42e/c0224327b7cbed9d3198e8dbec847281053dcd06/2d19b95c9723001f214f7a47d67b09f46238f200
Timeline
08/15/2026 CVE reserved08/22/2026 Advisory disclosed
08/22/2026 VulDB entry created
08/22/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-74624 (🔒)
GCVE (CVE): GCVE-0-2026-74624
GCVE (VulDB): GCVE-100-394408
Entry
Created: 08/22/2026 18:24Changes: 08/22/2026 18:24 (59)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.