CVE-2022-48781

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 2024-07-16. 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-53660 (ENISA EUVD) · GHSA-9v24-vr9v-j466 (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:

crypto: af_alg - get rid of alg_memory_allocated

alg_memory_allocated does not seem to be really used.

alg_proto does have a .memory_allocated field, but no corresponding .sysctl_mem.

This means sk_has_account() returns true, but all sk_prot_mem_limits() users will trigger a NULL dereference [1].

THis was not a problem until SO_RESERVE_MEM addition.

general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] CPU: 1 PID: 3591 Comm: syz-executor153 Not tainted 5.17.0-rc3-syzkaller-00316-gb81b1829e7e3 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:sk_prot_mem_limits include/net/sock.h:1523 [inline] RIP: 0010:sock_reserve_memory+0x1d7/0x330 net/core/sock.c:1000 Code: 08 00 74 08 48 89 ef e8 27 20 bb f9 4c 03 7c 24 10 48 8b 6d 00 48 83 c5 08 48 89 e8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 48 89 ef e8 fb 1f bb f9 48 8b 6d 00 4c 89 ff 48 RSP: 0018:ffffc90001f1fb68 EFLAGS: 00010202 RAX: 0000000000000001 RBX: ffff88814aabc000 RCX: dffffc0000000000 RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffffff90e18120 RBP: 0000000000000008 R08: dffffc0000000000 R09: fffffbfff21c3025 R10: fffffbfff21c3025 R11: 0000000000000000 R12: ffffffff8d109840 R13: 0000000000001002 R14: 0000000000000001 R15: 0000000000000001 FS: 0000555556e08300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fc74416f130 CR3: 0000000073d9e000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: sock_setsockopt+0x14a9/0x3a30 net/core/sock.c:1446 __sys_setsockopt+0x5af/0x980 net/socket.c:2176 __do_sys_setsockopt net/socket.c:2191 [inline] __se_sys_setsockopt net/socket.c:2188 [inline] __x64_sys_setsockopt+0xb1/0xc0 net/socket.c:2188 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7fc7440fddc9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffe98f07968 EFLAGS: 00000246 ORIG_RAX: 0000000000000036 RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fc7440fddc9 RDX: 0000000000000049 RSI: 0000000000000001 RDI: 0000000000000004 RBP: 0000000000000000 R08: 0000000000000004 R09: 00007ffe98f07990 R10: 0000000020000000 R11: 0000000000000246 R12: 00007ffe98f0798c R13: 00007ffe98f079a0 R14: 00007ffe98f079e0 R15: 0000000000000000 Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:sk_prot_mem_limits include/net/sock.h:1523 [inline] RIP: 0010:sock_reserve_memory+0x1d7/0x330 net/core/sock.c:1000 Code: 08 00 74 08 48 89 ef e8 27 20 bb f9 4c 03 7c 24 10 48 8b 6d 00 48 83 c5 08 48 89 e8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 48 89 ef e8 fb 1f bb f9 48 8b 6d 00 4c 89 ff 48 RSP: 0018:ffffc90001f1fb68 EFLAGS: 00010202 RAX: 0000000000000001 RBX: ffff88814aabc000 RCX: dffffc0000000000 RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffffff90e18120 RBP: 0000000000000008 R08: dffffc0000000000 R09: fffffbfff21c3025 R10: fffffbfff21c3025 R11: 0000000000000000 R12: ffffffff8d109840 R13: 0000000000001002 R14: 0000000000000001 R15: 0000000000000001 FS: 0000555556e08300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fc74416f130 CR3: 0000000073d9e000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

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
9th
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 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

July 16, 2024

Last Modified

November 21, 2024

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.16.11 (fixes >=5.16.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 5.16.11-1: fixed in 5.16.11-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.16.11-1: fixed in 5.16.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.16.11-1: fixed in 5.16.11-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-48781?
CVE-2022-48781 is a medium-severity vulnerability; its CVE record was published on July 16, 2024. In the Linux kernel, the following vulnerability has been resolved: crypto: af_alg - get rid of alg_memory_allocated alg_memory_allocated does not seem to be really used. alg_proto does have a .memory_allocated field, but no corresponding .sysctl_mem. This means sk_has_account() returns true, but…
When was the CVE record for CVE-2022-48781 published?
The CVE record for CVE-2022-48781 was published on July 16, 2024. 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 21, 2024; the record at its source may have been updated since.
Is CVE-2022-48781 actively exploited?
CVE-2022-48781 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-48781?
CVE-2022-48781 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-48781?
A fix for CVE-2022-48781 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-48781

Explore →

Is Your Infrastructure Affected by CVE-2022-48781?

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

Book a Demo →Browse All CVEs