netfilter: nft_exthdr: fix register tracking for F_PRESENT flag
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c078ca3b0c5bf82c2b31906c446d6e2ad8ea0783 · < 78069a6d8bc86c9e036eb82c2af4a19cc1871a53| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s netfilter nft_exthdr code can mark more register bytes as initialized than it writes. This occurs when a userspace request sets NFT_EXTHDR_F_PRESENT with a length greater than 4, leaving uninitialized stack data in the remaining register bytes. The input does not specify authentication requirements or whether user interaction is needed.
Engineers running Linux kernels with netfilter nft_exthdr should check whether their kernel includes the fix; affected versions are not specified.