<?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, 09 Oct 2026 02:35:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-22014 — soc: qcom: pdr: Fix the potential deadlock</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-22014</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;soc: qcom: pdr: Fix the potential deadlock&lt;/p&gt;
&lt;p&gt;When some client process A call pdr_add_lookup() to add the look up for
the service and does schedule locator work, later a process B got a new
server packet indicating locator is up and call pdr_locator_new_server()
which eventually sets pdr-&amp;gt;locator_init_complete to true which process A
sees and takes list lock and queries domain list but it will timeout due
to deadlock as the response will queued to the same qmi-&amp;gt;wq and it is
ordered workqueue and process B is not able to complete new server
request work due to deadlock on list lock.&lt;/p&gt;
&lt;p&gt;Fix it by removing the unnecessary list iteration as the list iteration
is already being done inside locator work, so avoid it here and just
call schedule_work() here.&lt;/p&gt;
&lt;p&gt;Process A                        Process B&lt;/p&gt;
&lt;p&gt;process_scheduled_works()
pdr_add_lookup()                      qmi_data_ready_work()
 process_scheduled_works()             pdr_locator_new_server()
                                         pdr-&amp;gt;locator_init_complete=true;
   pdr_locator_work()
    mutex_lock(&amp;amp;pdr-&amp;gt;list_lock);&lt;/p&gt;
&lt;p&gt;pdr_locate_service()                  mutex_lock(&amp;amp;pdr-&amp;gt;list_lock);&lt;/p&gt;
&lt;p&gt;pdr_get_domain_list()
       pr_err(&amp;#34;PDR: %s get domain list
               txn wait failed: %d\n&amp;#34;,
               req-&amp;gt;service_name,
               ret);&lt;/p&gt;
&lt;p&gt;Timeout error log due to deadlock:&lt;/p&gt;
&lt;p&gt;&amp;#34;
 PDR: tms/servreg get domain lis…&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;soc: qcom: pdr: Fix the potential deadlock&lt;/p&gt;
&lt;p&gt;When some client process A call pdr_add_lookup() to add the look up for
the service and does schedule locator work, later a process B got a new
server packet indicating locator is up and call pdr_locator_new_server()
which eventually sets pdr-&amp;gt;locator_init_complete to true which process A
sees and takes list lock and queries domain list but it will timeout due
to deadlock as the response will queued to the same qmi-&amp;gt;wq and it is
ordered workqueue and process B is not able to complete new server
request work due to deadlock on list lock.&lt;/p&gt;
&lt;p&gt;Fix it by removing the unnecessary list iteration as the list iteration
is already being done inside locator work, so avoid it here and just
call schedule_work() here.&lt;/p&gt;
&lt;p&gt;Process A                        Process B&lt;/p&gt;
&lt;p&gt;process_scheduled_works()
pdr_add_lookup()                      qmi_data_ready_work()
 process_scheduled_works()             pdr_locator_new_server()
                                         pdr-&amp;gt;locator_init_complete=true;
   pdr_locator_work()
    mutex_lock(&amp;amp;pdr-&amp;gt;list_lock);&lt;/p&gt;
&lt;p&gt;pdr_locate_service()                  mutex_lock(&amp;amp;pdr-&amp;gt;list_lock);&lt;/p&gt;
&lt;p&gt;pdr_get_domain_list()
       pr_err(&amp;#34;PDR: %s get domain list
               txn wait failed: %d\n&amp;#34;,
               req-&amp;gt;service_name,
               ret);&lt;/p&gt;
&lt;p&gt;Timeout error log due to deadlock:&lt;/p&gt;
&lt;p&gt;&amp;#34;
 PDR: tms/servreg get domain lis…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-22014</guid>
    </item>
    <item>
      <title>USN-7591-1 — linux, linux-gcp, linux-gke, linux-gkeop, linux-ibm, linux-kvm, linux-lowlatency, linux-nvidia, linux-nvidia-tegra, lin…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7591-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-gke, Ubuntu:22.04:LTS: linux-gkeop, Ubuntu:22.04:LTS: linux-ibm, Ubuntu:22.04:LTS: linux-kvm, Ubuntu:22.04:LTS: linux-lowlatency, Ubuntu:22.04:LTS: linux-nvidia, Ubuntu:22.04:LTS: linux-nvidia-tegra, Ubuntu:22.04:LTS: linux-nvidia-tegra-igx and 1 more&lt;/p&gt;
&lt;p&gt;Michael Randrianantenaina discovered that the Bluetooth driver in the Linux
Kernel contained an improper access control vulnerability. A nearby
attacker could use this to connect a rougue device and possibly execute
arbitrary code. (CVE-2024-8805)&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly verify the target namespace when handling
upcalls. An attacker could use this to expose sensitive information.
(CVE-2025-2312)&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:
  - PowerPC architecture;
  - x86 architecture;
  - ACPI drivers;
  - Clock framework and drivers;
  - GPU drivers;
  - HID subsystem;
  - InfiniBand drivers;
  - Media drivers;
  - MemoryStick subsystem;
  - Network drivers;
  - Mellanox network drivers;
  - NTB driver;
  - PCI subsystem;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - QCOM SoC drivers;
  - Thermal drivers;
  - BTRFS file system;
  - Ext4 file system;
  - JFS file system;
  - Network file system (NFS) server daemon;
  - NTFS3 file system;
  - File systems infrastructure;
  - Proc file system;
  - SMB network file system;
  - IPv6 networking;
  - RDMA verbs API;
  - SoC audio core drivers;
  - Tracing infrastructure;
  - Watch queue notification mechanism;
  - 802.1Q VLAN protocol;
  - Asynchronous Transfer Mo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-gke, Ubuntu:22.04:LTS: linux-gkeop, Ubuntu:22.04:LTS: linux-ibm, Ubuntu:22.04:LTS: linux-kvm, Ubuntu:22.04:LTS: linux-lowlatency, Ubuntu:22.04:LTS: linux-nvidia, Ubuntu:22.04:LTS: linux-nvidia-tegra, Ubuntu:22.04:LTS: linux-nvidia-tegra-igx and 1 more&lt;/p&gt;
&lt;p&gt;Michael Randrianantenaina discovered that the Bluetooth driver in the Linux
Kernel contained an improper access control vulnerability. A nearby
attacker could use this to connect a rougue device and possibly execute
arbitrary code. (CVE-2024-8805)&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly verify the target namespace when handling
upcalls. An attacker could use this to expose sensitive information.
(CVE-2025-2312)&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:
  - PowerPC architecture;
  - x86 architecture;
  - ACPI drivers;
  - Clock framework and drivers;
  - GPU drivers;
  - HID subsystem;
  - InfiniBand drivers;
  - Media drivers;
  - MemoryStick subsystem;
  - Network drivers;
  - Mellanox network drivers;
  - NTB driver;
  - PCI subsystem;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - QCOM SoC drivers;
  - Thermal drivers;
  - BTRFS file system;
  - Ext4 file system;
  - JFS file system;
  - Network file system (NFS) server daemon;
  - NTFS3 file system;
  - File systems infrastructure;
  - Proc file system;
  - SMB network file system;
  - IPv6 networking;
  - RDMA verbs API;
  - SoC audio core drivers;
  - Tracing infrastructure;
  - Watch queue notification mechanism;
  - 802.1Q VLAN protocol;
  - Asynchronous Transfer Mo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7591-1</guid>
    </item>
  </channel>
</rss>
