dpaa2-switch: validate num_ifs to prevent out-of-bounds write
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 539dda3c5d190c5088b5e57944b1b482fcb464de · < c18493f750208eb4ff1198fc5a02786b8b2d70a6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dpaa2-switch: validate num_ifs to prevent out-of-bounds write
The driver obtains sw_attr.num_ifs from firmware via dpsw_get_attributes() but never validates it against DPSW_MAX_IF (64). This value controls iteration in dpaa2_switch_fdb_get_flood_cfg(), which writes port indices into the fixed-size cfg->if_id[DPSW_MAX_IF] array. When firmware reports num_ifs >= 64, the loop can write past the array bounds.
Add a bound check for num_ifs in dpaa2_switch_init().
dpaa2_switch_fdb_get_flood_cfg() appends the control interface (port num_ifs) after all matched ports. When num_ifs == DPSW_MAX_IF and all ports match the flood filter, the loop fills all 64 slots and the control interface write overflows by one entry.
The check uses >= because num_ifs == DPSW_MAX_IF is also functionally broken.
build_if_id_bitmap() silently drops any ID >= 64: if (id[i] < DPSW_MAX_IF) bmap[id[i] / 64] |= ...
From the CVE record · Linux
The Linux kernel’s dpaa2-switch driver does not validate the number of interfaces reported by firmware before writing port IDs into a fixed-size array. A firmware-reported value of 64 or more can cause an out-of-bounds write; the input does not specify attacker access, authentication requirements, or user interaction.
Engineers running Linux kernels with the dpaa2-switch driver should check their versions against the vendor advisory; affected versions are not specified.