Kernel use-after-free via unreferenced cad_pid initialization
Published Mar 15, 2024 · Updated May 11, 2026
Use-after-free in Linux from 2.6.19 allows local users to access freed kernel memory through a write to the cad_pid sysctl. kernel_init_freeable assigns the init task's PID object to cad_pid without calling get_pid, so proc_do_cad_pid later calls put_pid on an unheld reference. Reaching the flaw requires local permission to modify the sysctl; later signal delivery can dereference the freed PID object and crash the kernel.
Summary
What happened
Use-after-free in Linux from 2.6.19 allows local users to access freed kernel memory through a write to the cad_pid sysctl. kernel_init_freeable assigns the init task's PID object to cad_pid without calling get_pid, so proc_do_cad_pid later calls put_pid on an unheld reference. Reaching the flaw requires local permission to modify the sysctl; later signal delivery can dereference the freed PID object and crash the kernel.
The record
- CVE
- CVE-2021-47118
- Published
- Mar 15, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 15, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.19
- Affected versionversion=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <0711f0d7050b9e07c44bc159bbc64ac0a1022c7f
- Affected versionversion=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <2cd6eedfa6344f5ef5c3dac3aee57a39b5b46dff
- Affected versionversion=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <4dbd8808a591b49b717862e6e0081bcf14a87788
- Affected versionversion=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <7178be006d495ffb741c329012da289b62dddfe6
- Affected versionversion=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <764c2e892d1fe895392aff62fb353fdce43bb529
- Affected versionversion=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <b8ff869f20152fbe66b6c2e2715d26a2f9897cca
- Affected versionversion=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <d106f05432e60f9f62d456ef017687f5c73cb414
- Affected versionversion=9ec52099e4b8678a60e9f93e41ad87885d64f3e6 <f86c80515a8a3703e0ca2e56deb50fc2879c5ea4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo