CVE-2021-47498 json
dm rq: don't queue request to blk-mq during DM suspend
published 2024-05-22 2 y ago modified 2026-06-17 4 mo ago also EUVD-2021-34502
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
dm rq: don't queue request to blk-mq during DM suspend
DM uses blk-mq's quiesce/unquiesce to stop/start device mapper queue.
But blk-mq's unquiesce may come from outside events, such as elevator switch, updating nr_requests or others, and request may come during suspend, so simply ask for blk-mq to requeue it.
Fixes one kernel panic issue when running updating nr_requests and dm-mpath suspend/resume stress test.
Patch / fix
- Linux Linux 5.10.241, 5.14.14, 5.15
- linux Debian 14, Debian 13, Debian 12 5.14.16-1
debian advisories DEBIAN-CVE-2021-47498
- kernel RHEL 8 4.18.0-372.9.1.el8
- perf RHEL 8 4.18.0-372.9.1.el8
- bpftool RHEL 8 4.18.0-372.9.1.el8
- kernel-core RHEL 8 4.18.0-372.9.1.el8
- kernel-tools RHEL 8 4.18.0-372.9.1.el8
- python3-perf RHEL 8 4.18.0-372.9.1.el8
- kernel-modules RHEL 8 4.18.0-372.9.1.el8
- kernel-zfcpdump RHEL 8 4.18.0-372.9.1.el8
red hat advisories RHSA-2022:1988
- kernel-azure SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-16.194.1
- kernel-syms-azure SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-16.194.1
- kernel-source-azure SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-16.194.1
- kernel-syms SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.222.1
- kernel-source SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.222.1
- kernel-default SLES for SAP 12 SP5, SLES 12 SP5, SLE Workstation Extension 12 SP5 +2 more 4.12.14-122.222.1
- kernel-obs-build SLE Software Development Kit 12 SP5 4.12.14-122.222.1
- kernel-rt SLE Real Time 12 SP5 4.12.14-10.194.1
suse advisories SUSE-SU-2024:2901-1SUSE-SU-2024:2561-1SUSE-SU-2024:2493-1SUSE-SU-2024:2190-1SUSE-SU-2024:2189-1SUSE-SU-2024:2185-1
Vendor 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-47498 updated cvss 5.5
kernel: dm rq: don't queue request to blk-mq during DM suspend
-
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 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +6 moreaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux BaseOS (v. 8) perf 4.18.0-372.9.1.el8, kernel 4.18.0-372.9.1.el8, bpftool 4.18.0-372.9.1.el8, kernel-core 4.18.0-372.9.1.el8, kernel-tools 4.18.0-372.9.1.el8, python3-perf 4.18.0-372.9.1.el8, +15 more Red Hat Enterprise Linux CRB (v. 8) kernel-debuginfo-common-x86_64 4.18.0-372.9.1.el8, kernel-debuginfo-common-aarch64 4.18.0-372.9.1.el8, kernel-debuginfo-common-ppc64le 4.18.0-372.9.1.el8fixed: vendor fix RHSA-2022:1988
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more 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
- 2 y ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 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
- Technology feeds
References
Sources
- CVE List CVE-2021-47498
- NVD CVE-2021-47498
Fencer Vulns 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.