CVE-2021-47229: 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…

PriorityP421medium5.5CVSS 3.1

AVLACLPRLUINSUCNINAH

EPSS

0.23%

13.4th percentile

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/[email protected]/ https://lore.kernel.org/linux-pci/[email protected]/ 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

18 ranges

Vendor	Product	Version range	Fixed in
debian	linux	< linux 5.10.46-1 (bookworm)	linux 5.10.46-1 (bookworm)
linux	linux	—	—
linux	linux	>= 8c39d710363c14ecb09219332869707395d1d495 < 400e6b1860c8be61388d0b77814c53260f96e17a	400e6b1860c8be61388d0b77814c53260f96e17a
linux	linux	>= 8c39d710363c14ecb09219332869707395d1d495 < b00a9aaa4be20ad6e3311fb78a485eae0899e89a	b00a9aaa4be20ad6e3311fb78a485eae0899e89a
linux	linux	>= 8c39d710363c14ecb09219332869707395d1d495 < 4c90f90a91d75c3c73dd633827c90e8746d9f54d	4c90f90a91d75c3c73dd633827c90e8746d9f54d
linux	linux	>= 8c39d710363c14ecb09219332869707395d1d495 < 1a1dbc4473974867fe8c5f195c17b341c8e82867	1a1dbc4473974867fe8c5f195c17b341c8e82867
linux	linux	>= 8c39d710363c14ecb09219332869707395d1d495 < 3d213a4ddf49a860be6e795482c17f87e0c82b2a	3d213a4ddf49a860be6e795482c17f87e0c82b2a
linux	linux	>= 8c39d710363c14ecb09219332869707395d1d495 < f18139966d072dab8e4398c95ce955a9742e04f7	f18139966d072dab8e4398c95ce955a9742e04f7
linux	linux_kernel	< 4.14.240	4.14.240
linux	linux_kernel	—	—
linux	linux_kernel	>= 0 < 5.10.46-1	5.10.46-1
linux	linux_kernel	>= 0 < 5.10.46-1	5.10.46-1
linux	linux_kernel	>= 0 < 5.10.46-1	5.10.46-1
linux	linux_kernel	>= 0 < 5.10.46-1	5.10.46-1
linux	linux_kernel	>= 4.15 < 4.19.198	4.19.198
linux	linux_kernel	>= 4.20 < 5.4.128	5.4.128
linux	linux_kernel	>= 5.11 < 5.12.13	5.12.13
linux	linux_kernel	>= 5.5 < 5.10.46	5.10.46

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

osv5.5MEDIUM

vendor_debian5.5MEDIUM

vendor_redhat5.5MEDIUM

Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.