In the Linux kernel, the following vulnerability has been resolved:
selinux: Add boundary check in put_entry()
Just like next_entry(), boundary check is necessary to prevent memory out-of-bound access.
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-06-18. NVD baseline CVSS 7.1; sources differ by 0.0.
A fix is available — apply it.
In the Linux kernel, the following vulnerability has been resolved:
selinux: Add boundary check in put_entry()
Just like next_entry(), boundary check is necessary to prevent memory out-of-bound access.
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).
June 18, 2025
November 19, 2025
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-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, bug fix, and enhancement update
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | kernel-0:5.14.0-70.142.1.el9_0 | 2025-08-19 | redhat |
| redhat | kernel-rt-0:5.14.0-70.142.1.rt21.214.el9_0 | 2025-08-19 | redhat |
| redhat | kernel-0:5.14.0-284.130.1.el9_2 | 2025-08-13 | redhat |
| redhat | kernel-rt-0:5.14.0-284.130.1.rt14.415.el9_2 | 2025-08-11 | redhat |
| redhat | kernel-0:5.14.0-362.8.1.el9_3 | 2023-11-07 | redhat |
| linux | Kernel @ 4.14.291 | — | 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.
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
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 102 total refreshes for this CVE.
Explore the affected products and dependency analysis for CVE-2022-50200
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.