CVE-2026-43205dpaa2-switch: validate num_ifs to prevent out-of-bounds write
- 7.8HighCVSS base score
- 0.14%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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] |= ...
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 5 days later
· 5 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.14% · top 97% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < a26dda3bae469c8e4e1b1993ad33dafa32d0fc28
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < a3034a8d56174dd6464c46823438f25797910a8d
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < b690635d4719214892855b79ce018d4b1672ac96
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < 8b841fd529db9faf8bc678d429d4bf4e98b10900
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < 89764cf44544e943230f5e03b8c40a90da26537c
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < c18493f750208eb4ff1198fc5a02786b8b2d70a6
- affected 539dda3c5d190c5088b5e57944b1b482fcb464de – < 8a5752c6dcc085a3bfc78589925182e4e98468c5
- affected 5.13
- unaffected < 5.13
- unaffected 5.15.202 – ≤ 5.15.*
- unaffected 6.1.165 – ≤ 6.1.*
- unaffected 6.6.128 – ≤ 6.6.*
- unaffected 6.12.75 – ≤ 6.12.*
- unaffected 6.18.16 – ≤ 6.18.*
- unaffected 6.19.6 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References7
- https://git.kernel.org/stable/c/a26dda3bae469c8e4e1b1993ad33dafa32d0fc28 (opens in a new tab)
- https://git.kernel.org/stable/c/a3034a8d56174dd6464c46823438f25797910a8d (opens in a new tab)
- https://git.kernel.org/stable/c/b690635d4719214892855b79ce018d4b1672ac96 (opens in a new tab)
- https://git.kernel.org/stable/c/8b841fd529db9faf8bc678d429d4bf4e98b10900 (opens in a new tab)
- https://git.kernel.org/stable/c/89764cf44544e943230f5e03b8c40a90da26537c (opens in a new tab)
- https://git.kernel.org/stable/c/c18493f750208eb4ff1198fc5a02786b8b2d70a6 (opens in a new tab)
- https://git.kernel.org/stable/c/8a5752c6dcc085a3bfc78589925182e4e98468c5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-27768 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43205)Record last updated .