“—” beside the score: it is equal to the CVSS score beside it.
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-12-30. The CNA's CVSS baseline 7.5; sources differ by 0.0.
A fix is available — apply it.
In the Linux kernel, the following vulnerability has been resolved:
tcp: fix a signed-integer-overflow bug in tcp_add_backlog()
The type of sk_rcvbuf and sk_sndbuf in struct sock is int, and in tcp_add_backlog(), the variable limit is caculated by adding sk_rcvbuf, sk_sndbuf and 64 * 1024, it may exceed the max value of int and overflow. This patch reduces the limit budget by halving the sndbuf to solve this issue since ACK packets are much smaller than the payload.
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.
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
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.
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
December 30, 2025
August 5, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Red Hat Security Advisory: kernel security update
Red Hat Security Advisory: kernel security update
Red Hat Security Advisory: kernel security update
Red Hat Security Advisory: kernel-rt security update
Red Hat Security Advisory: kernel security update
Red Hat Security Advisory: kernel security update
Red Hat Security Advisory: kernel-rt security update
Red Hat Security Advisory: kernel security update
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | kernel-0:4.18.0-193.187.1.el8_2 | 2026-02-26 | redhat |
| redhat | kernel-0:4.18.0-305.186.1.el8_4 | 2026-02-25 | redhat |
| redhat | kernel-0:4.18.0-477.130.1.el8_8 | 2026-02-25 | redhat |
| redhat | kernel-rt-0:5.14.0-70.165.1.rt21.237.el9_0 | 2026-02-11 | redhat |
| redhat | kernel-0:4.18.0-372.179.1.el8_6 | 2026-02-11 | redhat |
| redhat | kernel-0:5.14.0-70.165.1.el9_0 | 2026-02-11 | redhat |
| redhat | kernel-0:5.14.0-284.155.1.el9_2 | 2026-02-04 | redhat |
| redhat | kernel-rt-0:5.14.0-284.155.1.rt14.440.el9_2 | 2026-02-04 | redhat |
| redhat | kernel-0:4.18.0-553.100.1.el8_10 | 2026-02-02 | redhat |
| redhat | kernel-rt-0:4.18.0-553.100.1.rt7.441.el8_10 | 2026-02-02 | redhat |
| redhat | kernel-0:5.14.0-362.8.1.el9_3 | 2023-11-07 | redhat |
| linux | Kernel @ 5.4.278 (fixes >=4.9.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.
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 5.10.103-1 ... 5.10.92-2 (22 versions) |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | — |
| — |
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 240 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 142 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
redhat:RHSA-2026:1661 · redhat:RHSA-2026:1909 · redhat:RHSA-2026:2490
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-50865
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.