CVE-2026-22977

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 2026-01-21. 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-2026-3682 (ENISA EUVD) · GHSA-rgj2-xq4c-hrvm (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: sock: fix hardened usercopy panic in sock_recv_errqueue

skbuff_fclone_cache was created without defining a usercopy region, [1] unlike skbuff_head_cache which properly whitelists the cb[] field. [2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is enabled and the kernel attempts to copy sk_buff.cb data to userspace via sock_recv_errqueue() -> put_cmsg().

The crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone() (from skbuff_fclone_cache) [1]

  • The skb is cloned via skb_clone() using the pre-allocated fclone
[3] 3. The cloned skb is queued to sk_error_queue for timestamp reporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE)
  • sock_recv_errqueue() calls put_cmsg() to copy serr->ee from skb->cb
[4] 6. __check_heap_object() fails because skbuff_fclone_cache has no usercopy whitelist [5]

When cloned skbs allocated from skbuff_fclone_cache are used in the socket error queue, accessing the sock_exterr_skb structure in skb->cb via put_cmsg() triggers a usercopy hardening violation:

[ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object 'skbuff_fclone_cache' (offset 296, size 16)! [ 5.382796] kernel BUG at mm/usercopy.c:102! [ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI [ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7 [ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80 [ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff <0f> 0b 490 [ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246 [ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74 [ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0 [ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74 [ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001 [ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00 [ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000 [ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0 [ 5.384903] PKRU: 55555554 [ 5.384903] Call Trace: [ 5.384903] [ 5.384903] __check_heap_object+0x9a/0xd0 [ 5.384903] __check_object_size+0x46c/0x690 [ 5.384903] put_cmsg+0x129/0x5e0 [ 5.384903] sock_recv_errqueue+0x22f/0x380 [ 5.384903] tls_sw_recvmsg+0x7ed/0x1960 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? schedule+0x6d/0x270 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? mutex_unlock+0x81/0xd0 [ 5.384903] ? __pfx_mutex_unlock+0x10/0x10 [ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10 [ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0 [ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5

The crash offset 296 corresponds to skb2->cb within skbuff_fclones:

  • sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 -
offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 = 272 + 24 (inside sock_exterr_skb.ee)

This patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure.

[1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885 [2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104 [3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566 [4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491 [5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719

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.1% × 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. 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

January 21, 2026

Last Modified

October 19, 2026

Advisory Details (9)

Auto-updated Jul 14, 2026
Patch available.
Web page

SSA-253495

https://cert-portal.siemens.com/productcert/html/ssa-253495.html
Web page

SSA-019113

https://cert-portal.siemens.com/productcert/html/ssa-019113.html
Web page

net: sock: fix hardened usercopy panic in sock_recv_errqueue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e00b169eaac5f7cdbf710c354c8fa76d02009115
Web page

net: sock: fix hardened usercopy panic in sock_recv_errqueue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c655d2167bf014d4c61b4faeca59b60ff9b9f6b1
Web page

net: sock: fix hardened usercopy panic in sock_recv_errqueue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8c6901aa29626e35045130bac09b75f791acca85
Web page

net: sock: fix hardened usercopy panic in sock_recv_errqueue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88dd6be7ebb3153b662c2cebcb06e032a92857f5
Web page

net: sock: fix hardened usercopy panic in sock_recv_errqueue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/582a5e922a9652fcbb7d0165c95d5b20aa37575d
Web page

net: sock: fix hardened usercopy panic in sock_recv_errqueue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a71a1a8d0ed718b1c7a9ac61f07e5755c47ae20
Web page

net: sock: fix hardened usercopy panic in sock_recv_errqueue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/005671c60fcf1dbdb8bddf12a62568fd5e4ec391

Vendor Advisories for CVE-2026-22977(3)

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

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1031.31) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-10-19ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-10-19ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-10-19ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1094.98) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-10-19ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1030.30) @ noble2026-10-19ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1099.98) @ jammy2026-10-19ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-10-19ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1019.19~24.04.3+1) @ noble2026-10-19ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.17.0-1018.20~24.04.1) @ noble2026-10-19ubuntu
linuxKernel @ 5.10.248 (fixes >=4.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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (48 versions)
  • every version up to 5.10.249-1: fixed in 5.10.249-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)
  • every version up to 6.1.162-1~deb11u1: fixed in 6.1.162-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)
  • every version up to 6.1.162-1: fixed in 6.1.162-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)
  • every version up to 6.12.69-1: fixed in 6.12.69-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (97 versions)
  • every version up to 6.18.8-1: fixed in 6.18.8-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 41× 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 99 of 212 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 113 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-22977?
CVE-2026-22977 is a medium-severity vulnerability; its CVE record was published on January 21, 2026. In the Linux kernel, the following vulnerability has been resolved: net: sock: fix hardened usercopy panic in sock_recv_errqueue skbuff_fclone_cache was created without defining a usercopy region, [1] unlike skbuff_head_cache which properly whitelists the cb[] field. [2] This causes a usercopy…
When was the CVE record for CVE-2026-22977 published?
The CVE record for CVE-2026-22977 was published on January 21, 2026. 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 19, 2026; the record at its source may have been updated since.
Is CVE-2026-22977 actively exploited?
CVE-2026-22977 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-2026-22977?
CVE-2026-22977 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-22977?
A fix for CVE-2026-22977 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-22977 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-2026-22977

Explore →

Is Your Infrastructure Affected by CVE-2026-22977?

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

Book a Demo →Browse All CVEs