csirt@kutim:~/threat-intel/cve/CVE-2021-47229

Katalog CVE

CVSS 5.5 · Medium EPSS 0,23%

Kerentanan pada linux kernel. Skor CVSS 3.1 5.5 (Medium) menurut NVD.

Deskripsi (NVD)

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.

Rincian

Terbit di NVD
21 Mei 2024
Terakhir diubah
17 Juni 2026
Status NVD
Analyzed
CVSS 3.1
5.5 (Medium), sumber NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H · uraikan di kalkulator
EPSS (30 hari)
0,23% peluang dieksploitasi; lebih tinggi dari 12,3% CVE lain

Produk dan versi terdampak

VendorProdukVersi terdampak
linux linux kernel Semua versi sebelum 4.14.240
linux linux kernel Versi 4.15 hingga sebelum 4.19.198
linux linux kernel Versi 4.20 hingga sebelum 5.4.128
linux linux kernel Versi 5.5 hingga sebelum 5.10.46
linux linux kernel Versi 5.11 hingga sebelum 5.12.13
linux linux kernel Versi 5.13 rc1
linux linux kernel Versi 5.13 rc2
linux linux kernel Versi 5.13 rc3
linux linux kernel Versi 5.13 rc4
linux linux kernel Versi 5.13 rc5
linux linux kernel Versi 5.13 rc6

> Data dari konfigurasi CPE di NVD.

Referensi dan perbaikan

Sumber: NVD · CVE.org · EPSS. Halaman ini disusun otomatis dari data tersebut; pembaruan terakhir 5 Okt 2026, 20:10 WITA. Kalau sistem di Perangkat Daerah memakai produk ini dan butuh bantuan, laporkan lewat kanal pelaporan.