CVE-2022-49462: drm/msm/a6xx: Fix refcount leak in a6xx_gpu_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.26% (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 06907a374f1b74f8f2fb30720dc6df81331e4fb5, 48e82ce8cdb19c20a5020fa446b286d6a147450c, 65ddbc0d26824e2a5d6154d01d8cf39344900213.
Low priority for now. Upgrade to Linux Linux 06907a374f1b74f8f2fb30720dc6df81331e4fb5, 48e82ce8cdb19c20a5020fa446b286d6a147450c, 65ddbc0d26824e2a5d6154d01d8cf39344900213 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: drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. a6xx_gmu_init() passes the node to of_find_device_by_node() and of_dma_configure(), of_find_device_by_node() will takes its reference, of_dma_configure() doesn't need the node after usage. Add missing of_node_put() to avoid refcount leak.
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 19th 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 kernel4.19 and later · before 5.4.198
- linux linux kernel5.5 and later · before 5.10.121
- linux linux kernel5.11 and later · before 5.15.46
- linux linux kernel5.16 and later · before 5.17.14
- linux linux kernel5.18 and later · before 5.18.3
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.19affected
- 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and later · before 6832e36f156ea35a6ed74bca72727806116effddaffected · git
- 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and later · before 48e82ce8cdb19c20a5020fa446b286d6a147450caffected · git
- 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and later · before edff4c1af831d0c02e654eed9da7d74174de49d5affected · git
- 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and later · before 65ddbc0d26824e2a5d6154d01d8cf39344900213affected · git
- 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and later · before 06907a374f1b74f8f2fb30720dc6df81331e4fb5affected · git
- 4b565ca5a2cbbbb6345e8789da89c193b6b00e5a and later · before c56de483093d7ad0782327f95dda7da97bc4c315affected · git
- before 4.19not affected · semver
- 5.4.198 and later · up to and including 5.4.*not affected · semver
- 5.10.121 and later · up to and including 5.10.*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 5.18.5-1 | 5.18.5-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-2022-49460Feb 26, 2025 · PM / devfreq: rk3399_dmc: Disable edev on remove()22Monitor
- ← EarlierCVE-2022-49461Feb 26, 2025 · amt: fix memory leak for advertisement message22Monitor
- Later →CVE-2022-49463Feb 26, 2025 · thermal/drivers/imx_sc_thermal: Fix refcount leak in imx_sc_thermal_probe22Monitor
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 | 06907a374f1b74f8f2fb30720dc6df81331e4fb5 | Vendor (CNA) |
| Linux Linux | 48e82ce8cdb19c20a5020fa446b286d6a147450c | Vendor (CNA) |
| Linux Linux | 65ddbc0d26824e2a5d6154d01d8cf39344900213 | Vendor (CNA) |
| Linux Linux | 6832e36f156ea35a6ed74bca72727806116effdd | Vendor (CNA) |
| Linux Linux | c56de483093d7ad0782327f95dda7da97bc4c315 | Vendor (CNA) |
| Linux Linux | edff4c1af831d0c02e654eed9da7d74174de49d5 | Vendor (CNA) |
| debian:linux | 5.18.5-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)
—
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 (5 more)Show less
- git.kernel.org/stable/c/48e82ce8cdb19c20a5020fa446b286d6a147450c
- git.kernel.org/stable/c/65ddbc0d26824e2a5d6154d01d8cf39344900213
- git.kernel.org/stable/c/6832e36f156ea35a6ed74bca72727806116effdd
- git.kernel.org/stable/c/c56de483093d7ad0782327f95dda7da97bc4c315
- git.kernel.org/stable/c/edff4c1af831d0c02e654eed9da7d74174de49d5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.