CVE-2022-50287: drm/i915/bios: fix a memory leak in generate_lfp_data_ptrs
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/bios: fix a memory leak in generate_lfp_data_ptrs
When (size != 0 || ptrs->lvds_ entries != 3), the program tries to
free() the ptrs. However, the ptrs is not created by calling kzmalloc(),
but is obtained by pointer offset operation.
This may lead to memory leaks or undefined behavior.
Fix this by replacing the arguments of kfree() with ptrs_block.
(cherry picked from commit 7674cd0b7d28b952151c3df26bbfa7e07eb2b4ec)
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel graphics driver memory-management flaw. The public record says incorrect freeing of a pointer in the Intel i915 BIOS parsing path may cause memory leaks or undefined behavior. No CVSS score or active exploitation is provided in the supplied sources.
Executive priority
Treat as a kernel maintenance issue with incomplete severity data. It deserves tracking and patching where affected kernels are present, but the provided evidence does not support emergency response absent vendor escalation or confirmed exposure on critical systems.
Technical view
In drm/i915/bios generate_lfp_data_ptrs, the code could call kfree() on ptrs, which was derived by pointer offset rather than allocated with kzmalloc(). The fix changes the free target to ptrs_block. Impact details are limited to memory leaks or undefined behavior.
Likely exposure
Exposure appears limited to Linux systems running the affected kernel versions listed in the CVE data and reaching the drm/i915 BIOS code path. The bundle names Linux kernel versions including 5.19, 6.0.16, 6.1.2, and 6.2 as affected, but does not provide full deployment context.
Exploitation context
The supplied bundle marks KEV as false and cites no active exploitation. It also does not describe a public exploit, trigger path, privilege requirement, or reliable security impact beyond memory leak or undefined behavior.
Researcher notes
The record lacks CVSS, CWE, exploitability notes, and detailed affected-range semantics. Focus validation on kernel version, i915 reachability, and presence of the stable fix. Avoid inferring remote exploitability or broader Linux impact from the current evidence.
Mitigation direction
Check your Linux distribution or kernel vendor guidance for fixed packages.
Update affected kernels to versions containing the referenced stable commits.
Prioritize systems using the Intel i915 graphics driver path.
Include this in normal kernel patch cycles unless vendor guidance raises severity.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and appliances.
Confirm whether exposed systems use or load the i915 driver.
Check vendor kernel changelogs for the referenced stable commits.
Record exceptions where affected kernels cannot be updated promptly.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CVE-2022-50287 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
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.
Sep 15, 2025, 14:21 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.