CVE-2022-50323

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 (severity: MODERATE) 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
Trending — 3 sources updated this week

Also known asEUVD-2022-55532 (ENISA EUVD) · GHSA-3cwp-rh3m-h6g8 (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:

net: do not sense pfmemalloc status in skb_append_pagefrags()

skb_append_pagefrags() is used by af_unix and udp sendpage() implementation so far.

In commit 326140063946 ("tcp: TX zerocopy should not sense pfmemalloc status") we explained why we should not sense pfmemalloc status for pages owned by user space.

We should also use skb_fill_page_desc_noacc() in skb_append_pagefrags() to avoid following KCSAN report:

BUG: KCSAN: data-race in lru_add_fn / skb_append_pagefrags

write to 0xffffea00058fc1c8 of 8 bytes by task 17319 on cpu 0: __list_add include/linux/list.h:73 [inline] list_add include/linux/list.h:88 [inline] lruvec_add_folio include/linux/mm_inline.h:323 [inline] lru_add_fn+0x327/0x410 mm/swap.c:228 folio_batch_move_lru+0x1e1/0x2a0 mm/swap.c:246 lru_add_drain_cpu+0x73/0x250 mm/swap.c:669 lru_add_drain+0x21/0x60 mm/swap.c:773 free_pages_and_swap_cache+0x16/0x70 mm/swap_state.c:311 tlb_batch_pages_flush mm/mmu_gather.c:59 [inline] tlb_flush_mmu_free mm/mmu_gather.c:256 [inline] tlb_flush_mmu+0x5b2/0x640 mm/mmu_gather.c:263 tlb_finish_mmu+0x86/0x100 mm/mmu_gather.c:363 exit_mmap+0x190/0x4d0 mm/mmap.c:3098 __mmput+0x27/0x1b0 kernel/fork.c:1185 mmput+0x3d/0x50 kernel/fork.c:1207 copy_process+0x19fc/0x2100 kernel/fork.c:2518 kernel_clone+0x166/0x550 kernel/fork.c:2671 __do_sys_clone kernel/fork.c:2812 [inline] __se_sys_clone kernel/fork.c:2796 [inline] __x64_sys_clone+0xc3/0xf0 kernel/fork.c:2796 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd

read to 0xffffea00058fc1c8 of 8 bytes by task 17325 on cpu 1: page_is_pfmemalloc include/linux/mm.h:1817 [inline] __skb_fill_page_desc include/linux/skbuff.h:2432 [inline] skb_fill_page_desc include/linux/skbuff.h:2453 [inline] skb_append_pagefrags+0x210/0x600 net/core/skbuff.c:3974 unix_stream_sendpage+0x45e/0x990 net/unix/af_unix.c:2338 kernel_sendpage+0x184/0x300 net/socket.c:3561 sock_sendpage+0x5a/0x70 net/socket.c:1054 pipe_to_sendpage+0x128/0x160 fs/splice.c:361 splice_from_pipe_feed fs/splice.c:415 [inline] __splice_from_pipe+0x222/0x4d0 fs/splice.c:559 splice_from_pipe fs/splice.c:594 [inline] generic_splice_sendpage+0x89/0xc0 fs/splice.c:743 do_splice_from fs/splice.c:764 [inline] direct_splice_actor+0x80/0xa0 fs/splice.c:931 splice_direct_to_actor+0x305/0x620 fs/splice.c:886 do_splice_direct+0xfb/0x180 fs/splice.c:974 do_sendfile+0x3bf/0x910 fs/read_write.c:1255 __do_sys_sendfile64 fs/read_write.c:1323 [inline] __se_sys_sendfile64 fs/read_write.c:1309 [inline] __x64_sys_sendfile64+0x10c/0x150 fs/read_write.c:1309 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd

value changed: 0x0000000000000000 -> 0xffffea00058fc188

Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 17325 Comm: syz-executor.0 Not tainted 6.1.0-rc1-syzkaller-00158-g440b7895c990-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022

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 SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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.
EPSS PROB
0.2%
EPSS %ILE
4th
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-11-05). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (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)60 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 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

Published

September 15, 2025

Last Modified

November 5, 2026

References (3)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.15.77 (fixes >=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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.7-1: fixed in 6.0.7-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.7-1: fixed in 6.0.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.7-1: fixed in 6.0.7-1
—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2022-50323?
CVE-2022-50323 is a medium-severity vulnerability; its CVE record was published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: net: do not sense pfmemalloc status in skb_append_pagefrags() skb_append_pagefrags() is used by af_unix and udp sendpage() implementation so far. In commit 326140063946 ("tcp: TX zerocopy should not sense pfmemalloc status") we…
When was the CVE record for CVE-2022-50323 published?
The CVE record for CVE-2022-50323 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 November 5, 2026; the record at its source may have been updated since.
Is CVE-2022-50323 actively exploited?
CVE-2022-50323 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50323?
CVE-2022-50323 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50323?
A fix for CVE-2022-50323 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-50323

Explore →

Is Your Infrastructure Affected by CVE-2022-50323?

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

Book a Demo →Browse All CVEs