<?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:24:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38516 — pinctrl: qcom: msm: mark certain pins as invalid for interrupts</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38516</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: qcom: msm: mark certain pins as invalid for interrupts&lt;/p&gt;
&lt;p&gt;On some platforms, the UFS-reset pin has no interrupt logic in TLMM but
is nevertheless registered as a GPIO in the kernel. This enables the
user-space to trigger a BUG() in the pinctrl-msm driver by running, for
example: `gpiomon -c 0 113` on RB2.&lt;/p&gt;
&lt;p&gt;The exact culprit is requesting pins whose intr_detection_width setting
is not 1 or 2 for interrupts. This hits a BUG() in
msm_gpio_irq_set_type(). Potentially crashing the kernel due to an
invalid request from user-space is not optimal, so let&amp;#39;s go through the
pins and mark those that would fail the check as invalid for the irq chip
as we should not even register them as available irqs.&lt;/p&gt;
&lt;p&gt;This function can be extended if we determine that there are more
corner-cases like this.&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: qcom: msm: mark certain pins as invalid for interrupts&lt;/p&gt;
&lt;p&gt;On some platforms, the UFS-reset pin has no interrupt logic in TLMM but
is nevertheless registered as a GPIO in the kernel. This enables the
user-space to trigger a BUG() in the pinctrl-msm driver by running, for
example: `gpiomon -c 0 113` on RB2.&lt;/p&gt;
&lt;p&gt;The exact culprit is requesting pins whose intr_detection_width setting
is not 1 or 2 for interrupts. This hits a BUG() in
msm_gpio_irq_set_type(). Potentially crashing the kernel due to an
invalid request from user-space is not optimal, so let&amp;#39;s go through the
pins and mark those that would fail the check as invalid for the irq chip
as we should not even register them as available irqs.&lt;/p&gt;
&lt;p&gt;This function can be extended if we determine that there are more
corner-cases like this.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38516</guid>
    </item>
  </channel>
</rss>
