<?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://vulnerability.circl.lu</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, 29 Sep 2026 03:54:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80648 — pinctrl: spacemit: fix NULL check in spacemit_pin_set_config</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80648</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;pinctrl: spacemit: fix NULL check in spacemit_pin_set_config&lt;/p&gt;
&lt;p&gt;spacemit_pin_set_config() looks up the per-pin descriptor with
spacemit_get_pin() then checks the wrong variable for failure:&lt;/p&gt;
&lt;p&gt;const struct spacemit_pin *spin = spacemit_get_pin(pctrl, pin);
	...
	if (!pin)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;reg = spacemit_pin_to_reg(pctrl, spin-&amp;gt;pin);&lt;/p&gt;
&lt;p&gt;pin is an unsigned int pin id, where 0 (GPIO_0 / gmac0_rxdv on K3) is a
valid pin, so rejecting it here drops the PAD config write for the first
pin of every group. On K3 Pico-ITX the GMAC RGMII group lists pin 0 as
its first entry, so its drive-strength / bias configuration was silently
ignored.&lt;/p&gt;
&lt;p&gt;The intended guard is against spacemit_get_pin() returning NULL when the
pin id isn&amp;#39;t in the SoC&amp;#39;s pin table. Check spin instead, which both
restores PAD setup for pin 0 and prevents a NULL deref on spin-&amp;gt;pin.&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;pinctrl: spacemit: fix NULL check in spacemit_pin_set_config&lt;/p&gt;
&lt;p&gt;spacemit_pin_set_config() looks up the per-pin descriptor with
spacemit_get_pin() then checks the wrong variable for failure:&lt;/p&gt;
&lt;p&gt;const struct spacemit_pin *spin = spacemit_get_pin(pctrl, pin);
	...
	if (!pin)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;reg = spacemit_pin_to_reg(pctrl, spin-&amp;gt;pin);&lt;/p&gt;
&lt;p&gt;pin is an unsigned int pin id, where 0 (GPIO_0 / gmac0_rxdv on K3) is a
valid pin, so rejecting it here drops the PAD config write for the first
pin of every group. On K3 Pico-ITX the GMAC RGMII group lists pin 0 as
its first entry, so its drive-strength / bias configuration was silently
ignored.&lt;/p&gt;
&lt;p&gt;The intended guard is against spacemit_get_pin() returning NULL when the
pin id isn&amp;#39;t in the SoC&amp;#39;s pin table. Check spin instead, which both
restores PAD setup for pin 0 and prevents a NULL deref on spin-&amp;gt;pin.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80648</guid>
    </item>
  </channel>
</rss>
