<?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>Fri, 02 Oct 2026 11:16:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-23161 — PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-23161</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;PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type&lt;/p&gt;
&lt;p&gt;The access to the PCI config space via pci_ops::read and pci_ops::write is
a low-level hardware access. The functions can be accessed with disabled
interrupts even on PREEMPT_RT. The pci_lock is a raw_spinlock_t for this
purpose.&lt;/p&gt;
&lt;p&gt;A spinlock_t becomes a sleeping lock on PREEMPT_RT, so it cannot be
acquired with disabled interrupts. The vmd_dev::cfg_lock is accessed in
the same context as the pci_lock.&lt;/p&gt;
&lt;p&gt;Make vmd_dev::cfg_lock a raw_spinlock_t type so it can be used with
interrupts disabled.&lt;/p&gt;
&lt;p&gt;This was reported as:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
  Call Trace:
   rt_spin_lock+0x4e/0x130
   vmd_pci_read+0x8d/0x100 [vmd]
   pci_user_read_config_byte+0x6f/0xe0
   pci_read_config+0xfe/0x290
   sysfs_kf_bin_read+0x68/0x90&lt;/p&gt;
&lt;p&gt;[bigeasy: reword commit message]
Tested-off-by: Luis Claudio R. Goncalves &amp;lt;lgoncalv@redhat.com&amp;gt;
[kwilczynski: commit log]
[bhelgaas: add back report info from
https://lore.kernel.org/lkml/20241218115951.83062-1-ryotkkr98@gmail.com/]&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;PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type&lt;/p&gt;
&lt;p&gt;The access to the PCI config space via pci_ops::read and pci_ops::write is
a low-level hardware access. The functions can be accessed with disabled
interrupts even on PREEMPT_RT. The pci_lock is a raw_spinlock_t for this
purpose.&lt;/p&gt;
&lt;p&gt;A spinlock_t becomes a sleeping lock on PREEMPT_RT, so it cannot be
acquired with disabled interrupts. The vmd_dev::cfg_lock is accessed in
the same context as the pci_lock.&lt;/p&gt;
&lt;p&gt;Make vmd_dev::cfg_lock a raw_spinlock_t type so it can be used with
interrupts disabled.&lt;/p&gt;
&lt;p&gt;This was reported as:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
  Call Trace:
   rt_spin_lock+0x4e/0x130
   vmd_pci_read+0x8d/0x100 [vmd]
   pci_user_read_config_byte+0x6f/0xe0
   pci_read_config+0xfe/0x290
   sysfs_kf_bin_read+0x68/0x90&lt;/p&gt;
&lt;p&gt;[bigeasy: reword commit message]
Tested-off-by: Luis Claudio R. Goncalves &amp;lt;lgoncalv@redhat.com&amp;gt;
[kwilczynski: commit log]
[bhelgaas: add back report info from
https://lore.kernel.org/lkml/20241218115951.83062-1-ryotkkr98@gmail.com/]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-23161</guid>
    </item>
  </channel>
</rss>
