CVE-2021-47229: PCI: aardvark: Fix kernel panic during PIO transfer
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1a1dbc4473974867fe8c5f195c17b341c8e82867, 3d213a4ddf49a860be6e795482c17f87e0c82b2a, 400e6b1860c8be61388d0b77814c53260f96e17a.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1a1dbc4473974867fe8c5f195c17b341c8e82867, 3d213a4ddf49a860be6e795482c17f87e0c82b2a, 400e6b1860c8be61388d0b77814c53260f96e17a or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.14.240
- linux linux kernel4.15 and later · before 4.19.198
- linux linux kernel4.20 and later · before 5.4.128
- linux linux kernel5.5 and later · before 5.10.46
- linux linux kernel5.11 and later · before 5.12.13
- linux linux kernel5.13
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.8affected
- 8c39d710363c14ecb09219332869707395d1d495 and later · before 400e6b1860c8be61388d0b77814c53260f96e17aaffected · git
- 8c39d710363c14ecb09219332869707395d1d495 and later · before b00a9aaa4be20ad6e3311fb78a485eae0899e89aaffected · git
- 8c39d710363c14ecb09219332869707395d1d495 and later · before 4c90f90a91d75c3c73dd633827c90e8746d9f54daffected · git
- 8c39d710363c14ecb09219332869707395d1d495 and later · before 1a1dbc4473974867fe8c5f195c17b341c8e82867affected · git
- 8c39d710363c14ecb09219332869707395d1d495 and later · before 3d213a4ddf49a860be6e795482c17f87e0c82b2aaffected · git
- 8c39d710363c14ecb09219332869707395d1d495 and later · before f18139966d072dab8e4398c95ce955a9742e04f7affected · git
- before 4.8not affected · semver
- 4.14.240 and later · up to and including 4.14.*not affected · semver
- 4.19.198 and later · up to and including 4.19.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.10.46-1 | 5.10.46-1 |
| SUSE:Linux Enterprise High Availability Extension 12 SP5 | kernel-default | before 4.12.14-122.219.1 | 4.12.14-122.219.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-default-base | before 5.3.18-150200.24.194.1.150200.9.99.1 | 5.3.18-150200.24.194.1.150200.9.99.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-docs | before 5.3.18-150200.24.194.1 | 5.3.18-150200.24.194.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-obs-build | before 5.3.18-150200.24.194.1 | 5.3.18-150200.24.194.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-preempt | before 5.3.18-150200.24.194.1 | 5.3.18-150200.24.194.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-source | before 5.3.18-150200.24.194.1 | 5.3.18-150200.24.194.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-syms | before 5.3.18-150200.24.194.1 | 5.3.18-150200.24.194.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-64kb | before 5.3.18-150300.59.164.1 | 5.3.18-150300.59.164.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-default-base | before 5.3.18-150300.59.164.1.150300.18.96.1 | 5.3.18-150300.59.164.1.150300.18.96.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-docs | before 5.3.18-150300.59.164.1 | 5.3.18-150300.59.164.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-obs-build | before 5.3.18-150300.59.164.1 | 5.3.18-150300.59.164.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-preempt | before 5.3.18-150300.59.164.1 | 5.3.18-150300.59.164.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-source | before 5.3.18-150300.59.164.1 | 5.3.18-150300.59.164.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | kernel-syms | before 5.3.18-150300.59.164.1 | 5.3.18-150300.59.164.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_57 | before 1-8.3.1 | 1-8.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP2 | kernel-default | before 5.3.18-150200.24.194.1 | 5.3.18-150200.24.194.1 |
| SUSE:Linux Enterprise Live Patching 15 SP2 | kernel-livepatch-SLE15-SP2_Update_49 | before 1-150200.5.3.1 | 1-150200.5.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-default | before 5.3.18-150300.59.164.1 | 5.3.18-150300.59.164.1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_45 | before 1-150300.7.3.1 | 1-150300.7.3.1 |
| SUSE:Linux Enterprise Micro 5.1 | kernel-rt | before 5.3.18-150300.172.1 | 5.3.18-150300.172.1 |
| SUSE:Linux Enterprise Micro 5.1 | kernel-rt | before 5.3.18-150300.211.1 | 5.3.18-150300.211.1 |
| SUSE:Linux Enterprise Micro 5.1 | kernel-source-rt | before 5.3.18-150300.211.1 | 5.3.18-150300.211.1 |
| SUSE:Linux Enterprise Micro 5.1 | kernel-source-rt | before 5.3.18-150300.172.1 | 5.3.18-150300.172.1 |
+12
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47227May 21, 2024 · x86/fpu: Prevent state corruption in __fpu__restore_sig()22Monitor
- ← EarlierCVE-2021-47228May 21, 2024 · x86/ioremap: Map EFI-reserved memory as encrypted for SEV24Monitor
- Later →CVE-2021-47230May 21, 2024 · KVM: x86: Immediately reset the MMU context when the SMM flag is cleared26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1a1dbc4473974867fe8c5f195c17b341c8e82867 | Vendor (CNA) |
| Linux Linux | 3d213a4ddf49a860be6e795482c17f87e0c82b2a | Vendor (CNA) |
| Linux Linux | 400e6b1860c8be61388d0b77814c53260f96e17a | Vendor (CNA) |
| Linux Linux | 4c90f90a91d75c3c73dd633827c90e8746d9f54d | Vendor (CNA) |
| Linux Linux | b00a9aaa4be20ad6e3311fb78a485eae0899e89a | Vendor (CNA) |
| Linux Linux | f18139966d072dab8e4398c95ce955a9742e04f7 | Vendor (CNA) |
| debian:linux | 5.10.46-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-azure | 4.12.14-16.188.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-default | 5.3.18-150200.24.194.1 · SUSE:Linux Enterprise Live Patching 15 SP2 | Package registry (OSV) |
| suse:kernel-default-base | 5.3.18-150200.24.194.1.150200.9.99.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | Package registry (OSV) |
| suse:kernel-docs | 5.3.18-150200.24.194.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP2_Update_49 | 1-150200.5.3.1 · SUSE:Linux Enterprise Live Patching 15 SP2 | Package registry (OSV) |
| suse:kernel-obs-build | 5.3.18-150200.24.194.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | Package registry (OSV) |
| suse:kernel-rt | 4.12.14-10.188.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-rt_debug | 4.12.14-10.188.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-source-azure | 4.12.14-16.188.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-source-rt | 4.12.14-10.188.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-syms-azure | 4.12.14-16.188.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-syms-rt | 4.12.14-10.188.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0519 · May 22, 2024(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3d213a4ddf49a860be6e795482c17f87e0c82b2a
- git.kernel.org/stable/c/400e6b1860c8be61388d0b77814c53260f96e17a
- git.kernel.org/stable/c/4c90f90a91d75c3c73dd633827c90e8746d9f54d
- git.kernel.org/stable/c/b00a9aaa4be20ad6e3311fb78a485eae0899e89a
- git.kernel.org/stable/c/f18139966d072dab8e4398c95ce955a9742e04f7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.