CVE-2022-49979

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%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: fix refcount bug in sk_psock_get (2)

Syzkaller reports refcount bug as follows: ------------[ cut here ]------------ refcount_t: saturated; leaking memory. WARNING: CPU: 1 PID: 3605 at lib/refcount.c:19 refcount_warn_saturate+0xf4/0x1e0 lib/refcount.c:19 Modules linked in: CPU: 1 PID: 3605 Comm: syz-executor208 Not tainted 5.18.0-syzkaller-03023-g7e062cda7d90 #0 __refcount_add_not_zero include/linux/refcount.h:163 [inline] __refcount_inc_not_zero include/linux/refcount.h:227 [inline] refcount_inc_not_zero include/linux/refcount.h:245 [inline] sk_psock_get+0x3bc/0x410 include/linux/skmsg.h:439 tls_data_ready+0x6d/0x1b0 net/tls/tls_sw.c:2091 tcp_data_ready+0x106/0x520 net/ipv4/tcp_input.c:4983 tcp_data_queue+0x25f2/0x4c90 net/ipv4/tcp_input.c:5057 tcp_rcv_state_process+0x1774/0x4e80 net/ipv4/tcp_input.c:6659 tcp_v4_do_rcv+0x339/0x980 net/ipv4/tcp_ipv4.c:1682 sk_backlog_rcv include/net/sock.h:1061 [inline] __release_sock+0x134/0x3b0 net/core/sock.c:2849 release_sock+0x54/0x1b0 net/core/sock.c:3404 inet_shutdown+0x1e0/0x430 net/ipv4/af_inet.c:909 __sys_shutdown_sock net/socket.c:2331 [inline] __sys_shutdown_sock net/socket.c:2325 [inline] __sys_shutdown+0xf1/0x1b0 net/socket.c:2343 __do_sys_shutdown net/socket.c:2351 [inline] __se_sys_shutdown net/socket.c:2349 [inline] __x64_sys_shutdown+0x50/0x70 net/socket.c:2349 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x46/0xb0

During SMC fallback process in connect syscall, kernel will replaces TCP with SMC. In order to forward wakeup smc socket waitqueue after fallback, kernel will sets clcsk->sk_user_data to origin smc socket in smc_fback_replace_callbacks().

Later, in shutdown syscall, kernel will calls sk_psock_get(), which treats the clcsk->sk_user_data as psock type, triggering the refcnt warning.

So, the root cause is that smc and psock, both will use sk_user_data field. So they will mismatch this field easily.

This patch solves it by using another bit(defined as SK_USER_DATA_PSOCK) in PTRMASK, to mark whether sk_user_data points to a psock object or not. This patch depends on a PTRMASK introduced in commit f1ff5ce2cd5e ("net, sk_msg: Clear sk_user_data pointer on clone if tagged").

For there will possibly be more flags in the sk_user_data field, this patch also refactor sk_user_data flags code to be more generic to improve its maintainability.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
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
0.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or 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 none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 18, 2025

Last Modified

August 5, 2026

References (3)

Vendor Advisories for CVE-2022-49979(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat
linuxKernel @ 5.15.65 (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

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

Data Freshness Timeline

(refreshed 7× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 171 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-49979?
CVE-2022-49979 is a medium vulnerability published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: net: fix refcount bug in skpsockget (2) Syzkaller reports refcount bug as follows: ------------[ cut here ]------------ refcount_t: saturated; leaking memory. WARNING: CPU: 1 PID: 3605 at lib/refcount.c:19…
When was CVE-2022-49979 disclosed?
CVE-2022-49979 was first published on June 18, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49979 actively exploited?
CVE-2022-49979 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49979?
CVE-2022-49979 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49979?
A fix for CVE-2022-49979 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49979 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-2022-49979

Explore →

Is Your Infrastructure Affected by CVE-2022-49979?

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

Book a Demo →Browse All CVEs