gpio: amd8111: Fix PCI device reference count leak
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.23% (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 4271515f189bd5fe2ec86b4089dab7cb804625d2, 45fecdb9f658d9c82960c98240bc0770ade19aca, 4749c5cc147c9860b96db1e71cc36d1de1bd3f59.
Low priority for now. Upgrade to Linux Linux 4271515f189bd5fe2ec86b4089dab7cb804625d2, 45fecdb9f658d9c82960c98240bc0770ade19aca, 4749c5cc147c9860b96db1e71cc36d1de1bd3f59 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: gpio: amd8111: Fix PCI device reference count leak 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() after the 'out' label. Since pci_dev_put() can handle NULL input parameter, there is no problem for the 'Device not found' branch. For the normal path, add pci_dev_put() in amd_gpio_exit().
- Published
- Oct 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th 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.6 and later · before 4.9.336
- linux linux kernel4.10 and later · before 4.14.302
- linux linux kernel4.15 and later · before 4.19.269
- linux linux kernel4.20 and later · before 5.4.227
- linux linux kernel5.5 and later · before 5.10.159
- linux linux kernel5.11 and later · before 5.15.83
- linux linux kernel5.16 and later · before 6.0.13
- 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.6affected
- f942a7de047d8c599cc1a9a26293c8c7400450ea and later · before 4749c5cc147c9860b96db1e71cc36d1de1bd3f59affected · git
- f942a7de047d8c599cc1a9a26293c8c7400450ea and later · before 71d591ef873f9ebb86cd8d053b3caee785b2de6aaffected · git
- f942a7de047d8c599cc1a9a26293c8c7400450ea and later · before b2bc053ebbba57a06fa655db5ea796de2edce445affected · git
- f942a7de047d8c599cc1a9a26293c8c7400450ea and later · before 48bd5d3801f6b67cc144449d434abbd5043a6d37affected · git
- f942a7de047d8c599cc1a9a26293c8c7400450ea and later · before 5ee6413d3dd972930af787b2c0c7aaeb379fa521affected · git
- f942a7de047d8c599cc1a9a26293c8c7400450ea and later · before 4271515f189bd5fe2ec86b4089dab7cb804625d2affected · git
- f942a7de047d8c599cc1a9a26293c8c7400450ea and later · before e364ce04d8f840478b09eee57b614de7cf1e743eaffected · git
- f942a7de047d8c599cc1a9a26293c8c7400450ea and later · before 45fecdb9f658d9c82960c98240bc0770ade19acaaffected · git
- before 3.6not 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.4-1 | 6.1.4-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
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 4271515f189bd5fe2ec86b4089dab7cb804625d2 | Vendor (CNA) |
| Linux Linux | 45fecdb9f658d9c82960c98240bc0770ade19aca | Vendor (CNA) |
| Linux Linux | 4749c5cc147c9860b96db1e71cc36d1de1bd3f59 | Vendor (CNA) |
| Linux Linux | 48bd5d3801f6b67cc144449d434abbd5043a6d37 | Vendor (CNA) |
| Linux Linux | 5ee6413d3dd972930af787b2c0c7aaeb379fa521 | Vendor (CNA) |
| Linux Linux | 71d591ef873f9ebb86cd8d053b3caee785b2de6a | Vendor (CNA) |
| Linux Linux | b2bc053ebbba57a06fa655db5ea796de2edce445 | Vendor (CNA) |
| Linux Linux | e364ce04d8f840478b09eee57b614de7cf1e743e | Vendor (CNA) |
| debian:linux | 6.1.4-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/45fecdb9f658d9c82960c98240bc0770ade19aca
- git.kernel.org/stable/c/4749c5cc147c9860b96db1e71cc36d1de1bd3f59
- git.kernel.org/stable/c/48bd5d3801f6b67cc144449d434abbd5043a6d37
- git.kernel.org/stable/c/5ee6413d3dd972930af787b2c0c7aaeb379fa521
- git.kernel.org/stable/c/71d591ef873f9ebb86cd8d053b3caee785b2de6a
- git.kernel.org/stable/c/b2bc053ebbba57a06fa655db5ea796de2edce445
- git.kernel.org/stable/c/e364ce04d8f840478b09eee57b614de7cf1e743e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.