Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-53218netfilter: nft_exthdr: fix register tracking for F_PRESENT flag

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.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53218, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c078ca3b0c5bf82c2b31906c446d6e2ad8ea0783 – < 8738b1b6d0e639ca1fc0f61516afd3557ac4ecc6
    • affected c078ca3b0c5bf82c2b31906c446d6e2ad8ea0783 – < 19748967d59c31d24d21d40b728570788310b237
    • affected c078ca3b0c5bf82c2b31906c446d6e2ad8ea0783 – < 46fc15a044e9938e7ea77786fb37edd2cd74f031
    • affected c078ca3b0c5bf82c2b31906c446d6e2ad8ea0783 – < cd513e43b4b2bd1de39e2367bc4261c699a8652f
    • affected c078ca3b0c5bf82c2b31906c446d6e2ad8ea0783 – < 67b27434c43b68a97becda98c9f0c8cf6cba2134
    • affected c078ca3b0c5bf82c2b31906c446d6e2ad8ea0783 – < 78069a6d8bc86c9e036eb82c2af4a19cc1871a53
    • affected c078ca3b0c5bf82c2b31906c446d6e2ad8ea0783 – < f08fb3d42fd3aad0b7a263da3ac3ebaf0845e265
    • affected c078ca3b0c5bf82c2b31906c446d6e2ad8ea0783 – < 772cecf198da732faebb5dcfc46d66a505be8495
  • Linux · Linux

    • affected 4.11
    • unaffected < 4.11
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53218 badge
[![CVE-2026-53218](https://cveledger.app/badge/CVE-2026-53218.svg)](https://cveledger.app/cve/CVE-2026-53218)

Record last updated .