In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_exthdr: fix register tracking for F_PRESENT flag… (CVE-2026-53218)
In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_exthdr: fix register tracking for F_PRESENT flag nft_exthdr_init() passes user-controlled priv->len to nft_parse_register_store(), which marks that many bytes in the register bitmap as initialized. However, when NFT_EXTHDR_F_PRESENT is set, the eval paths write only 1 byte (nft_reg_store8) or 4 bytes (*dest = 0 on TCP/DCCP error path). When len > 4, registers beyond the first are never written, retaining uninitialized stack data from nft_regs. Bail out if userspace requests too much data when F_PRESENT is set.
AI Analysis
Technical Summary
The Linux kernel vulnerability CVE-2026-53218 concerns the netfilter nft_exthdr module where nft_exthdr_init() passes a user-controlled length (priv->len) to nft_parse_register_store(), marking that many bytes as initialized in the register bitmap. When the NFT_EXTHDR_F_PRESENT flag is set, the evaluation paths write only 1 byte (via nft_reg_store8) or 4 bytes (setting *dest = 0 on TCP/DCCP error paths). If the length exceeds 4, registers beyond the first remain uninitialized, potentially leaking stack data from nft_regs. The resolution involves adding a check to bail out if userspace requests more data than allowed when F_PRESENT is set.
Potential Impact
This vulnerability can lead to the retention of uninitialized stack data in registers, which may expose sensitive information or cause undefined behavior. The CVSS vector indicates no confidentiality or integrity impact but a high availability impact, suggesting potential denial of service or kernel stability issues. There is no indication of known exploits in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should monitor vendor communications for updates. No specific mitigations are provided in the available data.
In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_exthdr: fix register tracking for F_PRESENT flag… (CVE-2026-53218)
Description
In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_exthdr: fix register tracking for F_PRESENT flag nft_exthdr_init() passes user-controlled priv->len to nft_parse_register_store(), which marks that many bytes in the register bitmap as initialized. However, when NFT_EXTHDR_F_PRESENT is set, the eval paths write only 1 byte (nft_reg_store8) or 4 bytes (*dest = 0 on TCP/DCCP error path). When len > 4, registers beyond the first are never written, retaining uninitialized stack data from nft_regs. Bail out if userspace requests too much data when F_PRESENT is set.
CVSS v3.1
Score 5.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability CVE-2026-53218 concerns the netfilter nft_exthdr module where nft_exthdr_init() passes a user-controlled length (priv->len) to nft_parse_register_store(), marking that many bytes as initialized in the register bitmap. When the NFT_EXTHDR_F_PRESENT flag is set, the evaluation paths write only 1 byte (via nft_reg_store8) or 4 bytes (setting *dest = 0 on TCP/DCCP error paths). If the length exceeds 4, registers beyond the first remain uninitialized, potentially leaking stack data from nft_regs. The resolution involves adding a check to bail out if userspace requests more data than allowed when F_PRESENT is set.
Potential Impact
This vulnerability can lead to the retention of uninitialized stack data in registers, which may expose sensitive information or cause undefined behavior. The CVSS vector indicates no confidentiality or integrity impact but a high availability impact, suggesting potential denial of service or kernel stability issues. There is no indication of known exploits in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should monitor vendor communications for updates. No specific mitigations are provided in the available data.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3j78-pf43-6mvq
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53218"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a46eca927e9c7971943a6a9
Added to database: 07/02/2026, 22:56:41 UTC
Last enriched: 07/02/2026, 23:02:00 UTC
Last updated: 07/31/2026, 19:24:49 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.