That bug was only created 20 Feb 2025. It usually takes at least 3 months (if you're lucky) for a fix to get into an actual IOS release so there's no chance of that being in a current release. Fixed status means dev team has devised a fix for the issue but it then goes into a queue for integration into the published releases. Depending on priority than can take anywhere up to a year. If you want to escalate it then as @marce1000 says you should open a TAC case. TAC can then ask dev team to get it into the next possible release.
17.9 has already gone End of Software Maintenance so unless you have a business case worth millions of $$$ depending on this fix, there is zero chance of it getting fixed in 17.9. 17.9.6 was published last year - before that bug was even opened so it's technically impossible for 17.9.6 to have the fix! 17.9.7 was released 21 March 2025 which means most fixes for that release would have been committed at least a month before - around the same time this bug was opened - so would have been impossible to even get it fixed in 17.9.7.
17.12.5 has already been released and it would also have been too late for that. So realistically, if you escalate, you might get this fixed in 17.12.6, which is at least 3 months away but it might even be too late for that if it hasn't already been committed. Should be safe to assume you could get it into 17.12.7 (at least 6 months away) but you should open a TAC case to make sure of that because if nobody is asking for a fix it can sometimes get de-prioritised.
Similarly for 17.15.4 and 17.15.5 which are the other releases it's likely to be targeted for.
One more thing: the bug is opened specifically for EWC but it probably affects all the 9800 series equally but EWC is End of Life now https://www.cisco.com/c/en/us/products/collateral/wireless/embedded-wireless-controller-catalyst-access-points/wireless-ewc-access-point-eol.html so if you're seeing it on 9800 WLC then make sure TAC are aware of that too.
