CVE-2026-43026: netfilter: ctnetlink: zero expect NAT fields when CTA_EXPECT_NAT absent
In the Linux kernel, the following vulnerability has been resolved:
netfilter: ctnetlink: zero expect NAT fields when CTA_EXPECT_NAT absent
ctnetlink_alloc_expect() allocates expectations from a non-zeroing
slab cache via nf_ct_expect_alloc(). When CTA_EXPECT_NAT is not
present in the netlink message, saved_addr and saved_proto are
never initialized. Stale data from a previous slab occupant can
then be dumped to userspace by ctnetlink_exp_dump_expect(), which
checks these fields to decide whether to emit CTA_EXPECT_NAT.
The safe sibling nf_ct_expect_init(), used by the packet path,
explicitly zeroes these fields.
Zero saved_addr, saved_proto and dir in the else branch, guarded
by IS_ENABLED(CONFIG_NF_NAT) since these fields only exist when
NAT is enabled.
Confirmed by priming the expect slab with NAT-bearing expectations,
freeing them, creating a new expectation without CTA_EXPECT_NAT,
and observing that the ctnetlink dump emits a spurious
CTA_EXPECT_NAT containing stale data from the prior allocation.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can leak stale NAT expectation data to userspace when a ctnetlink expectation omits NAT attributes. The source describes information disclosure, not code execution. Severity, CVSS, and practical impact are not provided, so business urgency depends on exposed kernel versions and whether relevant netfilter/NAT functionality is enabled.
Executive priority
Treat as a kernel information-disclosure issue needing normal vulnerability management until vendor severity clarifies impact. Prioritize internet-facing, appliance, and regulated environments after confirming affected kernel exposure.
Technical view
ctnetlink_alloc_expect() allocates nf_conntrack expectations from non-zeroed slab memory. If CTA_EXPECT_NAT is absent, saved_addr, saved_proto, and dir remain uninitialized. ctnetlink_exp_dump_expect() may later emit CTA_EXPECT_NAT based on stale values. The fix zeroes these NAT-related fields when NAT is enabled.
Likely exposure
Potentially relevant to Linux systems using kernels identified by the CVE sources, especially where netfilter connection tracking expectations and CONFIG_NF_NAT are present. The bundle does not establish exact distribution package ranges or required attacker privileges.
Exploitation context
The CVE record says the issue was confirmed by controlled slab priming and ctnetlink dumping. KEV is false, and the supplied sources do not report active exploitation or public weaponization.
Researcher notes
The source evidence supports an uninitialized-field disclosure path in ctnetlink expectation dumping. It does not define exploit prerequisites, privilege boundaries, affected distro packages, CVSS, CWE, or exploitation in the wild.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced stable fixes.
Review Siemens advisories if using products covered by SSA-082556 or SSA-019113.
Track Linux stable commit references listed in the CVE source bundle.
If updates are unavailable, follow vendor guidance rather than applying unsupported kernel changes.
Validation and detection
Inventory Linux kernel versions across affected systems.
Check whether CONFIG_NF_NAT is enabled in deployed kernels.
Map deployed kernels to vendor advisories and referenced stable commits.
Review distribution changelogs for CVE-2026-43026 or listed commit IDs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43026 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
11Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 1, 2026, 14:15 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.