What is CVE-2023-52455?

CVE-2023-52455 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 6.3 onward and patched in 6.6.14, 6.7.2 and 6.8. CVE-2023-52455 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2023-52455?

CVE-2023-52455 has a CVSS score of 7.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2023-52455?

Yes, CVE-2023-52455 has been patched. Fixed versions include 6.6.14, 6.7.2 and 6.8. If you are running Linux kernel 6.3 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2023-52455 actively exploited?

CVE-2023-52455 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2023-52455

High

In the Linux kernel, the following vulnerability has been resolved: iommu: Don't reserve 0-length IOVA region When the bootloader/firmware doesn't setup the framebuffers, their address and size are 0 in "iommu-addresses" property. If IOVA region is reserved with 0 length, then it ends up corrupting the IOVA rbtree with an entry which has pfn_hi < pfn_lo. If we intend to use display driver in kernel without framebuffer then it's causing the display IOMMU mappings to fail as entire valid IOVA space is reserved when address and length are passed as 0. An ideal solution would be firmware removing the "iommu-addresses" property and corresponding "memory-region" if display is not present. But the kernel should be able to handle this by checking for size of IOVA region and skipping the IOVA reservation if size is 0. Also, add a warning if firmware is requesting 0-length IOVA region reservation.

Package Linux Kernel

Published 2024-02-23

Last modified 2024-11-21

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.3 and later are affected. Fixed in 6.6.14, 6.7.2, 6.8 and their respective stable series.

Affected from

≥ 6.3

Fixed in

✓ 6.6.14 6.6.x ✓ 6.7.2 6.7.x ✓ 6.8

References

3 total

Kernel Git
https://git.kernel.org/stable/c/5e23e283910c9f30248732ae0770bcb0c9438abf

Patch
Kernel Git
https://git.kernel.org/stable/c/98b8a550da83cc392a14298c4b3eaaf0332ae6ad

Patch
Kernel Git
https://git.kernel.org/stable/c/bb57f6705960bebeb832142ce9abf43220c3eab1

Patch

Details

CVE ID CVE-2023-52455

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2024-02-23

Modified 2024-11-21

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2023-52455?

CVE-2023-52455 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.3 onward and has been patched in 6.6.14, 6.7.2 and 6.8. CVE-2023-52455 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2023-52455?

CVE-2023-52455 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2023-52455?

Yes. CVE-2023-52455 has been patched. Fixed versions include 6.6.14, 6.7.2 and 6.8. If you are running Linux kernel 6.3 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2023-52455 actively exploited?

No. CVE-2023-52455 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.