Which one, and how "fixed" are they?
If you mean iOS 9.3, then not quite - iPad bricked by iOS 9.3?, Reg, by Shaun Nichols, 2016 March 24 :
We asked Reg readers if they had experienced this problem, and the responses came pouring in, along with tips for workarounds that at least let you use your iPad until Apple can come up with a fix. So, we've decided to share our collection of reader horror stories in the hopes that, should your iPad 2 be stricken by this malady, you can take some comfort in knowing that you're not alone. ..... < snip > ..... Apple has finally published a couple of suggested fixes if you get stuck installing iOS 9.3. It's also suspended downloads of the new OS for older iThings until it's sorted out the problems at its end. Earlier this week, word broke of a bug in Apple's iOS 9.3 update that was leaving some iPad 2 tablets unable to function.
The latest one is more fun / serious (depending on how you look at it) - Apple's fruitless rootless security broken by code that fits in a tweet, Reg, by Chris Williams, 2016 March 30 :
The Cupertino goliath fixed an exploitable bug in its rootless code in the latest round of patches for Macs and iThings. But that's the not the end of the story, we're told. Apple's rootless design, aka System Integrity Protection (SIP), marks sensitive directories in the computer's file system as being off-limits even to the root user. Normally, on Unix-flavored OSes, root is all powerful and can do whatever it likes. Well, Apple hates that idea: it means malware with elevated privileges or a clumsy user can infect or trash vital executables and other files. On OS X El Capitan, root is no longer allowed to rule the roost and take over all aspects of the computer. The way SIP works is simple: mark /System, /bin, /sbin and /usr except /usr/local with a special flag that means only programs with a particular attribute can modify files in those directories. And very few programs – the software update tool being one of them – are given this special com.apple.rootless permission to access SIP-guarded folders. A shell running as root certainly doesn't have it. There are other restrictions imposed by SIP, such as limiting the debugging of certain apps and the blocking of certain kernel extensions from being loaded. Earlier this month, Apple squashed a logic bug in SIP found by SentinelOne researcher Pedro Vilaça. It could be exploited by software already running on a Mac to bypass Apple's SIP defenses, rendering the safeguards useless. Vilaça demonstrated at the SyScan360 2016 conference the design weakness using GDB to modify and create files in /System as a normal root user. However, flaws within SIP remain. One problem is that just like bugs lingered in root-owned setuid binaries that were exploited by hackers, flaws present in SIP-entitled programs can be abused, too. ..... < snip > Apple's much-hyped rootless security mechanism in OS X can be evaded even in the latest version of the operating system, according to a top researcher.
Looks like Tim Cook picked the wrong fight with the wrong people at the wrong time. He could have handled things very quietly, just like he did before, and just like he is and will be doing with China — they can squeeze Apple in Chinese market and with Chinese manufacturing and materials (e.g., Hon Hai / Foxconn and some parts suppliers) much easier than the U.S. can with Huawei, Xiaomi or ZTE, for example — instead of going "full Snowden" on the phony "privacy" and "encryption backdoor" pretext.
Yes, the iOS 9.3 problem has been fixed. Apple has been pushed out that fixes the problem with the earlier iPads and some iPhones. . . it even fixes the link problem in Safari. Sorry, you are wrong. If you note, your article was dated a week ago.
As for the exploit that can fit in a Tweet, it requires physical possession of the computer and several complex other vulnerabilities to work. That required gaining access to some Apple signed software (note it said it worked by using software running on Macs already!) which is not such an easy thing to do. Your article dated yesterday on this was discussing a conference that occurred last week. It's old news already covered on FR.