CVE-2021-47319 json
virtio-blk: Fix memory leak among suspend/resume procedure
published 2y ago modified 4mo ago also EUVD-2021-34324
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
virtio-blk: Fix memory leak among suspend/resume procedure
The vblk->vqs should be freed before we call init_vqs() in virtblk_restore().
Patch / fix
- Linux Linux 4.4.276, 4.9.276, 4.14.240, 4.19.198, 5.4.134, 5.10.52, 5.12.19, 5.13.4, 5.14
- linux Debian 14, Debian 13, Debian 12 5.14.6-1
debian advisories DEBIAN-CVE-2021-47319
- linux Ubuntu 18.04 LTS 4.15.0-156.163
- linux Ubuntu 20.04 LTS 5.4.0-88.99
- linux-aws Ubuntu 18.04 LTS 4.15.0-1111.118
- linux-aws Ubuntu 20.04 LTS 5.4.0-1057.60
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1053.57
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1005.6
- linux-kvm Ubuntu 18.04 LTS 4.15.0-1099.101
- linux-kvm Ubuntu 20.04 LTS 5.4.0-1047.49
ubuntu advisories UBUNTU-CVE-2021-47319
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-syms SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.219.1
- kernel-source SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.219.1
- kernel-default SLES for SAP 12 SP5, SLES 12 SP5, SLE Workstation Extension 12 SP5 +2 more 4.12.14-122.219.1
- kernel-obs-build SLE Software Development Kit 12 SP5 4.12.14-122.219.1
- kernel-rt SLE Real Time 12 SP5 4.12.14-10.188.1
- kernel-syms-rt SLE Real Time 12 SP5 4.12.14-10.188.1
- kernel-rt_debug SLE Real Time 12 SP5 4.12.14-10.188.1
- kernel-source-rt SLE Real Time 12 SP5 4.12.14-10.188.1
suse advisories SUSE-SU-2024:2184-1SUSE-SU-2024:1983-1SUSE-SU-2024:1979-1
- git.kernel.org/stable/c/381bde79d11e596002edfd914e6714291826967a commit
- git.kernel.org/stable/c/102d6bc6475ab09bab579c18704e6cf8d898e93c commit
- git.kernel.org/stable/c/863da837964c80c72e368a4f748c30d25daa1815 commit
- git.kernel.org/stable/c/600942d2fd49b90e44857d20c774b20d16f3130f commit
- git.kernel.org/stable/c/04c6e60b884cb5e94ff32af46867fb41d5848358 commit
- git.kernel.org/stable/c/cd24da0db9f75ca11eaf6060f0ccb90e2f3be3b0 commit
- git.kernel.org/stable/c/ca2b8ae93a6da9839dc7f9eb9199b18aa03c3dae commit
- git.kernel.org/stable/c/29a2f4a3214aa14d61cc9737c9f886dae9dbb710 commit
- git.kernel.org/stable/c/b71ba22e7c6c6b279c66f53ee7818709774efa1f commit
Is CVE-2021-47319 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2021-47319 updated cvss 6.1
kernel: virtio-blk: Fix memory leak among suspend/resume procedure
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 moreaffected: no fix available
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
-
git.kernel.org
/stable/c/381bde79d11e596002edfd914e6714291826967a
patch
-
git.kernel.org
/stable/c/102d6bc6475ab09bab579c18704e6cf8d898e93c
patch
-
git.kernel.org
/stable/c/863da837964c80c72e368a4f748c30d25daa1815
patch
-
git.kernel.org
/stable/c/600942d2fd49b90e44857d20c774b20d16f3130f
patch
-
git.kernel.org
/stable/c/04c6e60b884cb5e94ff32af46867fb41d5848358
patch
-
git.kernel.org
/stable/c/cd24da0db9f75ca11eaf6060f0ccb90e2f3be3b0
patch
-
git.kernel.org
/stable/c/ca2b8ae93a6da9839dc7f9eb9199b18aa03c3dae
patch
-
git.kernel.org
/stable/c/29a2f4a3214aa14d61cc9737c9f886dae9dbb710
patch
-
git.kernel.org
/stable/c/b71ba22e7c6c6b279c66f53ee7818709774efa1f
patch
Sources
- CVE List CVE-2021-47319
- NVD CVE-2021-47319
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.