Two of the bugs AISLE highlighted are memory corruption primitives. They could be used in certain situations to crash a program that was running OpenSSL (like a web server), which is a denial of service risk. Because of modern compiler safety techniques, they can’t on their own be used to access data or run code, but they’re still concerning because it sometimes turns out to be possible to chain primitives like these into more dangerous exploits.
The third bug is a “timing side-channel bug” with a particular opt-in certificate algorithm that OpenSSL provides, when used on ARM architectures. It’s a pretty niche circumstance but it does look legitimate to me. The only way to know if it’s exploitable would be to try to build some kind of a PoC.
OpenSSL is a very hardened target, and lots of security researchers look at it. Any security-relevant bugs found on OpenSSL are pretty impressive.
The best privacy/security guide I am aware of is Michael Bazzells book. Michael Bazzell is a former computer crimes investigator, and his methods are red teamed at least in the sense that he works with e.g. people with extremely determined stalkers. Some things that book goes over that this doesn’t:
How to buy your home/car/P.O. box with LLCs and keep them out of your name, how to get a SIM card not tied to you personally.
The who/what/where of how your personal information (incl. address, phone number, etc.) gets collected in the first place, and ends up in public databases (which of course the government also leverages). What you can do about data already there, to the extent that you can do something.
(For people in really advanced situations) How to disinform in a way that actually works & ends up poisoning records, for example by taking up an electricity bill inside a building you don’t own.
Obviously the government has capabilities that private individuals don’t, so maybe the threat model here is different. For the most part though I would say that peoples’ biggest privacy/security risk is that there are infinity public databases with all of their personal information, and anybody with a credit card can pull up their address. Stopping the inflow to those should be priority #1 and the solution isn’t even really that digital, it’s just arcane legal procedures.