> ...or someone spends a bit of time with an AI to come up with a patch?

Based on the guy's slides [0], it seems like Broadcom has already released a fixed version. The slide numbered as 97 contains this part of what I assume is an email with Broadcom:

  Thank you for your above-cited report. This report is based on Broadcom’s 18.1 SDK release.
  
  Broadcom has known about this specific vulnerability for a long time; other external entities have also reported it to us. For several years, Broadcom has been offering its customers updated software that lacks this vulnerability.
  
  In particular, the WPS implementation in this old software package (based on WPS Monitor) was obsoleted several years ago and replaced starting in 2018 by a new implementation based on HostAPD and WPA Supplicant.

The blog post makes it sound like there was no updated version, but the guy's email with Broadcom says otherwise. If we knew the name of the SDK, we could check the release notes and maybe get the truth. I gave up after like a minute of searching for the name, but perhaps others are more interested in the search than I am.

[0] <https://quentinkaiser.be/assets/qkaiser-broadcom-wps-hexacon...>

▲ SchemaLoad an hour ago | parent [-]

Broadcom just makes the chip right? So customers in this sense would be the router OEMs like netgear who may not have distributed the new update to end devices.

	▲	simoncion 30 minutes ago \| parent [-]
		> Broadcom just makes the chip right? And -based on the email- the SDK used by folks who use that chip in hardware, yes. So, yeah. The customers are the folks who build the hardware that uses that chip and the relevant parts of Broadcom's SDK as part of the software loaded into that hardware. Though it could totally be the ISP's fault for not testing and deploying updated firmware for affected CPE. There's not enough information to know exactly who is at fault, but it doesn't look like it's Broadcom.