All CPUs from all vendors have tons of bugs like this, which are mitigated in the operating system kernels, e.g. in the Linux kernel.
I am pretty certain that the Linux kernel must also contain specific code for various quirks of all Arm CPUs that have been used in the various Raspberry Pi models.
Intel had indeed several bugs that were more ugly than usual in their recent CPU models, like also MONITOR not working correctly in Lunar Lake, but even so, Intel still has better documentation for their CPU bugs than most vendors of Arm-based CPUs.
In any case, the bug that you linked was solved in the kernel years ago and it affects a privileged instruction that cannot be used in user programs. It does not have any direct relationship with memory and PCIe corruption. Memory corruption can occur inside the operating kernel only in certain circumstances, when the kernel changes the mapping of global memory pages and then writes the new pages, but the writes go to the old pages. However, this could happen only until 3 years ago, before the bug was known.
All CPUs from all vendors have tons of bugs like this, which are mitigated in the operating system kernels, e.g. in the Linux kernel.
I am pretty certain that the Linux kernel must also contain specific code for various quirks of all Arm CPUs that have been used in the various Raspberry Pi models.
Intel had indeed several bugs that were more ugly than usual in their recent CPU models, like also MONITOR not working correctly in Lunar Lake, but even so, Intel still has better documentation for their CPU bugs than most vendors of Arm-based CPUs.
In any case, the bug that you linked was solved in the kernel years ago and it affects a privileged instruction that cannot be used in user programs. It does not have any direct relationship with memory and PCIe corruption. Memory corruption can occur inside the operating kernel only in certain circumstances, when the kernel changes the mapping of global memory pages and then writes the new pages, but the writes go to the old pages. However, this could happen only until 3 years ago, before the bug was known.
so a single 3 year old errata for the n100 that was long since patched?