CVE-2026-43205

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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] |= ...

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
—
EPSS
3.7%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 11, 2026

Advisory Details (7)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

dpaa2-switch: validate num_ifs to prevent out-of-bounds write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c18493f750208eb4ff1198fc5a02786b8b2d70a6
generic

dpaa2-switch: validate num_ifs to prevent out-of-bounds write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b690635d4719214892855b79ce018d4b1672ac96
generic

dpaa2-switch: validate num_ifs to prevent out-of-bounds write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a3034a8d56174dd6464c46823438f25797910a8d
generic

dpaa2-switch: validate num_ifs to prevent out-of-bounds write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a26dda3bae469c8e4e1b1993ad33dafa32d0fc28
generic

dpaa2-switch: validate num_ifs to prevent out-of-bounds write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b841fd529db9faf8bc678d429d4bf4e98b10900
generic

dpaa2-switch: validate num_ifs to prevent out-of-bounds write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a5752c6dcc085a3bfc78589925182e4e98468c5
generic

dpaa2-switch: validate num_ifs to prevent out-of-bounds write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89764cf44544e943230f5e03b8c40a90da26537c

Vendor Advisories for CVE-2026-43205(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.18.1.el10_22026-05-28redhat
linuxKernel @ 5.15.202—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 138 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 22:32 UTCOSV refresh
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-13 22:30 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-08 15:16 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-01 15:06 UTCEPSS rescore
  23. 2026-06-30 23:22 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 75 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-27 03:08 UTCEPSS rescore
  3. 2026-06-25 13:49 UTCEPSS rescore
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-24 14:05 UTCEPSS rescore
  6. 2026-06-23 21:33 UTCEPSS rescore
  7. 2026-06-22 14:25 UTCEPSS rescore
  8. 2026-06-22 14:25 UTCEPSS rescore
  9. 2026-06-21 14:56 UTCEPSS rescore
  10. 2026-06-21 14:56 UTCEPSS rescore
  11. 2026-06-21 01:59 UTCEPSS rescore
  12. 2026-06-19 19:25 UTCEPSS rescore
  13. 2026-06-18 17:52 UTCEPSS rescore
  14. 2026-06-18 17:52 UTCEPSS rescore
  15. 2026-06-17 17:53 UTCEPSS rescore
  16. 2026-06-16 17:52 UTCEPSS rescore
  17. 2026-06-15 17:49 UTCEPSS rescore
  18. 2026-06-15 06:25 UTCVendor advisory
  19. 2026-06-15 06:25 UTCGHSA enrichment
  20. 2026-06-14 18:59 UTCVendor advisory
  21. 2026-06-14 18:58 UTCGHSA enrichment
  22. 2026-06-14 07:36 UTCVendor advisory
  23. 2026-06-14 07:36 UTCGHSA enrichment
  24. 2026-06-13 23:00 UTCEPSS rescore
  25. 2026-06-13 00:00 UTCVendor advisory
  26. 2026-06-13 00:00 UTCGHSA enrichment
  27. 2026-06-12 23:12 UTCEPSS rescore
  28. 2026-06-12 23:12 UTCEPSS rescore
  29. 2026-06-12 08:09 UTCVendor advisory
  30. 2026-06-12 08:09 UTCGHSA enrichment
  31. 2026-06-11 20:45 UTCVendor advisory
  32. 2026-06-11 20:45 UTCGHSA enrichment
  33. 2026-06-11 14:00 UTCEPSS rescore
  34. 2026-06-11 09:24 UTCVendor advisory
  35. 2026-06-11 09:23 UTCGHSA enrichment
  36. 2026-06-10 22:18 UTCEPSS rescore
  37. 2026-06-10 21:54 UTCVendor advisory
  38. 2026-06-10 21:54 UTCGHSA enrichment
  39. 2026-06-10 13:22 UTCEPSS rescore
  40. 2026-06-10 13:22 UTCEPSS rescore
  41. 2026-06-10 10:32 UTCVendor advisory
  42. 2026-06-10 10:32 UTCGHSA enrichment
  43. 2026-06-09 23:03 UTCVendor advisory
  44. 2026-06-09 23:03 UTCGHSA enrichment
  45. 2026-06-09 11:08 UTCVendor advisory
  46. 2026-06-09 11:08 UTCGHSA enrichment
  47. 2026-06-08 23:46 UTCVendor advisory
  48. 2026-06-08 23:46 UTCGHSA enrichment
  49. 2026-06-08 14:17 UTCEPSS rescore
  50. 2026-06-08 14:17 UTCEPSS rescore
  51. 2026-06-08 12:24 UTCVendor advisory
  52. 2026-06-08 12:24 UTCGHSA enrichment
  53. 2026-06-08 01:02 UTCVendor advisory
  54. 2026-06-08 01:02 UTCGHSA enrichment
  55. 2026-06-07 15:25 UTCEPSS rescore
  56. 2026-06-07 15:25 UTCEPSS rescore
  57. 2026-06-07 13:41 UTCVendor advisory
  58. 2026-06-07 13:41 UTCGHSA enrichment
  59. 2026-06-07 02:19 UTCVendor advisory
  60. 2026-06-07 02:19 UTCGHSA enrichment
  61. 2026-06-06 14:56 UTCVendor advisory
  62. 2026-06-06 14:56 UTCGHSA enrichment
  63. 2026-06-06 13:47 UTCEPSS rescore
  64. 2026-06-06 13:47 UTCEPSS rescore
  65. 2026-06-06 03:34 UTCVendor advisory
  66. 2026-06-06 03:34 UTCGHSA enrichment
  67. 2026-06-05 22:47 UTCEPSS rescore
  68. 2026-06-05 15:59 UTCVendor advisory
  69. 2026-06-05 15:59 UTCGHSA enrichment
  70. 2026-06-05 06:10 UTCEPSS rescore
  71. 2026-06-05 06:10 UTCEPSS rescore
  72. 2026-06-05 04:36 UTCVendor advisory
  73. 2026-06-05 04:36 UTCGHSA enrichment
  74. 2026-06-04 17:14 UTCVendor advisory
  75. 2026-06-04 17:14 UTCGHSA enrichment

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43205?
CVE-2026-43205 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: validate num_ifs to prevent out-of-bounds write The driver obtains swattr.numifs from firmware via dpswgetattributes() but never validates it against DPSWMAXIF (64). This value controls iteration in…
When was CVE-2026-43205 disclosed?
CVE-2026-43205 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43205 actively exploited?
CVE-2026-43205 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43205?
CVE-2026-43205 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43205?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43205, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43205

Explore →

Is Your Infrastructure Affected by CVE-2026-43205?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs