CVE-2025-23161: PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 13e5148f70e81991acbe0bab5b1b50ba699116e7, 18056a48669a040bef491e63b25896561ee14d90, 20d0a9062c031068fa39f725a32f182b709b5525; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.
Low priority for now. Upgrade to Linux Linux 13e5148f70e81991acbe0bab5b1b50ba699116e7, 18056a48669a040bef491e63b25896561ee14d90, 20d0a9062c031068fa39f725a32f182b709b5525; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 <lgoncalv@redhat.com> [kwilczynski: commit log] [bhelgaas: add back report info from https://lore.kernel.org/lkml/20241218115951.83062-1-ryotkkr98@gmail.com/]
- Published
- May 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.16 and later · before 6.1.135
- linux linux kernel6.2 and later · before 6.6.88
- linux linux kernelbefore 5.15.181
- linux linux kernel6.13 and later · before 6.13.12
- linux linux kernel6.14 and later · before 6.14.3
- linux linux kernel6.7 and later · before 6.12.24
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.5affected
- 185a383ada2e7794b0e82e040223e741b24d2bf8 and later · before c250262d6485ca333e9821f85b07eb383ec546b1affected · git
- 185a383ada2e7794b0e82e040223e741b24d2bf8 and later · before c2968c812339593ac6e2bdd5cc3adabe3f05fa53affected · git
- 185a383ada2e7794b0e82e040223e741b24d2bf8 and later · before 13e5148f70e81991acbe0bab5b1b50ba699116e7affected · git
- 185a383ada2e7794b0e82e040223e741b24d2bf8 and later · before 5c3cfcf0b4bf43530788b08a8eaf7896ec567484affected · git
- 185a383ada2e7794b0e82e040223e741b24d2bf8 and later · before 2358046ead696ca5c7c628d6c0e2c6792619a3e5affected · git
- 185a383ada2e7794b0e82e040223e741b24d2bf8 and later · before 20d0a9062c031068fa39f725a32f182b709b5525affected · git
- 185a383ada2e7794b0e82e040223e741b24d2bf8 and later · before 18056a48669a040bef491e63b25896561ee14d90affected · git
- before 4.5not affected · semver
- 5.15.181 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.135-1 | 6.1.135-1 |
| Debian:13 | linux | before 6.12.25-1 | 6.12.25-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-23159May 1, 2025 · media: venus: hfi: add a check to handle OOB in sfr region22Monitor
- ← EarlierCVE-2025-23160May 1, 2025 · media: mediatek: vcodec: Fix a resource leak related to the scp device in FW initialization22Monitor
- Later →CVE-2025-23162May 1, 2025 · drm/xe/vf: Don't try to trigger a full GT reset if VF22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 13e5148f70e81991acbe0bab5b1b50ba699116e7 | Vendor (CNA) |
| Linux Linux | 18056a48669a040bef491e63b25896561ee14d90 | Vendor (CNA) |
| Linux Linux | 20d0a9062c031068fa39f725a32f182b709b5525 | Vendor (CNA) |
| Linux Linux | 2358046ead696ca5c7c628d6c0e2c6792619a3e5 | Vendor (CNA) |
| Linux Linux | 5c3cfcf0b4bf43530788b08a8eaf7896ec567484 | Vendor (CNA) |
| Linux Linux | c250262d6485ca333e9821f85b07eb383ec546b1 | Vendor (CNA) |
| Linux Linux | c2968c812339593ac6e2bdd5cc3adabe3f05fa53 | Vendor (CNA) |
| azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.135-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/18056a48669a040bef491e63b25896561ee14d90
- git.kernel.org/stable/c/20d0a9062c031068fa39f725a32f182b709b5525
- git.kernel.org/stable/c/2358046ead696ca5c7c628d6c0e2c6792619a3e5
- git.kernel.org/stable/c/5c3cfcf0b4bf43530788b08a8eaf7896ec567484
- git.kernel.org/stable/c/c250262d6485ca333e9821f85b07eb383ec546b1
- git.kernel.org/stable/c/c2968c812339593ac6e2bdd5cc3adabe3f05fa53
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.