net: bridge: mrp: fix uninitialised bytes on the wire
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f7458934b0791c39a001e4d902fc3bf697b439b5 · < e08665218040f8e312abe40f74543186f3c2c941| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: mrp: fix uninitialised bytes on the wire
br_mrp_alloc_test_skb() builds MRP test frames on an skb from dev_alloc_skb(), which does not clear the linear data area. On the MRA ring-role branch the sub-option TLV header is appended with
sub_tlv = skb_put(skb, sizeof(*sub_tlv)); sub_tlv->type = BR_MRP_SUB_TLV_HEADER_TEST_AUTO_MGR;
so sub_tlv->length is never written, and the two trailing alignment bytes are appended with a bare skb_put() that does not clear them either. The neighbouring oui and sub_opt regions are explicitly zeroed, so three uninitialised bytes are left in every MRA MRP_Test frame that goes out.
Put the sub-option TLV header and the alignment padding in a single skb_put_zero(), which clears both. The AUTO_MGR sub-TLV carries no payload, so the zeroed length field is already the value it should have.
From the CVE record · Linux
The Linux kernel’s bridge MRP code leaves three uninitialized bytes in each MRA MRP_Test frame it sends. This can expose those bytes on the network when the MRA ring-role branch builds a test frame; the input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels that use bridge MRP should check their affected versions against the vendor advisory; no version range is provided.