According to https://www.kb.cert.org/vuls/id/918987/ either side can propose a new amount of entropy and the other side can accept or reject it. An updated controller firmware on either side could reject the connection.
Another option mentioned in the paper is for the OS to check the entropy level and close the connection after each renegotiation. I'm not sure if OSes have actually been updated to do that, but it would work for all kinds of devices even without hardware vendor support.
A rejected connection means a bricked device, on the other hand. Sure, newer drivers could protect me against attacks, but simultaneously prevent me from using my BT headphones.
Hopefully this would only be an issue during an attack. Not sure why your headphones would be legitimately negotiating encryption but then only supporting <7 bytes of entropy.
Another option mentioned in the paper is for the OS to check the entropy level and close the connection after each renegotiation. I'm not sure if OSes have actually been updated to do that, but it would work for all kinds of devices even without hardware vendor support.