<?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>Fri, 16 Oct 2026 09:13:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38632 — pinmux: fix race causing mux_owner NULL with active mux_usecount</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-38632</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;pinmux: fix race causing mux_owner NULL with active mux_usecount&lt;/p&gt;
&lt;p&gt;commit 5a3e85c3c397 (&amp;#34;pinmux: Use sequential access to access
desc-&amp;gt;pinmux data&amp;#34;) tried to address the issue when two client of the
same gpio calls pinctrl_select_state() for the same functionality, was
resulting in NULL pointer issue while accessing desc-&amp;gt;mux_owner.
However, issue was not completely fixed due to the way it was handled
and it can still result in the same NULL pointer.&lt;/p&gt;
&lt;p&gt;The issue occurs due to the following interleaving:&lt;/p&gt;
&lt;p&gt;cpu0 (process A)                   cpu1 (process B)&lt;/p&gt;
&lt;p&gt;pin_request() {                   pin_free() {&lt;/p&gt;
&lt;p&gt;mutex_lock()
                                         desc-&amp;gt;mux_usecount--; //becomes 0
                                         ..
                                         mutex_unlock()&lt;/p&gt;
&lt;p&gt;mutex_lock(desc-&amp;gt;mux)
  desc-&amp;gt;mux_usecount++; // becomes 1
  desc-&amp;gt;mux_owner = owner;
  mutex_unlock(desc-&amp;gt;mux)&lt;/p&gt;
&lt;p&gt;mutex_lock(desc-&amp;gt;mux)
                                         desc-&amp;gt;mux_owner = NULL;
                                         mutex_unlock(desc-&amp;gt;mux)&lt;/p&gt;
&lt;p&gt;This sequence leads to a state where the pin appears to be in use
(`mux_usecount == 1`) but has no owner (`mux_owner == NULL`), which can
cause NULL pointer on next pin_request on the same pin.&lt;/p&gt;
&lt;p&gt;Ensure that updates to mux_usecount and mux_owner are performed
atomically u…&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;pinmux: fix race causing mux_owner NULL with active mux_usecount&lt;/p&gt;
&lt;p&gt;commit 5a3e85c3c397 (&amp;#34;pinmux: Use sequential access to access
desc-&amp;gt;pinmux data&amp;#34;) tried to address the issue when two client of the
same gpio calls pinctrl_select_state() for the same functionality, was
resulting in NULL pointer issue while accessing desc-&amp;gt;mux_owner.
However, issue was not completely fixed due to the way it was handled
and it can still result in the same NULL pointer.&lt;/p&gt;
&lt;p&gt;The issue occurs due to the following interleaving:&lt;/p&gt;
&lt;p&gt;cpu0 (process A)                   cpu1 (process B)&lt;/p&gt;
&lt;p&gt;pin_request() {                   pin_free() {&lt;/p&gt;
&lt;p&gt;mutex_lock()
                                         desc-&amp;gt;mux_usecount--; //becomes 0
                                         ..
                                         mutex_unlock()&lt;/p&gt;
&lt;p&gt;mutex_lock(desc-&amp;gt;mux)
  desc-&amp;gt;mux_usecount++; // becomes 1
  desc-&amp;gt;mux_owner = owner;
  mutex_unlock(desc-&amp;gt;mux)&lt;/p&gt;
&lt;p&gt;mutex_lock(desc-&amp;gt;mux)
                                         desc-&amp;gt;mux_owner = NULL;
                                         mutex_unlock(desc-&amp;gt;mux)&lt;/p&gt;
&lt;p&gt;This sequence leads to a state where the pin appears to be in use
(`mux_usecount == 1`) but has no owner (`mux_owner == NULL`), which can
cause NULL pointer on next pin_request on the same pin.&lt;/p&gt;
&lt;p&gt;Ensure that updates to mux_usecount and mux_owner are performed
atomically u…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-38632</guid>
    </item>
    <item>
      <title>USN-7879-1 — linux, linux-aws, linux-gcp, linux-hwe-6.14, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7879-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.14&lt;/p&gt;
&lt;p&gt;It was discovered that improper initialization of CPU cache memory could
allow a local attacker with hypervisor access to overwrite SEV-SNP guest
memory resulting in loss of data integrity. (CVE-2024-36331)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Network block device driver;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - Powercap sysfs driver;
  - Voltage and Current Regulator drivers;
  - S/390 drivers;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - small TFT LCD display modules;
  - Media staging drivers;
  - USB Gadget drivers;
  - vDPA drivers;
  - VFIO drivers;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ceph distributed file sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.14&lt;/p&gt;
&lt;p&gt;It was discovered that improper initialization of CPU cache memory could
allow a local attacker with hypervisor access to overwrite SEV-SNP guest
memory resulting in loss of data integrity. (CVE-2024-36331)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Network block device driver;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - Powercap sysfs driver;
  - Voltage and Current Regulator drivers;
  - S/390 drivers;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - small TFT LCD display modules;
  - Media staging drivers;
  - USB Gadget drivers;
  - vDPA drivers;
  - VFIO drivers;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ceph distributed file sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7879-1</guid>
    </item>
  </channel>
</rss>
