CVE-2022-49222: drm/bridge: anx7625: Fix overflow issue on reading EDID
In the Linux kernel, the following vulnerability has been resolved:
drm/bridge: anx7625: Fix overflow issue on reading EDID
The length of EDID block can be longer than 256 bytes, so we should use
`int` instead of `u8` for the `edid_pos` variable.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49222 is a Linux kernel bug in the anx7625 display bridge driver. When reading EDID display data, a counter could overflow because it used an 8-bit value for data that may exceed 256 bytes. The public record does not state business impact, CVSS severity, or active exploitation.
Executive priority
Handle through routine kernel patch governance unless your fleet includes affected embedded or display-focused Linux devices. There is not enough public evidence to justify emergency response, but kernel fixes should be adopted through normal maintenance windows.
Technical view
The resolved kernel issue changes the anx7625 EDID read position variable from u8 to int because EDID block length can exceed 256 bytes. This addresses an overflow condition in drm/bridge/anx7625. The CVE record lists affected Linux kernel ranges and references stable kernel commits, but provides no CWE, CVSS, or exploitability detail.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the anx7625 DRM bridge driver present and relevant display hardware paths in use. Systems without this driver or hardware path are less likely exposed, but the source data does not provide a definitive exposure test.
Exploitation context
No active exploitation is reported in the provided sources, and the CVE is not marked as CISA KEV. The sources do not describe attack prerequisites, attacker location, required privileges, or practical impact. Treat exploitability as unproven from available public evidence.
Researcher notes
Key evidence is narrow: a kernel commit-level fix for an integer width overflow during EDID reads. The public CVE lacks CVSS, CWE, impact analysis, and exploitation details. Further triage should focus on driver reachability, hardware presence, and whether downstream kernels backported the fix.
Mitigation direction
Update to a Linux kernel or vendor kernel package containing the referenced stable fixes.
Check your Linux distribution or device vendor advisory for backported fixes.
Prioritize systems using the anx7625 display bridge driver or affected embedded hardware.
Track this under normal kernel maintenance if anx7625 exposure is absent or unconfirmed.
Validation and detection
Inventory Linux kernel versions against the affected and fixed ranges in the CVE record.
Confirm whether the anx7625 DRM bridge driver is enabled or present in deployed kernels.
Verify vendor kernels include one of the referenced stable commits or an equivalent backport.
Document systems where display bridge hardware exposure cannot be confirmed.
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-49222 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.
Feb 26, 2025, 01:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.