Security readout for executives and security teams
Plain-English summary
This CVE is a Linux kernel SELinux memory-safety fix. The public record says a missing boundary check in put_entry() could allow out-of-bounds memory access. Business urgency is unclear because the source bundle provides no CVSS score, no impact rating, and no active exploitation evidence.
Executive priority
Handle through normal Linux kernel patch governance unless local exposure is high. Escalate priority for sensitive SELinux-dependent systems, but avoid emergency response claims without CVSS, exploit evidence, or vendor impact details.
Technical view
The resolved issue adds a boundary check in SELinux put_entry(), matching next_entry(), to prevent memory out-of-bounds access. The CVE record identifies Linux kernel versions as affected and links multiple stable kernel commits. The bundle does not describe attacker privileges, reachability, crash behavior, data exposure, or privilege-escalation impact.
Likely exposure
Exposure is most likely on systems running affected Linux kernels with SELinux support present. Actual risk depends on distribution backports, kernel configuration, and whether SELinux policy loading or related SELinux paths are reachable. The bundle does not provide a complete affected-version matrix.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation, public exploit availability, or real-world attacks. Treat exploitation status as unconfirmed, not known-active.
Researcher notes
The record is sparse. It identifies an SELinux out-of-bounds access fix but omits root cause depth, trigger conditions, exploitability, and security impact. Researchers should anchor analysis to the stable commits and vendor advisories rather than infer privilege escalation or remote reachability.
Mitigation direction
- Update to a vendor-supported kernel containing the referenced SELinux boundary-check fix.
- Check distribution advisories for backported fixes before judging by version string alone.
- Prioritize internet-facing, multi-tenant, and high-assurance Linux systems using SELinux.
- Track vendor guidance if running custom or long-term support kernels.
Validation and detection
- Inventory Linux kernel versions across servers, containers hosts, and appliances.
- Confirm whether SELinux is enabled or compiled into deployed kernels.
- Compare installed kernels against vendor advisories and the referenced stable commits.
- Review patch management records for SELinux kernel fixes around this CVE.
Public sources used
- CVE Program
- CVE List V5
- Linux stable commit 2dabe6a872a5744865372eb30ea51e8ccd21305a
- Linux stable commit 477722f31ad73aa779154d1d7e00825538389f76
- Linux stable commit 90bdf50ae70c5571a277b5601e4f5df210831e0a
- Linux stable commit adbfdaacde18faf6cd4e490764045375266b3fbd
- Linux stable commit 7363a69d8ca8f0086f8e1196c8ddaf0e168614b1
- Linux stable commit 9605f50157cae00eb299e1189a6d708c84935ad8
- Linux stable commit dedd558d9765b72c66e5a53948e9f5abc3ece1f6
- Linux stable commit 15ec76fb29be31df2bccb30fc09875274cba2776
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2022-50200 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/2dabe6a872a5744865372eb30ea51e8ccd21305aCVE reference, Linux
- https://git.kernel.org/stable/c/477722f31ad73aa779154d1d7e00825538389f76CVE reference, Linux
- https://git.kernel.org/stable/c/90bdf50ae70c5571a277b5601e4f5df210831e0aCVE reference, Linux
- https://git.kernel.org/stable/c/adbfdaacde18faf6cd4e490764045375266b3fbdCVE reference, Linux
- https://git.kernel.org/stable/c/7363a69d8ca8f0086f8e1196c8ddaf0e168614b1CVE reference, Linux
- https://git.kernel.org/stable/c/9605f50157cae00eb299e1189a6d708c84935ad8CVE reference, Linux
- https://git.kernel.org/stable/c/dedd558d9765b72c66e5a53948e9f5abc3ece1f6CVE reference, Linux
- https://git.kernel.org/stable/c/15ec76fb29be31df2bccb30fc09875274cba2776CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.