Description
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.
Published: 2026-05-01
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability resides in the Linux kernel's netfilter ctnetlink module. When a netlink message omits the CTA_EXPECT_NAT flag, the allocation routine pulls memory from a non‑zeroing slab, leaving fields such as saved_addr and saved_proto uninitialized, reflecting a CWE-824 weakness. A subsequent dump operation then reads these stale values and can expose them to userspace, revealing former NAT configuration data that should not have been disclosed.

Affected Systems

All Linux kernel distributions are affected as the flaw exists in core kernel code. No specific kernel version is provided, so any kernel that has not incorporated the commit that zeroes these fields may be vulnerable. Users should verify whether the referenced commit is present in their kernel and, if not, apply the appropriate update.

Risk and Exploitability

The CVSS score is 5.5, indicating moderate severity. EPSS data is not available and the vulnerability is not listed in CISA KEV, suggesting no known exploitation. The likely attack vector is local via the ctnetlink netlink interface, and the required privilege level is inferred to be local user access capable of sending and reading netlink messages. The inference is marked because the description does not explicitly state the vector or privilege. Exploitation would allow an attacker to read stale NAT configuration data, which may aid in reconnaissance but does not provide direct code execution or privilege escalation.

Generated by OpenCVE AI on May 2, 2026 at 11:37 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the commit which zeros the uninitialized expectation fields.
  • If an update is not immediately available, restrict access to the ctnetlink interface by configuring netlink permissions or applying capabilities constraints so that only trusted users can send or receive ctnetlink messages.
  • If you cannot change permissions or update the kernel, consider hacking the kernel source to copy the zero‑initialization logic from a newer kernel into the kernel you use and recompiling.

Generated by OpenCVE AI on May 2, 2026 at 11:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4561-1 linux-6.1 security update
Debian DSA Debian DSA DSA-6243-1 linux security update
History

Sat, 02 May 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-824
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Fri, 01 May 2026 14:45:00 +0000

Type Values Removed Values Added
Description 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.
Title netfilter: ctnetlink: zero expect NAT fields when CTA_EXPECT_NAT absent
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-05-01T14:15:27.854Z

Reserved: 2026-05-01T14:12:55.976Z

Link: CVE-2026-43026

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-05-01T15:16:47.033

Modified: 2026-05-01T15:24:14.893

Link: CVE-2026-43026

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-05-01T00:00:00Z

Links: CVE-2026-43026 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-05-02T11:45:41Z

Weaknesses