CVE-2026-43028: netfilter: x_tables: ensure names are nul-terminated
In the Linux kernel, the following vulnerability has been resolved:
netfilter: x_tables: ensure names are nul-terminated
Reject names that lack a \0 character before feeding them
to functions that expect c-strings.
Fixes tag is the most recent commit that needs this change.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux netfilter’s x_tables handling allows a locally authenticated, low-privileged attacker to supply a name without proper termination. This may expose sensitive kernel-related information or disrupt the system. The issue is high severity but is not remotely exploitable according to the supplied CVSS vector.
Executive priority
Use an accelerated patch cycle, prioritizing shared or multi-user Linux systems. This is a meaningful local confidentiality and availability risk, but the supplied evidence does not justify emergency internet-wide incident treatment. Require asset owners to verify vendor backports rather than relying only on version numbers.
Technical view
x_tables passed fixed-size names to C-string functions without first ensuring a NUL terminator was present. The kernel fix rejects unterminated names. CVSS 3.1 scores this 7.1, with local access, low complexity, low privileges, no user interaction, and potentially high confidentiality and availability impact.
Likely exposure
Linux systems containing the affected x_tables code are candidates, particularly hosts accessible to untrusted local users or workloads. Network exposure alone is insufficient because the vector is local. The supplied version entries do not establish unambiguous affected and fixed ranges, so distribution-specific backports must be checked.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. The CVSS vector indicates exploitation requires local low-privileged access but no user interaction. Reported impacts concern confidentiality and availability, not integrity.
Researcher notes
The source description identifies missing NUL-termination validation before C-string processing, but does not name the downstream functions, trigger path, CWE, or precise vulnerable branch boundaries. Stable commits are supplied across multiple kernel lines. Avoid inferring privilege escalation: the stated vector reports unchanged scope, no integrity impact, and high confidentiality and availability impact.
Mitigation direction
Check Linux distributor advisories for affected packages and approved fixed kernel builds.
Update to a supported kernel containing the applicable stable fix or vendor backport.
Prioritize shared systems where untrusted users or workloads have local access.
Apply normal access restrictions while patching; no specific workaround is documented in the bundle.
Validation and detection
Inventory running kernel versions across Linux hosts and appliances.
Compare package builds against distributor advisories, including documented backports.
Verify the installed kernel contains the corresponding upstream fix or vendor equivalent.
Reboot where required, confirm the running kernel, and regression-test netfilter operations.
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-43028 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.
1CVSS vectors
3Timeline events
1ADP providers
11Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.