netfilter: ebtables: zero chainstack array
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 9f74d28e903fa4fdf82f870d0aeadddc8196e41c| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s ebtables table translation can attempt to free an uninitialized pointer if the possible-CPU mask is sparse and an allocation fails. The input does not establish a way for an attacker to trigger this condition or specify network access, authentication, or user-interaction requirements; it says the allocation failure is not expected in practice.
Engineers running Linux kernels with ebtables should check whether their kernel is affected; affected versions are not specified.