iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init()
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.24% (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 2a8f7b90681472948de172dbbf5a54cd342870aa, 4bedbbd782ebbe7287231fea862c158d4f08a9e3, 71c4a621985fc051ab86d3a86c749069a993fcb2.
Low priority for now. Upgrade to Linux Linux 2a8f7b90681472948de172dbbf5a54cd342870aa, 4bedbbd782ebbe7287231fea862c158d4f08a9e3, 71c4a621985fc051ab86d3a86c749069a993fcb2 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: iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. Add the missing pci_dev_put() for the error path to avoid reference count leak.
- Published
- Oct 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- —
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.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.15 and later · before 4.9.335
- linux linux kernel4.10 and later · before 4.14.301
- linux linux kernel4.15 and later · before 4.19.268
- linux linux kernel4.20 and later · before 5.4.226
- linux linux kernel5.5 and later · before 5.10.158
- linux linux kernel5.11 and later · before 5.15.82
- linux linux kernel5.16 and later · before 6.0.12
- linux linux kernel6.1
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
- 3.15affected
- 2e45528930388658603ea24d49cf52867b928d3e and later · before d47bc9d7bcdbb9adc9703513d964b514fee5b0bfaffected · git
- 2e45528930388658603ea24d49cf52867b928d3e and later · before 71c4a621985fc051ab86d3a86c749069a993fcb2affected · git
- 2e45528930388658603ea24d49cf52867b928d3e and later · before 876d7bfb89273997056220029ff12b1c2cc4691daffected · git
- 2e45528930388658603ea24d49cf52867b928d3e and later · before cbdd83bd2fd67142b03ce9dbdd1eab322ff7321faffected · git
- 2e45528930388658603ea24d49cf52867b928d3e and later · before a5c65cd56aed027f8a97fda8b691caaeb66d115eaffected · git
- 2e45528930388658603ea24d49cf52867b928d3e and later · before bdb613ef179ad4bb9d56a2533e9b30e434f1dfb7affected · git
- 2e45528930388658603ea24d49cf52867b928d3e and later · before 2a8f7b90681472948de172dbbf5a54cd342870aaaffected · git
- 2e45528930388658603ea24d49cf52867b928d3e and later · before 4bedbbd782ebbe7287231fea862c158d4f08a9e3affected · git
- before 3.15not 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.0.12-1 | 6.0.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49000Oct 21, 2024 · iommu/vt-d: Fix PCI device refcount leak in has_external_pci()22Monitor
- ← EarlierCVE-2022-49001Oct 21, 2024 · riscv: fix race when vmap stack overflow28Monitor
- Later →CVE-2022-49003Oct 21, 2024 · nvme: fix SRCU protection of nvme_ns_head list18Monitor
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 | 2a8f7b90681472948de172dbbf5a54cd342870aa | Vendor (CNA) |
| Linux Linux | 4bedbbd782ebbe7287231fea862c158d4f08a9e3 | Vendor (CNA) |
| Linux Linux | 71c4a621985fc051ab86d3a86c749069a993fcb2 | Vendor (CNA) |
| Linux Linux | 876d7bfb89273997056220029ff12b1c2cc4691d | Vendor (CNA) |
| Linux Linux | a5c65cd56aed027f8a97fda8b691caaeb66d115e | Vendor (CNA) |
| Linux Linux | bdb613ef179ad4bb9d56a2533e9b30e434f1dfb7 | Vendor (CNA) |
| Linux Linux | cbdd83bd2fd67142b03ce9dbdd1eab322ff7321f | Vendor (CNA) |
| Linux Linux | d47bc9d7bcdbb9adc9703513d964b514fee5b0bf | Vendor (CNA) |
| debian:linux | 6.0.12-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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)
—
CVSS 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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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/4bedbbd782ebbe7287231fea862c158d4f08a9e3
- git.kernel.org/stable/c/71c4a621985fc051ab86d3a86c749069a993fcb2
- git.kernel.org/stable/c/876d7bfb89273997056220029ff12b1c2cc4691d
- git.kernel.org/stable/c/a5c65cd56aed027f8a97fda8b691caaeb66d115e
- git.kernel.org/stable/c/bdb613ef179ad4bb9d56a2533e9b30e434f1dfb7
- git.kernel.org/stable/c/cbdd83bd2fd67142b03ce9dbdd1eab322ff7321f
- git.kernel.org/stable/c/d47bc9d7bcdbb9adc9703513d964b514fee5b0bf
Vendor advisories and official records. Exploit/PoC links are deliberately left out.