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-64413netfilter: ebtables: zero chainstack array

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: ebtables: zero chainstack array sashiko reports: looking at ebtables table translation, could a sparse cpu_possible_mask lead to an uninitialized pointer free? If cpu_possible_mask is sparse (for example, CPU 0 and CPU 2 are possible, but CPU 1 is not), the allocation loop skips CPU 1. If vmalloc_node() fails at CPU 2, the cleanup loop will blindly decrement and call vfree() on newinfo->chainstack[1]. Not a real-world bug, such allocation isn't expected to fail in the first place.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 4 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-64413, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2ade612967e2cdfb9290ebcb773f302c82f311fa
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 42bef500d07b5769d916e9122a3e3fa3fd2245ef
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < fc7f105451044501a50cfd530cfa3b472c54acbc
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9e6c5169db423e51dcc66a73fd15409c0d38e088
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 29bf41a9b59aff9f6197df58641a00037d567ca8
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9f74d28e903fa4fdf82f870d0aeadddc8196e41c
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5ee856e4208acafaaaf7b84824d39b78c21345d6
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < cbfe53599eebffd188938ab6774cc41794f6f9d5
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .