net/sched: sch_netem: fix out-of-bounds access in packet corruption
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c865e5d99e25a171e8262fc0f7ba608568633c64 · < d64cb81dcbd54927515a7f65e5e24affdc73c14b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/sched: sch_netem: fix out-of-bounds access in packet corruption
In netem_enqueue(), the packet corruption logic uses get_random_u32_below(skb_headlen(skb)) to select an index for modifying skb->data. When an AF_PACKET TX_RING sends fully non-linear packets over an IPIP tunnel, skb_headlen(skb) evaluates to 0.
Passing 0 to get_random_u32_below() takes the variable-ceil slow path which returns an unconstrained 32-bit random integer. Using this unconstrained value as an offset into skb->data results in an out-of-bounds memory access.
Fix this by verifying skb_headlen(skb) is non-zero before attempting to corrupt the linear data area. Fully non-linear packets will silently bypass the corruption logic.
From the CVE record · Linux
The Linux kernel's netem packet corruption logic can access memory out of bounds when an AF_PACKET TX_RING sends fully non-linear packets over an IPIP tunnel. The access occurs because the packet's linear data length is zero, leaving the corruption offset unconstrained. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with netem packet corruption should check their installations; affected versions are not specified.