Answer in brief
CVE-2026-64413 records a Unknown severity vulnerability in netfilter: ebtables: zero chainstack array. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64413 records a Unknown severity vulnerability in netfilter: ebtables: zero chainstack array. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2ade612967e2cdfb9290ebcb773f302c82f311fa || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <42bef500d07b5769d916e9122a3e3fa3fd2245ef || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fc7f105451044501a50cfd530cfa3b472c54acbc || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9e6c5169db423e51dcc66a73fd15409c0d38e088 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <29bf41a9b59aff9f6197df58641a00037d567ca8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9f74d28e903fa4fdf82f870d0aeadddc8196e41c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5ee856e4208acafaaaf7b84824d39b78c21345d6 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cbfe53599eebffd188938ab6774cc41794f6f9d5 | 2ade612967e2cdfb9290ebcb773f302c82f311fa, 42bef500d07b5769d916e9122a3e3fa3fd2245ef, fc7f105451044501a50cfd530cfa3b472c54acbc, 9e6c5169db423e51dcc66a73fd15409c0d38e088, 29bf41a9b59aff9f6197df58641a00037d567ca8, 9f74d28e903fa4fdf82f870d0aeadddc8196e41c, 5ee856e4208acafaaaf7b84824d39b78c21345d6, cbfe53599eebffd188938ab6774cc41794f6f9d5 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2ade612967e2cdfb9290ebcb773f302c82f311fa || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <42bef500d07b5769d916e9122a3e3fa3fd2245ef || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fc7f105451044501a50cfd530cfa3b472c54acbc || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9e6c5169db423e51dcc66a73fd15409c0d38e088 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <29bf41a9b59aff9f6197df58641a00037d567ca8 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9f74d28e903fa4fdf82f870d0aeadddc8196e41c || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5ee856e4208acafaaaf7b84824d39b78c21345d6 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cbfe53599eebffd188938ab6774cc41794f6f9d5 | 2ade612967e2cdfb9290ebcb773f302c82f311fa, 42bef500d07b5769d916e9122a3e3fa3fd2245ef, fc7f105451044501a50cfd530cfa3b472c54acbc, 9e6c5169db423e51dcc66a73fd15409c0d38e088, 29bf41a9b59aff9f6197df58641a00037d567ca8, 9f74d28e903fa4fdf82f870d0aeadddc8196e41c, 5ee856e4208acafaaaf7b84824d39b78c21345d6, cbfe53599eebffd188938ab6774cc41794f6f9d5 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.