CVE-2026-43116
Race Condition in Linux Kernel Netfilter ctnetlink
Publication date: 2026-05-06
Last updated on: 2026-05-08
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | From 6.19 (inc) to 6.19.14 (exc) |
| linux | linux_kernel | From 2.6.16 (inc) to 6.18.24 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's netfilter component, specifically in the ctnetlink subsystem that manages connection tracking expectations.
The issue arises because holding a reference on the expectation object alone is not sufficient to ensure the master conntrack object remains valid. The master conntrack object can be removed, making the reference (exp->master) invalid and potentially leading to unsafe access.
To fix this, the patch extends the locking mechanism (nf_conntrack_expect_lock) to ensure safe access to the master conntrack object by serializing access and holding proper references during operations such as adding, deleting, and getting expectations.
The fix involves expanding the spinlock sections to cover expectation lookups and moving certain operations outside the spinlock to maintain kernel memory allocation safety. It also includes delivering certain events under the spinlock and adding lock dependency annotations to help identify necessary locking paths.
How can this vulnerability impact me? :
This vulnerability can lead to unsafe access to kernel data structures related to connection tracking in the Linux kernel.
If exploited or triggered, it could cause kernel instability or crashes due to accessing invalid or freed memory (use-after-free conditions). This may result in denial of service or potentially other unpredictable behavior in systems relying on netfilter connection tracking.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved by extending the nf_conntrack_expect_lock section to ensure safe access to the master conntrack object in the Linux kernel netfilter ctnetlink subsystem.
Immediate mitigation involves applying the patch that extends the spinlock sections to cover expectation lookup and ensures proper locking when adding, deleting, or getting expectations.
Since this is a kernel-level fix, the recommended step is to update the Linux kernel to a version that includes this patch.