<?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://db.gcve.eu</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>Thu, 19 Nov 2026 17:30:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-47141 — pinmux: Use sequential access to access desc-&gt;pinmux data</title>
      <link>https://db.gcve.eu/vuln/cve-2024-47141</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: Use sequential access to access desc-&amp;gt;pinmux data&lt;/p&gt;
&lt;p&gt;When two client of the same gpio call pinctrl_select_state() for the
same functionality, we are seeing NULL pointer issue while accessing
desc-&amp;gt;mux_owner.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s say two processes A, B executing in pin_request() for the same pin
and process A updates the desc-&amp;gt;mux_usecount but not yet updated the
desc-&amp;gt;mux_owner while process B see the desc-&amp;gt;mux_usecount which got
updated by A path and further executes strcmp and while accessing
desc-&amp;gt;mux_owner it crashes with NULL pointer.&lt;/p&gt;
&lt;p&gt;Serialize the access to mux related setting with a mutex lock.&lt;/p&gt;
&lt;p&gt;cpu0 (process A)			cpu1(process B)&lt;/p&gt;
&lt;p&gt;pinctrl_select_state() {		  pinctrl_select_state() {
  pin_request() {				pin_request() {
  ...
						 ....
    } else {
         desc-&amp;gt;mux_usecount++;
    						desc-&amp;gt;mux_usecount &amp;amp;&amp;amp; strcmp(desc-&amp;gt;mux_owner, owner)) {&lt;/p&gt;
&lt;p&gt;if (desc-&amp;gt;mux_usecount &amp;gt; 1)
               return 0;
         desc-&amp;gt;mux_owner = owner;&lt;/p&gt;
&lt;p&gt;}						}&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: Use sequential access to access desc-&amp;gt;pinmux data&lt;/p&gt;
&lt;p&gt;When two client of the same gpio call pinctrl_select_state() for the
same functionality, we are seeing NULL pointer issue while accessing
desc-&amp;gt;mux_owner.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s say two processes A, B executing in pin_request() for the same pin
and process A updates the desc-&amp;gt;mux_usecount but not yet updated the
desc-&amp;gt;mux_owner while process B see the desc-&amp;gt;mux_usecount which got
updated by A path and further executes strcmp and while accessing
desc-&amp;gt;mux_owner it crashes with NULL pointer.&lt;/p&gt;
&lt;p&gt;Serialize the access to mux related setting with a mutex lock.&lt;/p&gt;
&lt;p&gt;cpu0 (process A)			cpu1(process B)&lt;/p&gt;
&lt;p&gt;pinctrl_select_state() {		  pinctrl_select_state() {
  pin_request() {				pin_request() {
  ...
						 ....
    } else {
         desc-&amp;gt;mux_usecount++;
    						desc-&amp;gt;mux_usecount &amp;amp;&amp;amp; strcmp(desc-&amp;gt;mux_owner, owner)) {&lt;/p&gt;
&lt;p&gt;if (desc-&amp;gt;mux_usecount &amp;gt; 1)
               return 0;
         desc-&amp;gt;mux_owner = owner;&lt;/p&gt;
&lt;p&gt;}						}&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-47141</guid>
    </item>
    <item>
      <title>USN-7379-1 — linux, linux-aws, linux-azure, linux-gcp, linux-hwe-6.11, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7379-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11&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;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Virtio block driver;
  - Bluetooth drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I3C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Microchip PCI driver;
  - MTD block device drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - i.MX PM domains;
  - Power supply drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - i.MX SoC drivers;
  - SPI subsystem;
  - UFS subsystem;
  - USB Gadget drivers;
  - TDX Guest driver;
  - AFS file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - F2FS file system;
  - JFFS…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11&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;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Virtio block driver;
  - Bluetooth drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I3C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Microchip PCI driver;
  - MTD block device drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - i.MX PM domains;
  - Power supply drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - i.MX SoC drivers;
  - SPI subsystem;
  - UFS subsystem;
  - USB Gadget drivers;
  - TDX Guest driver;
  - AFS file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - F2FS file system;
  - JFFS…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7379-1</guid>
    </item>
  </channel>
</rss>
