Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2021-47566: proc/vmcore: fix clearing user buffer by properly using clear_user()

Noroxi assessment

Priority: Monitor (action score 31/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 33a7d698f30fa0b99d50569e9909d3baa65d8f6a, 7b3a34f08d11e7f05cd00b8e09adaa15192f0ad1, 99d348b82bcb36171f24411d3f1a15706a2a937a.

Low priority for now. Upgrade to Linux Linux 33a7d698f30fa0b99d50569e9909d3baa65d8f6a, 7b3a34f08d11e7f05cd00b8e09adaa15192f0ad1, 99d348b82bcb36171f24411d3f1a15706a2a937a 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: proc/vmcore: fix clearing user buffer by properly using clear_user() To clear a user buffer we cannot simply use memset, we have to use clear_user(). With a virtio-mem device that registers a vmcore_cb and has some logically unplugged memory inside an added Linux memory block, I can easily trigger a BUG by copying the vmcore via "cp": systemd[1]: Starting Kdump Vmcore Save Service... kdump[420]: Kdump is using the default log level(3). kdump[453]: saving to /sysroot/var/crash/127.0.0.1-2021-11-11-14:59:22/ kdump[458]: saving vmcore-dmesg.txt to /sysroot/var/crash/127.0.0.1-2021-11-11-14:59:22/ kdump[465]: saving vmcore-dmesg.txt complete kdump[467]: saving vmcore BUG: unable to handle page fault for address: 00007f2374e01000 #PF: supervisor write access in kernel mode #PF: error_code(0x0003) - permissions violation PGD 7a523067 P4D 7a523067 PUD 7a528067 PMD 7a525067 PTE 800000007048f867 Oops: 0003 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 468 Comm: cp Not tainted 5.15.0+ #6 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-27-g64f37cc530f1-prebuilt.qemu.org 04/01/2014 RIP: 0010:read_from_oldmem.part.0.cold+0x1d/0x86 Code: ff ff ff e8 05 ff fe ff e9 b9 e9 7f ff 48 89 de 48 c7 c7 38 3b 60 82 e8 f1 fe fe ff 83 fd 08 72 3c 49 8d 7d 08 4c 89 e9 89 e8 <49> c7 45 00 00 00 00 00 49 c7 44 05 f8 00 00 00 00 48 83 e7 f81 RSP: 0018:ffffc9000073be08 EFLAGS: 00010212 RAX: 0000000000001000 RBX: 00000000002fd000 RCX: 00007f2374e01000 RDX: 0000000000000001 RSI: 00000000ffffdfff RDI: 00007f2374e01008 RBP: 0000000000001000 R08: 0000000000000000 R09: ffffc9000073bc50 R10: ffffc9000073bc48 R11: ffffffff829461a8 R12: 000000000000f000 R13: 00007f2374e01000 R14: 0000000000000000 R15: ffff88807bd421e8 FS: 00007f2374e12140(0000) GS:ffff88807f000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f2374e01000 CR3: 000000007a4aa000 CR4: 0000000000350eb0 Call Trace: read_vmcore+0x236/0x2c0 proc_reg_read+0x55/0xa0 vfs_read+0x95/0x190 ksys_read+0x4f/0xc0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae Some x86-64 CPUs have a CPU feature called "Supervisor Mode Access Prevention (SMAP)", which is used to detect wrong access from the kernel to user buffers like this: SMAP triggers a permissions violation on wrong access. In the x86-64 variant of clear_user(), SMAP is properly handled via clac()+stac(). To fix, properly use clear_user() when we're dealing with a user buffer.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 24, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 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.

Follow CVE-2021-47566

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.0 and later · before 4.4.294
  • linux linux kernel4.5 and later · before 4.9.292
  • linux linux kernel4.10 and later · before 4.14.257
  • linux linux kernel4.15 and later · before 4.19.219
  • linux linux kernel4.20 and later · before 5.4.163
  • linux linux kernel5.5 and later · before 5.10.83
  • linux linux kernel5.11 and later · before 5.15.6
  • linux linux kernel5.16

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

    • 3.0affected
    • 997c136f518c5debd63847e78e2a8694f56dcf90 and later · before a9e164bd160be8cbee1df70acb379129e3cd2e7caffected · git
    • 997c136f518c5debd63847e78e2a8694f56dcf90 and later · before 33a7d698f30fa0b99d50569e9909d3baa65d8f6aaffected · git
    • 997c136f518c5debd63847e78e2a8694f56dcf90 and later · before 99d348b82bcb36171f24411d3f1a15706a2a937aaffected · git
    • 997c136f518c5debd63847e78e2a8694f56dcf90 and later · before 9ef384ed300d1bcfb23d0ab0b487d544444d4b52affected · git
    • 997c136f518c5debd63847e78e2a8694f56dcf90 and later · before fd7974c547abfb03072a4ee706d3a6f182266f89affected · git
    • 997c136f518c5debd63847e78e2a8694f56dcf90 and later · before a8a917058faf4abaec9fb614bb6d5f8fe3529ec6affected · git
    • 997c136f518c5debd63847e78e2a8694f56dcf90 and later · before 7b3a34f08d11e7f05cd00b8e09adaa15192f0ad1affected · git
    • 997c136f518c5debd63847e78e2a8694f56dcf90 and later · before c1e63117711977cc4295b2ce73de29dd17066c82affected · git
    • before 3.0not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.15.15-15.15.15-1
openSUSE:Leap 15.5dtb-aarch64before 5.14.21-150500.55.73.15.14.21-150500.55.73.1
openSUSE:Leap 15.5kernel-64kbbefore 5.14.21-150500.55.73.15.14.21-150500.55.73.1
openSUSE:Leap 15.5kernel-azurebefore 5.14.21-150500.33.60.15.14.21-150500.33.60.1
openSUSE:Leap 15.5kernel-debugbefore 5.14.21-150500.55.73.15.14.21-150500.55.73.1
openSUSE:Leap 15.5kernel-docsbefore 5.14.21-150500.55.73.25.14.21-150500.55.73.2
openSUSE:Leap 15.5kernel-kvmsmallbefore 5.14.21-150500.55.73.15.14.21-150500.55.73.1
openSUSE:Leap 15.5kernel-obs-buildbefore 5.14.21-150500.55.73.15.14.21-150500.55.73.1
openSUSE:Leap 15.5kernel-obs-qabefore 5.14.21-150500.55.73.15.14.21-150500.55.73.1
openSUSE:Leap 15.5kernel-rtbefore 5.14.21-150500.13.61.15.14.21-150500.13.61.1
openSUSE:Leap 15.5kernel-rt_debugbefore 5.14.21-150500.13.61.15.14.21-150500.13.61.1
openSUSE:Leap 15.5kernel-sourcebefore 5.14.21-150500.55.73.15.14.21-150500.55.73.1
openSUSE:Leap 15.5kernel-source-azurebefore 5.14.21-150500.33.60.15.14.21-150500.33.60.1
openSUSE:Leap 15.5kernel-source-rtbefore 5.14.21-150500.13.61.15.14.21-150500.13.61.1
openSUSE:Leap 15.5kernel-symsbefore 5.14.21-150500.55.73.15.14.21-150500.55.73.1
openSUSE:Leap 15.5kernel-syms-azurebefore 5.14.21-150500.33.60.15.14.21-150500.33.60.1
openSUSE:Leap 15.5kernel-syms-rtbefore 5.14.21-150500.13.61.15.14.21-150500.13.61.1
openSUSE:Leap 15.5kernel-zfcpdumpbefore 5.14.21-150500.55.73.15.14.21-150500.55.73.1
openSUSE:Leap Micro 5.5kernel-defaultbefore 5.14.21-150500.55.73.15.14.21-150500.55.73.1
openSUSE:Leap Micro 5.5kernel-default-basebefore 5.14.21-150500.55.73.1.150500.6.33.85.14.21-150500.55.73.1.150500.6.33.8
Red Hat:rhel_aus:8.6::baseosbpftoolbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseosbpftool-debuginfobefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernelbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-abi-stablelistsbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6

+80

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2021-47564May 24, 2024 · net: marvell: prestera: fix double free issue on err path
    31Monitor
  • ← EarlierCVE-2021-47565May 24, 2024 · scsi: mpt3sas: Fix kernel panic during drive powercycle test
    31Monitor
  • Later →CVE-2021-47567May 24, 2024 · powerpc/32: Fix hardlockup on vmap stack overflow
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux33a7d698f30fa0b99d50569e9909d3baa65d8f6aVendor (CNA)
Linux Linux7b3a34f08d11e7f05cd00b8e09adaa15192f0ad1Vendor (CNA)
Linux Linux99d348b82bcb36171f24411d3f1a15706a2a937aVendor (CNA)
Linux Linux9ef384ed300d1bcfb23d0ab0b487d544444d4b52Vendor (CNA)
Linux Linuxa8a917058faf4abaec9fb614bb6d5f8fe3529ec6Vendor (CNA)
Linux Linuxa9e164bd160be8cbee1df70acb379129e3cd2e7cVendor (CNA)
Linux Linuxc1e63117711977cc4295b2ce73de29dd17066c82Vendor (CNA)
Linux Linuxfd7974c547abfb03072a4ee706d3a6f182266f89Vendor (CNA)
debian:linux5.15.15-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch645.14.21-150500.55.73.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-64kb5.14.21-150500.55.73.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-azure5.14.21-150500.33.60.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-debug5.14.21-150500.55.73.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-default5.14.21-150500.55.73.1 · openSUSE:Leap Micro 5.5Package registry (OSV)
opensuse:kernel-default-base5.14.21-150500.55.73.1.150500.6.33.8 · openSUSE:Leap Micro 5.5Package registry (OSV)
opensuse:kernel-rt5.14.21-150500.13.61.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-rt_debug5.14.21-150500.13.61.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-source-azure5.14.21-150500.33.60.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-source-rt5.14.21-150500.13.61.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-syms-azure5.14.21-150500.33.60.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:kernel-syms-rt5.14.21-150500.13.61.1 · openSUSE:Leap 15.5Package registry (OSV)
red hat:bpftool0:4.18.0-372.118.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-372.118.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-372.118.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-372.118.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-372.118.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-372.118.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-372.118.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-372.118.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-372.118.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)

+15

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.

Finders, 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).

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records