<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 15:27:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52505 — phy: lynx-28g: serialize concurrent phy_set_mode_ext() calls to shared registers</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-52505</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;phy: lynx-28g: serialize concurrent phy_set_mode_ext() calls to shared registers&lt;/p&gt;
&lt;p&gt;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 &amp;#34;old&amp;#34; or for the
&amp;#34;new&amp;#34; protocol), corruption of the values programmed to hardware is
possible, because lynx_28g_rmw() has no locking.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;phy: lynx-28g: serialize concurrent phy_set_mode_ext() calls to shared registers&lt;/p&gt;
&lt;p&gt;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 &amp;#34;old&amp;#34; or for the
&amp;#34;new&amp;#34; protocol), corruption of the values programmed to hardware is
possible, because lynx_28g_rmw() has no locking.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-52505</guid>
    </item>
  </channel>
</rss>
