Kernel memory disclosure via Post Cursor2 overread
Published Feb 26, 2025 · Updated May 11, 2026
Out-of-bounds read in Linux kernel DRM DisplayPort code in 5.5 through 5.17.1 allows local users to read kernel memory. drm_dp_get_adjust_request_post_cursor indexes a six-byte link_status array at the Post Cursor2 register offset, reaching index 10. Low-privileged local access is required; the read can expose kernel data or crash the system, without integrity impact.
Summary
What happened
Out-of-bounds read in Linux kernel DRM DisplayPort code in 5.5 through 5.17.1 allows local users to read kernel memory. drm_dp_get_adjust_request_post_cursor indexes a six-byte link_status array at the Post Cursor2 register offset, reaching index 10. Low-privileged local access is required; the read can expose kernel data or crash the system, without integrity impact.
The record
- CVE
- CVE-2022-49218
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125, CAPEC-540, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.5
- Affected versionversion=79465e0ffeb9e4866939ea562bc55367be91e595 <a2151490cc6c57b368d7974ffd447a8b36ade639
- Affected versionversion=79465e0ffeb9e4866939ea562bc55367be91e595 <aeaed9a9fe694f8b1462fb81e2d33298c929180b
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo