In the Linux kernel, the following vulnerability has been resolved:
media: imx-jpeg: Align upwards buffer size
The hardware can support any image size WxH,
with arbitrary W (image width) and H (image height) dimensions.
Align upwards buffer size for both encoder and decoder.
and leave the picture resolution unchanged.
For decoder, the risk of memory out of bounds can be avoided.
For both encoder and decoder, the driver will lift the limitation of
resolution alignment.
For example, the decoder can support jpeg whose resolution is 227x149
the encoder can support nv12 1080P, won't change it to 1920x1072.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel driver flaw in the i.MX JPEG media component. Certain image sizes could cause the decoder to use an incorrectly sized buffer, creating a memory out-of-bounds risk. The public record does not provide a CVSS score or evidence of exploitation.
Executive priority
Set priority after confirming whether affected i.MX JPEG hardware and driver paths exist in the environment. If present in production appliances or embedded systems, schedule kernel updates through normal security maintenance. No source currently supports emergency response for active exploitation.
Technical view
The imx-jpeg driver failed to align encoder and decoder buffer sizes upward while preserving picture resolution. The fix changes buffer sizing so arbitrary width and height inputs are supported without decoder out-of-bounds memory risk. The source data identifies Linux kernel versions and stable commits but gives limited range detail.
Likely exposure
Exposure is most likely on Linux systems using the imx-jpeg media driver, typically hardware platforms with i.MX JPEG acceleration. Generic Linux servers without this driver or hardware path are less likely exposed, but downstream kernel configuration must be checked.
Exploitation context
The source bundle does not report active exploitation, KEV listing, public exploit availability, impact scope, or attacker prerequisites. Treat this as a kernel memory-safety issue requiring asset-specific validation rather than an internet-wide emergency based on current evidence.
Researcher notes
The record is sparse: no CVSS, CWE, exploit status, or detailed affected-version ranges are provided. The core issue is decoder out-of-bounds memory risk from buffer alignment behavior. Research should focus on kernel config, driver reachability, and whether downstream kernels include the stable commits.
Mitigation direction
Apply vendor kernel updates containing the referenced Linux stable fixes.
Confirm downstream distributions have backported the imx-jpeg buffer alignment change.
Prioritize systems using i.MX JPEG encode or decode functionality.
Check vendor guidance if no patched kernel is available.
Track CVE updates because severity and affected range details are incomplete.
Validation and detection
Inventory kernels and identify systems with the imx-jpeg driver enabled.
Compare deployed kernels against vendor advisories and referenced stable commits.
Review media workloads that decode JPEGs through i.MX acceleration.
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-50182 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
5Source 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.
Jun 18, 2025, 11:03 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.