CVE-2022-49221
Last modified
CVE-2022-49221 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: drm/msm/dp: populate connector of struct dp_panel DP CTS test case 4.2.2.6 has valid edid with bad checksum on purpose and expect DP source return correct checksum. During drm edid read, correct edid checksum is calculated and stored at connector::real_edid_checksum. The problem is struct dp_panel::connector never be assigned, instead the connector is stored in struct msm_dp::connector. EPSS estimates a 0.25% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dp: populate connector of struct dp_panel DP CTS test case 4.2.2.6 has valid edid with bad checksum on purpose and expect DP source return correct checksum. During drm edid read, correct edid checksum is calculated and stored at connector::real_edid_checksum. The problem is struct dp_panel::connector never be assigned, instead the connector is stored in struct msm_dp::connector. When we run compliance testing test case 4.2.2.6 dp_panel_handle_sink_request() won't have a valid edid set in struct dp_panel::edid so we'll try to use the connectors real_edid_checksum and hit a NULL pointer dereference error because the connector pointer is never assigned. Changes in V2: -- populate panel connector at msm_dp_modeset_init() instead of at dp_panel_read_sink_caps() Changes in V3: -- remove unhelpful kernel crash trace commit text -- remove renaming dp_display parameter to dp Changes in V4: -- add more details to commit text Changes in v10: -- group into one series Changes in v11: -- drop drm/msm/dp: dp_link_parse_sink_count() return immediately if aux read Signee-off-by: Kuogee Hsieh <quic_khsieh@quicinc.com>
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.10.67, < 5.10.110 |
| Linux | Linux Kernel | >= 5.13.19, < 5.14 |
| Linux | Linux Kernel | >= 5.14.6, < 5.15.33 |
| Linux | Linux Kernel | >= 5.16, < 5.16.19 |
| Linux | Linux Kernel | >= 5.17, < 5.17.2 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-49221?
How severe is CVE-2022-49221?
How do I fix CVE-2022-49221?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-49216In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49217In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49218In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-49219In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-4922Inappropriate implementation in Blink in Google Chrome prior…6.5
- CVE-2022-49220In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49222In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49223In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-49224In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49225In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49226In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49227In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-49221?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
