You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
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.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
OR
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.18 up to (excluding) 6.1.59
*cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.5.8
*cpe:2.3:o:linux:linux_kernel:6.6:rc1:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:6.6:rc2:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:6.6:rc3:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:6.6:rc4:*:*:*:*:*:*
*cpe:2.3:o:linux:linux_kernel:6.6:rc5:*:*:*:*:*:*
Changed
Reference Type
https://git.kernel.org/stable/c/139ad1143151a07be93bf741d4ea7c89e59f89ce No Types Assigned
New CVE Received from kernel.org3/02/2024 5:15:47 PM
Action
Type
Old Value
New Value
Added
Description
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.
Added
Reference
Linux https://git.kernel.org/stable/c/139ad1143151a07be93bf741d4ea7c89e59f89ce [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/6f901f8448c6b25ed843796b114471d2a3fc5dfb [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/c2d7c79898b427d263c64a4841987eec131f2d4e [No types assigned]
Quick Info
CVE Dictionary Entry: CVE-2023-52505 NVD
Published Date: 03/02/2024 NVD
Last Modified: 06/17/2026
Source: kernel.org