First published: Tue May 21 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: PCI: aardvark: Fix kernel panic during PIO transfer Trying to start a new PIO transfer by writing value 0 in PIO_START register when previous transfer has not yet completed (which is indicated by value 1 in PIO_START) causes an External Abort on CPU, which results in kernel panic: SError Interrupt on CPU0, code 0xbf000002 -- SError Kernel panic - not syncing: Asynchronous SError Interrupt To prevent kernel panic, it is required to reject a new PIO transfer when previous one has not finished yet. If previous PIO transfer is not finished yet, the kernel may issue a new PIO request only if the previous PIO transfer timed out. In the past the root cause of this issue was incorrectly identified (as it often happens during link retraining or after link down event) and special hack was implemented in Trusted Firmware to catch all SError events in EL3, to ignore errors with code 0xbf000002 and not forwarding any other errors to kernel and instead throw panic from EL3 Trusted Firmware handler. Links to discussion and patches about this issue: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=3c7dcdac5c50 https://lore.kernel.org/linux-pci/20190316161243.29517-1-repk@triplefau.lt/ https://lore.kernel.org/linux-pci/971be151d24312cc533989a64bd454b4@www.loen.fr/ https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/1541 But the real cause was the fact that during link retraining or after link down event the PIO transfer may take longer time, up to the 1.44s until it times out. This increased probability that a new PIO transfer would be issued by kernel while previous one has not finished yet. After applying this change into the kernel, it is possible to revert the mentioned TF-A hack and SError events do not have to be caught in TF-A EL3.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | ||
Linux Kernel | <4.14.240 | |
Linux Kernel | >=4.15<4.19.198 | |
Linux Kernel | >=4.20<5.4.128 | |
Linux Kernel | >=5.5<5.10.46 | |
Linux Kernel | >=5.11<5.12.13 | |
Linux Kernel | =5.13-rc1 | |
Linux Kernel | =5.13-rc2 | |
Linux Kernel | =5.13-rc3 | |
Linux Kernel | =5.13-rc4 | |
Linux Kernel | =5.13-rc5 | |
Linux Kernel | =5.13-rc6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-47229 has been classified as a high-severity vulnerability due to its potential to cause kernel panic.
To fix CVE-2021-47229, update the Linux kernel to a version that includes the patch provided in the official updates.
CVE-2021-47229 affects certain versions of the Linux kernel that utilize the aardvark PCI driver.
The impact of CVE-2021-47229 can lead to instability, causing a system crash during PIO transfer operations.
CVE-2021-47229 is not considered a remote exploit as it requires local access to trigger the kernel panic.