CVE-2021-47229

Summary

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.

Affected Software

VendorProductVersion RangeStatus
LinuxLinux8c39d710363c14ecb09219332869707395d1d495 < 400e6b1860c8be61388d0b77814c53260f96e17aaffected
LinuxLinux8c39d710363c14ecb09219332869707395d1d495 < b00a9aaa4be20ad6e3311fb78a485eae0899e89aaffected
LinuxLinux8c39d710363c14ecb09219332869707395d1d495 < 4c90f90a91d75c3c73dd633827c90e8746d9f54daffected
LinuxLinux8c39d710363c14ecb09219332869707395d1d495 < 1a1dbc4473974867fe8c5f195c17b341c8e82867affected
LinuxLinux8c39d710363c14ecb09219332869707395d1d495 < 3d213a4ddf49a860be6e795482c17f87e0c82b2aaffected
LinuxLinux8c39d710363c14ecb09219332869707395d1d495 < f18139966d072dab8e4398c95ce955a9742e04f7affected
LinuxLinux4.8affected
LinuxLinux0 < 4.8unaffected
LinuxLinux4.14.240 <= 4.14.*unaffected
LinuxLinux4.19.198 <= 4.19.*unaffected
LinuxLinux5.4.128 <= 5.4.*unaffected
LinuxLinux5.10.46 <= 5.10.*unaffected
LinuxLinux5.12.13 <= 5.12.*unaffected
LinuxLinux5.13 <= *unaffected

Weaknesses

ADP Enrichment

CVE Program Container

Additional References

CISA ADP Vulnrichment

  • SSVC:
  • Exploitation: none
    • Automatable: no
    • Technical Impact: partial

References