PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type
In the Linux kernel, the following vulnerability has been resolved: PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type 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. 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. Make vmd_dev::cfg_lock a raw_spinlock_t type so it can be used with interrupts disabled. This was reported as: 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 [bigeasy: reword commit message] Tested-off-by: Luis Claudio R. Goncalves [kwilczynski: commit log] [bhelgaas: add back report info from https://lore.kernel.org/lkml/20241218115951.83062-1-ryotkkr98@gmail.com/]
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.15.181, 6.1.135, 6.12.24, 6.13.12, 6.14.3, 6.6.88
- CVEs
- CVE-2025-23161
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 08:45 UTC · Revision 1
Source evidence
PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type
core-osv · Original sourcePublished 1 May 2025, 12:55 UTC
In the Linux kernel, the following vulnerability has been resolved: PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type 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. 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. Make vmd_dev::cfg_lock a raw_spinlock_t type so it can be used with interrupts disabled. This was reported as: 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 [bigeasy: reword commit message] Tested-off-by: Luis Claudio R. Goncalves [kwilczynski: commit log] [bhelgaas: add back report info from https://lore.kernel.org/lkml/20241218115951.83062-1-ryotkkr98@gmail.com/]
osv:CVE-2025-23161
Kernel
Fixed versions: 5.15.181, 6.1.135, 6.6.88, 6.12.24, 6.13.12, 6.14.3
Complete source record
{
"id": "004586fb05898c5a417f38d354fb45302f7261690ce4f8426410b6c9fcd58812",
"url": "https://osv.dev/vulnerability/CVE-2025-23161",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type",
"summary": "In the Linux kernel, the following vulnerability has been resolved: PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type 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. 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. Make vmd_dev::cfg_lock a raw_spinlock_t type so it can be used with interrupts disabled. This was reported as: 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 [bigeasy: reword commit message] Tested-off-by: Luis Claudio R. Goncalves [kwilczynski: commit log] [bhelgaas: add back report info from https://lore.kernel.org/lkml/20241218115951.83062-1-ryotkkr98@gmail.com/]",
"evidence": "osv:CVE-2025-23161",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.15.181",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.135",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.88",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.24",
"evidence": "/affected/1/ranges"
},
{
"value": "6.13.12",
"evidence": "/affected/1/ranges"
},
{
"value": "6.14.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-23161",
"aliases": [
"CVE-2025-23161"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "185a383ada2e7794b0e82e040223e741b24d2bf8"
},
{
"fixed": "c250262d6485ca333e9821f85b07eb383ec546b1"
},
{
"fixed": "c2968c812339593ac6e2bdd5cc3adabe3f05fa53"
},
{
"fixed": "13e5148f70e81991acbe0bab5b1b50ba699116e7"
},
{
"fixed": "5c3cfcf0b4bf43530788b08a8eaf7896ec567484"
},
{
"fixed": "2358046ead696ca5c7c628d6c0e2c6792619a3e5"
},
{
"fixed": "20d0a9062c031068fa39f725a32f182b709b5525"
},
{
"fixed": "18056a48669a040bef491e63b25896561ee14d90"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-23161.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.5.0"
},
{
"fixed": "5.15.181"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.135"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.88"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.24"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.13.12"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.14.0"
},
{
"fixed": "6.14.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-23161.json"
}
}
],
"modified": "2026-10-28T02:30:34.088245423Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/13e5148f70e81991acbe0bab5b1b50ba699116e7",
"https://git.kernel.org/stable/c/18056a48669a040bef491e63b25896561ee14d90",
"https://git.kernel.org/stable/c/20d0a9062c031068fa39f725a32f182b709b5525",
"https://git.kernel.org/stable/c/2358046ead696ca5c7c628d6c0e2c6792619a3e5",
"https://git.kernel.org/stable/c/5c3cfcf0b4bf43530788b08a8eaf7896ec567484",
"https://git.kernel.org/stable/c/c250262d6485ca333e9821f85b07eb383ec546b1",
"https://git.kernel.org/stable/c/c2968c812339593ac6e2bdd5cc3adabe3f05fa53",
"https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/23xxx/CVE-2025-23161.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-23161",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/23xxx/CVE-2025-23161.json"
}
},
"related_cves": [
{
"value": "CVE-2025-23161",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 501227,
"published_at": "2025-05-01T12:55:46.021+00:00"
}