Answer in brief
CVE-2022-50201 records a Medium severity (CVSS 5.5) vulnerability in selinux: fix memleak in security_read_state_kernel(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=fdd1ffe8a812b1109388e4bc389e57b2695ad095 <c877c5217145bda8fd95f506bf42f8d981afa57d || >=fdd1ffe8a812b1109388e4bc389e57b2695ad095 <f3cd7562c0a6774fc62d79654482014020e574f5 || >=fdd1ffe8a812b1109388e4bc389e57b2695ad095 <1fc1f72aad2070d34022d0823e4cf09706b53f25 || >=fdd1ffe8a812b1109388e4bc389e57b2695ad095 <73de1befcc53a7c68b0c5e76b9b5ac41c517760f | c877c5217145bda8fd95f506bf42f8d981afa57d, f3cd7562c0a6774fc62d79654482014020e574f5, 1fc1f72aad2070d34022d0823e4cf09706b53f25, 73de1befcc53a7c68b0c5e76b9b5ac41c517760f |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In the Linux kernel, the following vulnerability has been resolved: selinux: fix memleak in security_read_state_kernel() In this function, it directly returns the result of __security_read_policy without freeing the allocated memory in *data, cause memory leak issue, so free the memory if __security_read_policy failed. [PM: subject line tweak]
Quoted source text, attributed separately from HOL analysis.