CVE-2021-22600 — Linux Kernel Privilege Escalation Vulnerability
A double free bug in packet_set_ring() in net/packet/af_packet.c can be exploited by a local user through crafted syscalls to escalate privileges or deny service. We recommend upgrading kernel past the effected versions or rebuilding past ec6af094ea28f0f2dda1a6a33b14cd57e36a9755
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (github)+6
- EPSS 6.6% (30-day exploitation probability)+14
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
CISA required action CISA
Apply updates per vendor instructions.
US federal deadline: May 2, 2022 — passed 1627 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Linux Linux Kernel, Linux Kernel Kernel…).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 94% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 10.0version 9.0 | Vulnerable | NIST National Vulnerability Database |
| Linux | Linux Kernel | ≥ 4.14.175 and < 4.14.259≥ 4.19.114 and < 4.19.222≥ 5.4.29 and < 5.4.168≥ 5.5.14 and < 5.10.88≥ 5.11 and < 5.15.11 | Vulnerable | NIST National Vulnerability Database |
| Linux Kernel | Kernel | < 5.16-rc6< 5.15.11< 5.10.88< 5.4.168 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Netapp | 8300 Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | 8700 Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | A400 Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | C400 Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H300s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H410c Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H410s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H500s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H700s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.0 | CVSS 3.1 | High | 1.0 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 6.6 | CVSS 3.1 | Medium | 0.8 | 5.3 | cve-coordination@google.com via NIST National Vulnerability Database |
| 6.6 | CVSS 3.1 | Medium | — | — | Google via CVE Program (cve.org) e CISA ADP |
| 7.2 | CVSS 2.0 | High | 3.9 | 10.0 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 6.59%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
- Hunt retroactively in logs from before Apr 11, 2022 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux kernel/kernel
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · netapp/8300 firmware, netapp/8700 firmware, netapp/a400 firmware, netapp/c400 firmware, linux/linux kernel, debian/debia
- CVSS changed · 7.0
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2022
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- security.netapp.com/advisory/ntap-20230110-0002/
- github.com/advisories/GHSA-6rrc-7vqp-364c
- nvd.nist.gov/vuln/detail/CVE-2021-22600
- lists.debian.org/debian-lts-announce/2022/03/msg00012.html
- www.debian.org/security/2022/dsa-5096
- security.netapp.com/advisory/ntap-20230110-0002
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-98164 KVM: x86/mmu: Check write tracking in all address spaces 16d
- High CVE-2026-98163 cgroup: Avoid iteration of dying tasks with zero refcount 19d
- Medium CVE-2026-98162 smb/server: fix tree connection leak in smb2_tree_connect() 20d
- High CVE-2026-98156 drm/virtio: use the DMA API for resource backing on Xen 20d
- Medium CVE-2026-98159 wifi: mt76: mt7921: validate CLC firmware records 20d
- Medium CVE-2026-98137 ntfs: treat any nonzero dio zero-range return as an error 20d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2021-22600 is "Linux Kernel Privilege Escalation Vulnerability", rated High. It affects Debian Linux (Debian); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.0 describes technical severity. EPSS 6.59% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.