What is CVE-2023-52505?

CVE-2023-52505 is a Medium severity Linux kernel vulnerability with a CVSS score of 4.7 out of 10, classified as a Improper Locking flaw (CWE-667), affecting Linux kernel versions from 5.18 onward and patched in 6.1.59, 6.5.8 and 6.6. CVE-2023-52505 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

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

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

Yes, CVE-2023-52505 has been patched. Fixed versions include 6.1.59, 6.5.8 and 6.6. If you are running Linux kernel 5.18 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2023-52505 actively exploited?

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

What is Improper Locking (CWE-667)?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/667.html

CVE-2023-52505

Medium

In the Linux kernel, the following vulnerability has been resolved: phy: lynx-28g: serialize concurrent phy_set_mode_ext() calls to shared registers The protocol converter configuration registers PCC8, PCCC, PCCD (implemented by the driver), as well as others, control protocol converters from multiple lanes (each represented as a different struct phy). So, if there are simultaneous calls to phy_set_mode_ext() to lanes sharing the same PCC register (either for the "old" or for the "new" protocol), corruption of the values programmed to hardware is possible, because lynx_28g_rmw() has no locking. Add a spinlock in the struct lynx_28g_priv shared by all lanes, and take the global spinlock from the phy_ops :: set_mode() implementation. There are no other callers which modify PCC registers.

Package Linux Kernel

Published 2024-03-02

Last modified 2025-01-13

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

4.7

out of 10

Medium

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Vector string

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

Weakness type

CWE-667

CVE-2023-52505 is a Improper Locking vulnerability

What is Improper Locking?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. Learn more on MITRE CWE

Affected versions

Linux kernel versions 5.18 and later are affected. Fixed in 6.1.59, 6.5.8, 6.6 and their respective stable series.

Affected from

≥ 5.18

Fixed in

✓ 6.1.59 6.1.x ✓ 6.5.8 6.5.x ✓ 6.6

References

3 total

Kernel Git
https://git.kernel.org/stable/c/139ad1143151a07be93bf741d4ea7c89e59f89ce

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

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

Patch

Details

CVE ID CVE-2023-52505

Severity Medium

CVSS score 4.7 / 10

CVSS version 3.1

Published 2024-03-02

Modified 2025-01-13

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2023-52505?

CVE-2023-52505 is a Medium severity Linux kernel vulnerability with a CVSS score of 4.7 out of 10 , classified as an Improper Locking flaw (CWE-667) . It affects Linux kernel versions from 5.18 onward and has been patched in 6.1.59, 6.5.8 and 6.6. CVE-2023-52505 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2023-52505?

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

Yes. CVE-2023-52505 has been patched. Fixed versions include 6.1.59, 6.5.8 and 6.6. If you are running Linux kernel 5.18 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2023-52505 actively exploited?

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