netfilter: nft_meta_bridge: fix stale stack leak via IIFHWADDR register
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.367.0.137.1In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_meta_bridge: fix stale stack leak via IIFHWADDR register
NFT_META_BRI_IIFHWADDR declares its destination register with len = ETH_ALEN (6 bytes), which the register-init tracking rounds up to two 32-bit registers (8 bytes). nft_meta_bridge_get_eval() then does memcpy(dest, br_dev->dev_addr, ETH_ALEN), writing only 6 bytes and leaving the upper 2 bytes of the second register as uninitialised nft_do_chain() stack. A downstream load of that register span leaks those stale bytes to userspace.
Zero the second register before the memcpy so the full declared span is written.
From the CVE record · Linux
In the Linux kernel’s netfilter nft_meta_bridge component, the IIFHWADDR register leaves two bytes of stack data uninitialized. A downstream load of the register span can expose those stale bytes to userspace. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with the affected netfilter nft_meta_bridge component should check their versions; no affected versions are listed.