CVE-2022-50280

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2025-09-15. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2022-55575 (ENISA EUVD) · GHSA-3pxv-j5r5-v5qh (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

pnode: terminate at peers of source

The propagate_mnt() function handles mount propagation when creating mounts and propagates the source mount tree @source_mnt to all applicable nodes of the destination propagation mount tree headed by @dest_mnt.

Unfortunately it contains a bug where it fails to terminate at peers of @source_mnt when looking up copies of the source mount that become masters for copies of the source mount tree mounted on top of slaves in the destination propagation tree causing a NULL dereference.

Once the mechanics of the bug are understood it's easy to trigger. Because of unprivileged user namespaces it is available to unprivileged users.

While fixing this bug we've gotten confused multiple times due to unclear terminology or missing concepts. So let's start this with some clarifications:

* The terms "master" or "peer" denote a shared mount. A shared mount belongs to a peer group.

* A peer group is a set of shared mounts that propagate to each other. They are identified by a peer group id. The peer group id is available in @shared_mnt->mnt_group_id. Shared mounts within the same peer group have the same peer group id. The peers in a peer group can be reached via @shared_mnt->mnt_share.

* The terms "slave mount" or "dependent mount" denote a mount that receives propagation from a peer in a peer group. IOW, shared mounts may have slave mounts and slave mounts have shared mounts as their master. Slave mounts of a given peer in a peer group are listed on that peers slave list available at @shared_mnt->mnt_slave_list.

* The term "master mount" denotes a mount in a peer group. IOW, it denotes a shared mount or a peer mount in a peer group. The term "master mount" - or "master" for short - is mostly used when talking in the context of slave mounts that receive propagation from a master mount. A master mount of a slave identifies the closest peer group a slave mount receives propagation from. The master mount of a slave can be identified via @slave_mount->mnt_master. Different slaves may point to different masters in the same peer group.

* Multiple peers in a peer group can have non-empty ->mnt_slave_lists. Non-empty ->mnt_slave_lists of peers don't intersect. Consequently, to ensure all slave mounts of a peer group are visited the ->mnt_slave_lists of all peers in a peer group have to be walked.

* Slave mounts point to a peer in the closest peer group they receive propagation from via @slave_mnt->mnt_master (see above). Together with these peers they form a propagation group (see below). The closest peer group can thus be identified through the peer group id @slave_mnt->mnt_master->mnt_group_id of the peer/master that a slave mount receives propagation from.

* A shared-slave mount is a slave mount to a peer group pg1 while also a peer in another peer group pg2. IOW, a peer group may receive propagation from another peer group.

If a peer group pg1 is a slave to another peer group pg2 then all peers in peer group pg1 point to the same peer in peer group pg2 via ->mnt_master. IOW, all peers in peer group pg1 appear on the same ->mnt_slave_list. IOW, they cannot be slaves to different peer groups.

* A pure slave mount is a slave mount that is a slave to a peer group but is not a peer in another peer group.

* A propagation group denotes the set of mounts consisting of a single peer group pg1 and all slave mounts and shared-slave mounts that point to a peer in that peer group via ->mnt_master. IOW, all slave mounts such that @slave_mnt->mnt_master->mnt_group_id is equal to @shared_mnt->mnt_group_id.

The concept of a propagation group makes it easier to talk about a single propagation level in a propagation tree.

For example, in propagate_mnt() the immediate peers of @dest_mnt and all slaves of @dest_mnt's peer group form a propagation group pr ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

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

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

Published

September 15, 2025

Last Modified

December 4, 2025

References (9)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.9.337 (fixes >=3.15.0)—osv

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (25 versions)
  • every version up to 5.10.178-1: fixed in 5.10.178-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.1.4-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.1.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.4-1: fixed in 6.1.4-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 34× 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 96 of 184 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 88 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-25 17:54 UTCEG score recompute
  10. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-24 17:43 UTCEG score recompute
  12. 2026-10-24 17:43 UTCGHSA enrichmentGHSA-3pxv-j5r5-v5qh · GitHub CVSS 5.5
  13. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-10-18 08:19 UTCEG score recompute
  21. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-10-12 18:41 UTCEG score recompute
  25. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 71 more
  1. 2026-10-11 22:04 UTCEG score recompute
  2. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-02 05:10 UTCOSV refresh
  12. 2026-09-30 16:13 UTCEG score recompute
  13. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-13 00:36 UTCOSV refresh
  25. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  26. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  27. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  28. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  29. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  34. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  35. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  37. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  38. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  39. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  40. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-08-25 03:56 UTCOSV refresh
  42. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  43. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  44. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  46. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  49. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  50. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  51. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  52. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  53. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  54. 2026-08-08 21:25 UTCOSV refresh
  55. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  56. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  57. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  58. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  59. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  60. 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  61. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  62. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  63. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  64. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  65. 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  66. 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  67. 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  68. 2026-07-23 20:11 UTCOSV refresh
  69. 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  70. 2026-07-23 02:17 UTCEG score recompute
  71. 2026-07-22 23:04 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-50280?
CVE-2022-50280 is a medium-severity vulnerability; its CVE record was published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: pnode: terminate at peers of source The propagate_mnt() function handles mount propagation when creating mounts and propagates the source mount tree @source_mnt to all applicable nodes of the destination propagation mount tree…
When was the CVE record for CVE-2022-50280 published?
The CVE record for CVE-2022-50280 was published on September 15, 2025. 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 December 4, 2025; the record at its source may have been updated since.
Is CVE-2022-50280 actively exploited?
CVE-2022-50280 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50280?
CVE-2022-50280 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50280?
A fix for CVE-2022-50280 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-50280

Explore →

Is Your Infrastructure Affected by CVE-2022-50280?

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

Book a Demo →Browse All CVEs