{"uuid": "bd05b16a-93ab-4658-a3a4-a195336320e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-23161", "type": "seen", "source": "https://t.me/cvedetector/24228", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-23161 - Linux kernel PCI VMD Raw Spinlock Type Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-23161 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nPCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type  \n  \nThe access to the PCI config space via pci_ops::read and pci_ops::write is  \na low-level hardware access. The functions can be accessed with disabled  \ninterrupts even on PREEMPT_RT. The pci_lock is a raw_spinlock_t for this  \npurpose.  \n  \nA spinlock_t becomes a sleeping lock on PREEMPT_RT, so it cannot be  \nacquired with disabled interrupts. The vmd_dev::cfg_lock is accessed in  \nthe same context as the pci_lock.  \n  \nMake vmd_dev::cfg_lock a raw_spinlock_t type so it can be used with  \ninterrupts disabled.  \n  \nThis was reported as:  \n  \n  BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48  \n  Call Trace:  \n   rt_spin_lock+0x4e/0x130  \n   vmd_pci_read+0x8d/0x100 [vmd]  \n   pci_user_read_config_byte+0x6f/0xe0  \n   pci_read_config+0xfe/0x290  \n   sysfs_kf_bin_read+0x68/0x90  \n  \n[bigeasy: reword commit message]  \nTested-off-by: Luis Claudio R. Goncalves   \n[kwilczynski: commit log]  \n[bhelgaas: add back report info from  \n] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:26.000000Z"}