Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2021-47118: pid: take a reference when initializing `cad_pid`

HighCVSS 7.8 · v3.1—No exploit Fix available

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.24% (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 0711f0d7050b9e07c44bc159bbc64ac0a1022c7f, 2cd6eedfa6344f5ef5c3dac3aee57a39b5b46dff, 4dbd8808a591b49b717862e6e0081bcf14a87788.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0711f0d7050b9e07c44bc159bbc64ac0a1022c7f, 2cd6eedfa6344f5ef5c3dac3aee57a39b5b46dff, 4dbd8808a591b49b717862e6e0081bcf14a87788 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: pid: take a reference when initializing `cad_pid` During boot, kernel_init_freeable() initializes `cad_pid` to the init task's struct pid. Later on, we may change `cad_pid` via a sysctl, and when this happens proc_do_cad_pid() will increment the refcount on the new pid via get_pid(), and will decrement the refcount on the old pid via put_pid(). As we never called get_pid() when we initialized `cad_pid`, we decrement a reference we never incremented, can therefore free the init task's struct pid early. As there can be dangling references to the struct pid, we can later encounter a use-after-free (e.g. when delivering signals). This was spotted when fuzzing v5.13-rc3 with Syzkaller, but seems to have been around since the conversion of `cad_pid` to struct pid in commit 9ec52099e4b8 ("[PATCH] replace cad_pid by a struct pid") from the pre-KASAN stone age of v2.6.19. Fix this by getting a reference to the init task's struct pid when we assign it to `cad_pid`. Full KASAN splat below. ================================================================== BUG: KASAN: use-after-free in ns_of_pid include/linux/pid.h:153 [inline] BUG: KASAN: use-after-free in task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 Read of size 4 at addr ffff23794dda0004 by task syz-executor.0/273 CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1 Hardware name: linux,dummy-virt (DT) Call trace: ns_of_pid include/linux/pid.h:153 [inline] task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 do_notify_parent+0x308/0xe60 kernel/signal.c:1950 exit_notify kernel/exit.c:682 [inline] do_exit+0x2334/0x2bd0 kernel/exit.c:845 do_group_exit+0x108/0x2c8 kernel/exit.c:922 get_signal+0x4e4/0x2a88 kernel/signal.c:2781 do_signal arch/arm64/kernel/signal.c:882 [inline] do_notify_resume+0x300/0x970 arch/arm64/kernel/signal.c:936 work_pending+0xc/0x2dc Allocated by task 0: slab_post_alloc_hook+0x50/0x5c0 mm/slab.h:516 slab_alloc_node mm/slub.c:2907 [inline] slab_alloc mm/slub.c:2915 [inline] kmem_cache_alloc+0x1f4/0x4c0 mm/slub.c:2920 alloc_pid+0xdc/0xc00 kernel/pid.c:180 copy_process+0x2794/0x5e18 kernel/fork.c:2129 kernel_clone+0x194/0x13c8 kernel/fork.c:2500 kernel_thread+0xd4/0x110 kernel/fork.c:2552 rest_init+0x44/0x4a0 init/main.c:687 arch_call_rest_init+0x1c/0x28 start_kernel+0x520/0x554 init/main.c:1064 0x0 Freed by task 270: slab_free_hook mm/slub.c:1562 [inline] slab_free_freelist_hook+0x98/0x260 mm/slub.c:1600 slab_free mm/slub.c:3161 [inline] kmem_cache_free+0x224/0x8e0 mm/slub.c:3177 put_pid.part.4+0xe0/0x1a8 kernel/pid.c:114 put_pid+0x30/0x48 kernel/pid.c:109 proc_do_cad_pid+0x190/0x1b0 kernel/sysctl.c:1401 proc_sys_call_handler+0x338/0x4b0 fs/proc/proc_sysctl.c:591 proc_sys_write+0x34/0x48 fs/proc/proc_sysctl.c:617 call_write_iter include/linux/fs.h:1977 [inline] new_sync_write+0x3ac/0x510 fs/read_write.c:518 vfs_write fs/read_write.c:605 [inline] vfs_write+0x9c4/0x1018 fs/read_write.c:585 ksys_write+0x124/0x240 fs/read_write.c:658 __do_sys_write fs/read_write.c:670 [inline] __se_sys_write fs/read_write.c:667 [inline] __arm64_sys_write+0x78/0xb0 fs/read_write.c:667 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall arch/arm64/kernel/syscall.c:49 [inline] el0_svc_common.constprop.1+0x16c/0x388 arch/arm64/kernel/syscall.c:129 do_el0_svc+0xf8/0x150 arch/arm64/kernel/syscall.c:168 el0_svc+0x28/0x38 arch/arm64/kernel/entry-common.c:416 el0_sync_handler+0x134/0x180 arch/arm64/kernel/entry-common.c:432 el0_sync+0x154/0x180 arch/arm64/kernel/entry.S:701 The buggy address belongs to the object at ffff23794dda0000 which belongs to the cache pid of size 224 The buggy address is located 4 bytes inside of 224-byte region [ff ---truncated---

Published
Mar 15, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 15th 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-47118

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

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

    • 2.6.19affected
    • 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 and later · before 764c2e892d1fe895392aff62fb353fdce43bb529affected · git
    • 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 and later · before f86c80515a8a3703e0ca2e56deb50fc2879c5ea4affected · git
    • 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 and later · before 4dbd8808a591b49b717862e6e0081bcf14a87788affected · git
    • 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 and later · before d106f05432e60f9f62d456ef017687f5c73cb414affected · git
    • 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 and later · before 2cd6eedfa6344f5ef5c3dac3aee57a39b5b46dffaffected · git
    • 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 and later · before 7178be006d495ffb741c329012da289b62dddfe6affected · git
    • 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 and later · before b8ff869f20152fbe66b6c2e2715d26a2f9897ccaaffected · git
    • 9ec52099e4b8678a60e9f93e41ad87885d64f3e6 and later · before 0711f0d7050b9e07c44bc159bbc64ac0a1022c7faffected · git
    • before 2.6.19not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.5.1.el8_104.18.0-553.5.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.5.1.rt7.346.el8_104.18.0-553.5.1.rt7.346.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.5.1.rt7.346.el8_104.18.0-553.5.1.rt7.346.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.5.1.rt7.346.el8_104.18.0-553.5.1.rt7.346.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.5.1.rt7.346.el8_104.18.0-553.5.1.rt7.346.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.5.1.rt7.346.el8_104.18.0-553.5.1.rt7.346.el8_10
AlmaLinux:8kernel-rt-debug-kvmbefore 4.18.0-553.5.1.rt7.346.el8_104.18.0-553.5.1.rt7.346.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.5.1.rt7.346.el8_104.18.0-553.5.1.rt7.346.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.5.1.rt7.346.el8_104.18.0-553.5.1.rt7.346.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.5.1.rt7.346.el8_104.18.0-553.5.1.rt7.346.el8_10

+65

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-47116Mar 15, 2024 · ext4: fix memory leak in ext4_mb_init_backend on error path.
    22Monitor
  • ← EarlierCVE-2021-47117Mar 15, 2024 · ext4: fix bug on in ext4_es_cache_extent as ext4_split_extent_at failed
    22Monitor
  • Later →CVE-2021-47119Mar 15, 2024 · ext4: fix memory leak in ext4_fill_super
    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 Linux0711f0d7050b9e07c44bc159bbc64ac0a1022c7fVendor (CNA)
Linux Linux2cd6eedfa6344f5ef5c3dac3aee57a39b5b46dffVendor (CNA)
Linux Linux4dbd8808a591b49b717862e6e0081bcf14a87788Vendor (CNA)
Linux Linux7178be006d495ffb741c329012da289b62dddfe6Vendor (CNA)
Linux Linux764c2e892d1fe895392aff62fb353fdce43bb529Vendor (CNA)
Linux Linuxb8ff869f20152fbe66b6c2e2715d26a2f9897ccaVendor (CNA)
Linux Linuxd106f05432e60f9f62d456ef017687f5c73cb414Vendor (CNA)
Linux Linuxf86c80515a8a3703e0ca2e56deb50fc2879c5ea4Vendor (CNA)
almalinux:bpftool4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.5.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux5.10.46-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.5.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.5.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.5.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.5.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.5.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.5.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.5.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.5.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-553.5.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+5

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.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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.

References

All records