CVE-2022-49218: drm/dp: Fix OOB read when handling Post Cursor2 register
In the Linux kernel, the following vulnerability has been resolved:
drm/dp: Fix OOB read when handling Post Cursor2 register
The link_status array was not large enough to read the Adjust Request
Post Cursor2 register, so remove the common helper function to avoid
an OOB read, found with a -Warray-bounds build:
drivers/gpu/drm/drm_dp_helper.c: In function 'drm_dp_get_adjust_request_post_cursor':
drivers/gpu/drm/drm_dp_helper.c:59:27: error: array subscript 10 is outside array bounds of 'const u8[6]' {aka 'const unsigned char[6]'} [-Werror=array-bounds]
59 | return link_status[r - DP_LANE0_1_STATUS];
| ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/drm_dp_helper.c:147:51: note: while referencing 'link_status'
147 | u8 drm_dp_get_adjust_request_post_cursor(const u8 link_status[DP_LINK_STATUS_SIZE],
| ~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Replace the only user of the helper with an open-coded fetch and decode,
similar to drivers/gpu/drm/amd/display/dc/core/dc_link_dp.c.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49218 is an out-of-bounds read in the Linux kernel DisplayPort DRM helper code. A local user with low privileges could potentially read sensitive memory or cause impact to availability. It is not listed as actively exploited in KEV, and the public record points to upstream kernel fixes.
Executive priority
Treat as a high-priority kernel maintenance issue where local users exist. It is not an internet-facing remote bug based on the provided CVSS vector, but kernel memory disclosure and availability impact justify timely patching.
Technical view
The flaw is CWE-125 in drm/dp handling of the Adjust Request Post Cursor2 register. The link_status array was too small for the helper’s index calculation, triggering an out-of-bounds read. Upstream resolved it by removing the shared helper and open-coding the fetch/decode in the only user.
Likely exposure
Exposure is most likely on systems running affected Linux kernel versions with DRM/DisplayPort code present. The CVE record indicates affected Linux kernel ranges around 5.5 through fixes in 5.17.2 and 5.18, but operators should verify against their vendor kernel package status.
Exploitation context
The CVSS vector is local, low complexity, low privileges required, and no user interaction. No KEV listing or provided source reports active exploitation. Practical exploitation details are not established in the provided sources.
Researcher notes
The public description says the issue was found via -Warray-bounds during build analysis. Review the two upstream stable commits for exact code changes and map them to distribution backports. Do not assume exploitability beyond the local CVSS context without additional evidence.
Mitigation direction
Apply Linux kernel updates that include the referenced upstream stable fixes.
Check your Linux distribution advisory for backported fixes and exact package versions.
Prioritize shared workstations, developer systems, and hosts with local user access.
Validation and detection
Inventory Linux kernel versions across endpoints and servers.
Compare installed kernels with vendor advisories for CVE-2022-49218.
Confirm fixed kernel packages are deployed and running after reboot.
Review whether systems use DRM/DisplayPort-capable graphics paths.
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.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.