CVE-2021-22600

CRITICALNVD 6.69.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-04-11), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 6.6 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at every mission impact level
CISA-KEV: ExploitedEPSS PROB: 6.6%CVSS: 6.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
6.6
EG Score
9.0CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
6.6%
EPSS %ILE
93rd
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
6.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 14 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 14 days if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2021-22600

Published

January 26, 2022

Last Modified

October 24, 2025

Advisory Details (5)

Auto-updated Oct 20, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-22600
Web pageMentions a patch (unverified)

[SECURITY] [DSA 5096-1] linux security update

https://www.debian.org/security/2022/dsa-5096
Web pageMentions a patch (unverified)

[SECURITY] [DLA 2941-1] linux-4.19 security update

https://lists.debian.org/debian-lts-announce/2022/03/msg00012.html
Web page

net/packet: rx_owner_map depends on pg_vec - kernel/git/torvalds/linux.git - Linux kernel source tree

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=ec6af094ea28f0f2dda1a6a33b14cd57e36a9755

Vendor Advisories for CVE-2021-22600(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
linux4.19.118-1 ... 4.19.98-1~bpo9+1 (36 versions)
  • every version up to 4.19.232-1: fixed in 4.19.232-1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.46-4 ... 5.10.92-1~bpo10+1 (6 versions)
  • every version up to 5.10.92-1: fixed in 5.10.92-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
linux-4.194.19.132-1~deb9u1 ... 4.19.208-1~deb9u1 (10 versions)
  • every version up to 4.19.232-1~deb9u1: fixed in 4.19.232-1~deb9u1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(7)

Data Freshness Timeline

(refreshed 25× in last 7d / 301× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,884 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,784 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:28 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  2. 2026-10-23 04:18 UTCEG score recompute
  3. 2026-10-23 04:18 UTCVendor advisory
  4. 2026-10-23 04:18 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-22 16:29 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  6. 2026-10-22 02:21 UTCEG score recompute
  7. 2026-10-22 02:21 UTCVendor advisory
  8. 2026-10-22 02:21 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-21 16:28 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  10. 2026-10-21 00:26 UTCEG score recompute
  11. 2026-10-21 00:26 UTCVendor advisory
  12. 2026-10-21 00:26 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-10-20 16:28 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  14. 2026-10-19 22:28 UTCEG score recompute
  15. 2026-10-19 22:28 UTCVendor advisory
  16. 2026-10-19 22:28 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-10-19 16:28 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  18. 2026-10-18 20:32 UTCEG score recompute
  19. 2026-10-18 20:32 UTCVendor advisory
  20. 2026-10-18 20:32 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-18 09:10 UTCEG score recompute
  22. 2026-10-17 18:36 UTCEG score recompute
  23. 2026-10-17 18:36 UTCVendor advisory
  24. 2026-10-17 18:35 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-17 16:28 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
Show 75 more
  1. 2026-10-16 16:39 UTCEG score recompute
  2. 2026-10-16 16:39 UTCVendor advisory
  3. 2026-10-16 16:38 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-10-16 16:33 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  5. 2026-10-15 16:28 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  6. 2026-10-15 14:40 UTCEG score recompute
  7. 2026-10-15 14:40 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-14 16:28 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  9. 2026-10-14 12:42 UTCEG score recompute
  10. 2026-10-14 12:42 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-13 16:28 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  12. 2026-10-13 10:45 UTCVendor advisory
  13. 2026-10-13 10:45 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-10-12 19:24 UTCEG score recompute
  15. 2026-10-12 16:29 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  16. 2026-10-12 08:49 UTCVendor advisory
  17. 2026-10-12 08:49 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-10-12 04:43 UTCVendor advisory
  19. 2026-10-12 04:42 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-12 00:37 UTCVendor advisory
  21. 2026-10-12 00:36 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-11 20:27 UTCEG score recompute
  23. 2026-10-11 20:27 UTCVendor advisory
  24. 2026-10-11 20:27 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-11 16:23 UTCEG score recompute
  26. 2026-10-11 16:23 UTCVendor advisory
  27. 2026-10-11 16:22 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-10-11 13:43 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  29. 2026-10-11 12:16 UTCEG score recompute
  30. 2026-10-11 12:16 UTCVendor advisory
  31. 2026-10-11 12:16 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  32. 2026-10-11 08:11 UTCVendor advisory
  33. 2026-10-11 08:11 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  34. 2026-10-11 04:06 UTCVendor advisory
  35. 2026-10-11 04:06 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  36. 2026-10-11 00:00 UTCEG score recompute
  37. 2026-10-11 00:00 UTCVendor advisory
  38. 2026-10-11 00:00 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  39. 2026-10-10 19:56 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  40. 2026-10-10 19:55 UTCVendor advisory
  41. 2026-10-10 19:55 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  42. 2026-10-10 15:50 UTCVendor advisory
  43. 2026-10-10 15:50 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-10-10 11:45 UTCVendor advisory
  45. 2026-10-10 11:45 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  46. 2026-10-10 07:40 UTCVendor advisory
  47. 2026-10-10 07:40 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-10-10 03:35 UTCVendor advisory
  49. 2026-10-10 03:35 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-10-09 23:30 UTCEG score recompute
  51. 2026-10-09 23:30 UTCVendor advisory
  52. 2026-10-09 23:30 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  53. 2026-10-09 20:04 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  54. 2026-10-09 19:25 UTCVendor advisory
  55. 2026-10-09 19:24 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  56. 2026-10-09 15:20 UTCVendor advisory
  57. 2026-10-09 15:20 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  58. 2026-10-09 11:14 UTCVendor advisory
  59. 2026-10-09 11:14 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-10-09 07:09 UTCVendor advisory
  61. 2026-10-09 07:08 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-10-09 03:03 UTCVendor advisory
  63. 2026-10-09 03:03 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-10-08 22:59 UTCVendor advisory
  65. 2026-10-08 22:58 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  66. 2026-10-08 18:53 UTCEG score recompute
  67. 2026-10-08 18:53 UTCVendor advisory
  68. 2026-10-08 18:53 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  69. 2026-10-08 16:39 UTCEPSS rescoreEPSS 6.6% · 93rd percentile
  70. 2026-10-08 14:47 UTCVendor advisory
  71. 2026-10-08 14:47 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-10-08 10:38 UTCVendor advisory
  73. 2026-10-08 10:37 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8
  74. 2026-10-08 06:31 UTCVendor advisory
  75. 2026-10-08 06:30 UTCGHSA enrichmentGHSA-6rrc-7vqp-364c · GitHub severity HIGH · GitHub CVSS 7.8

Frequently asked(6)

What is CVE-2021-22600?
CVE-2021-22600 is a critical-severity vulnerability; its CVE record was published on January 26, 2022. A double free bug in packetsetring() 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
When was the CVE record for CVE-2021-22600 published?
The CVE record for CVE-2021-22600 was published on January 26, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2025; the record at its source may have been updated since.
Is CVE-2021-22600 actively exploited?
Yes. CISA added CVE-2021-22600 to the Known Exploited Vulnerabilities catalog on April 11, 2022, affecting Linux Kernel. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2021-22600?
CVE-2021-22600 has a CVSS v3 base score of 6.6 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2021-22600?
CVE-2021-22600 affects Linux Kernel. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2021-22600?
A fix for CVE-2021-22600 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-22600 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-22600

Explore →

Is Your Infrastructure Affected by CVE-2021-22600?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.