CVE-2022-50200

HIGHNVD 7.17.1—

7.1

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.

CVSS v3: 7.1
EG Score: 7.1(medium)
EPSS: 20.1%
KEV: Not listed

Published

June 18, 2025

Last Modified

November 19, 2025

References (8)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/15ec76fb29be31df2bccb30fc09875274cba2776
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/2dabe6a872a5744865372eb30ea51e8ccd21305a
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/477722f31ad73aa779154d1d7e00825538389f76
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/7363a69d8ca8f0086f8e1196c8ddaf0e168614b1
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/90bdf50ae70c5571a277b5601e4f5df210831e0a
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/9605f50157cae00eb299e1189a6d708c84935ad8
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/adbfdaacde18faf6cd4e490764045375266b3fbd
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/dedd558d9765b72c66e5a53948e9f5abc3ece1f6

Patch Availability(5)

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

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.

Weakness Classification(1)

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

CWE-125Out-of-bounds Read

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 13× in last 7d / 20× 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.

2026-06-08 14:15 UTCEPSS rescore
2026-06-08 14:15 UTCEPSS rescore
2026-06-07 15:23 UTCEPSS rescore
2026-06-07 15:23 UTCEPSS rescore
2026-06-06 13:46 UTCEPSS rescore
2026-06-06 13:46 UTCEPSS rescore
2026-06-05 22:46 UTCEPSS rescore
2026-06-05 22:46 UTCEPSS rescore
2026-06-05 06:09 UTCEPSS rescore
2026-06-05 06:09 UTCEPSS rescore
2026-06-04 13:11 UTCEPSS rescore
2026-06-02 20:12 UTCEPSS rescore
2026-06-02 20:12 UTCEPSS rescore
2026-06-01 13:50 UTCEPSS rescore
2026-06-01 13:50 UTCEPSS rescore
2026-05-31 22:29 UTCEPSS rescore
2026-05-31 22:29 UTCEPSS rescore
2026-05-31 00:15 UTCEPSS rescore
2026-05-31 00:15 UTCEPSS rescore
2026-05-30 03:12 UTCEG score recompute

Frequently asked(5)

What is CVE-2022-50200?

CVE-2022-50200 is a high vulnerability published on June 18, 2025. 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.

When was CVE-2022-50200 disclosed?

CVE-2022-50200 was first published in the National Vulnerability Database on June 18, 2025, with the most recent update on November 19, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2022-50200 actively exploited?

CVE-2022-50200 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2022-50200?

CVE-2022-50200 has a CVSS v3 base score of 7.1 (NVD).

How do I remediate CVE-2022-50200?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50200, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-50200

Explore →

Is Your Infrastructure Affected by CVE-2022-50200?

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

Start Free Scan →Browse All CVEs

CVE-2022-50200

Published

Last Modified

References (8)

Patch Availability(5)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2022-50200?

Same vendor

Same CWE

CVE-2022-50200

📅 Published

🔄 Last Modified

🔗 References (8)

Patch Availability(5)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2022-50200?

🔗 Related CVEs(same vendor + same CWE)

Same vendor

Same CWE

Published

Last Modified

References (8)

Frequently asked(5)

Related CVEs(same vendor + same CWE)