CVE-2021-47048: spi: spi-zynqmp-gqspi: fix use-after-free in zynqmp_qspi_exec_op
In the Linux kernel, the following vulnerability has been resolved:
spi: spi-zynqmp-gqspi: fix use-after-free in zynqmp_qspi_exec_op
When handling op->addr, it is using the buffer "tmpbuf" which has been
freed. This will trigger a use-after-free KASAN warning. Let's use
temporary variables to store op->addr.val and op->cmd.opcode to fix
this issue.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47048 is a Linux kernel memory safety bug in the spi-zynqmp-gqspi driver. The driver could reuse a freed temporary buffer while handling SPI operation address data, producing a use-after-free condition. Public sources do not provide CVSS, impact detail, or evidence of active exploitation.
Executive priority
Give this medium priority for embedded or appliance fleets using affected Linux kernels and this SPI driver. For general server fleets without this driver path, urgency is lower, but kernel maintenance should still track vendor fixes.
Technical view
The issue is in zynqmp_qspi_exec_op. When processing op->addr, code referenced tmpbuf after it had been freed. The resolved fix stores op->addr.val and op->cmd.opcode in temporary variables before freeing the buffer. The source identifies affected Linux kernel version ranges but provides limited normalized version detail.
Likely exposure
Exposure appears limited to Linux systems running affected kernel builds that include and exercise the spi-zynqmp-gqspi driver. The bundle references Linux 5.10, 5.11, 5.12, and 5.13-related version data, but exact downstream vendor package exposure must be confirmed from vendor advisories.
Exploitation context
The source bundle does not cite public exploitation, proof-of-concept activity, or CISA KEV listing. It only describes a KASAN-detectable use-after-free in kernel driver code. Treat exploitability and operational impact as unconfirmed from the provided evidence.
Researcher notes
The evidence supports a resolved kernel use-after-free, not a proven exploitable attack path. The affected-version data in the bundle is sparse and partly normalized poorly, so validate against CVE JSON and upstream stable commits before declaring specific products affected.
Mitigation direction
Check Linux distribution or device vendor guidance for fixed kernel packages.
Prioritize updates on systems using the spi-zynqmp-gqspi driver.
Review the referenced stable kernel commits when maintaining custom kernels.
If patching is delayed, reduce reliance on affected hardware paths where feasible.
Validation and detection
Inventory deployed kernel versions across relevant Linux systems.
Determine whether spi-zynqmp-gqspi is built, loaded, or used.
Compare custom kernels with the referenced upstream stable commits.
Confirm vendor kernel packages include the upstream fix.
Monitor logs or testing for KASAN use-after-free findings if enabled.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-47048 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.