CVE-2023-52819: drm/amd: Fix UBSAN array-index-out-of-bounds for Polaris and Tonga

Published May 21, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

drm/amd: Fix UBSAN array-index-out-of-bounds for Polaris and Tonga

For pptable structs that use flexible array sizes, use flexible arrays.

Other sources

In the Linux kernel, the following vulnerability has been resolved:

drm/amd: Fix UBSAN array-index-out-of-bounds for Polaris and Tonga

The Linux kernel CVE team has assigned CVE-2023-52819 to this issue.

Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024052105-CVE-2023-52819-98d5@gregkh/T

Red Hat

Affected Software

17 affected componentsFixes available
redhat/kernel<4.14.331
4.14.331
redhat/kernel<4.19.300
4.19.300
redhat/kernel<5.4.262
5.4.262
redhat/kernel<5.10.202
5.10.202
redhat/kernel<5.15.140
5.15.140
redhat/kernel<6.1.64
6.1.64
redhat/kernel<6.5.13
6.5.13
redhat/kernel<6.6.3
6.6.3
redhat/kernel<6.7
6.7
Linux Linux kernel<4.14.331
Linux Linux kernel>=4.15<4.19.300
Linux Linux kernel>=4.20<5.4.262
Linux Linux kernel>=5.5<5.10.202
Linux Linux kernel>=5.11<5.15.140
Linux Linux kernel>=5.16<6.1.64
Linux Linux kernel>=6.2<6.5.13
Linux Linux kernel>=6.6<6.6.3

Event History

May 21, 2024
CVE Published
via MITRE·03:31 PM
Data Sourced
via MITRE·03:31 PM
Description
May 22, 2024
Data Sourced
via Red Hat·05:33 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2023-52819?

CVE-2023-52819 is categorized with a high severity level due to its potential impact on system stability and security.

2

How do I fix CVE-2023-52819?

To fix CVE-2023-52819, update the Linux kernel to versions 4.14.331, 4.19.300, 5.4.262, 5.10.202, 5.15.140, 6.1.64, 6.5.13, 6.6.3, or 6.7.

3

Which Linux kernel versions are affected by CVE-2023-52819?

CVE-2023-52819 affects various Linux kernel versions prior to updates 4.14.331, 4.19.300, 5.4.262, 5.10.202, 5.15.140, 6.1.64, 6.5.13, 6.6.3, and 6.7.

4

What are the potential consequences of CVE-2023-52819?

The potential consequences of CVE-2023-52819 include system crashes or data corruption due to array-index-out-of-bounds issues.

5

Is there a specific remediation timeline for CVE-2023-52819?

Organizations are encouraged to remediate CVE-2023-52819 as soon as possible, ideally by applying the latest kernel updates immediately.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203