CVE-2022-49439 json
powerpc/fsl_rio: Fix refcount leak in fsl_rio_setup
published 2025-02-26 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2022-54790
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 18%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
powerpc/fsl_rio: Fix refcount leak in fsl_rio_setup
of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.
Patch / fix
- Linux Linux 4.14.283, 4.19.247, 5.4.198, 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19
- linux Debian 14, Debian 13, Debian 12 5.18.5-1
debian advisories DEBIAN-CVE-2022-49439
- linux Ubuntu 18.04 LTS 4.15.0-192.203
- linux Ubuntu 20.04 LTS 5.4.0-126.142
- linux Ubuntu 22.04 LTS 5.15.0-47.51
- linux-aws Ubuntu 18.04 LTS 4.15.0-1140.151
- linux-aws Ubuntu 20.04 LTS 5.4.0-1085.92
- linux-aws Ubuntu 22.04 LTS 5.15.0-1019.23
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1089.97
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1017.23
ubuntu advisories UBUNTU-CVE-2022-49439
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/51e25fbf20c9152d84a34b7afac15a41fe5c9116 commit
- git.kernel.org/stable/c/5b8aa2ba38c010f47c965dd9bb5a8561813ed649 commit
- git.kernel.org/stable/c/bcb6c4c5eb4836a21411dfe8247bf9951eb6e7c3 commit
- git.kernel.org/stable/c/46fd994763cf6884b88a2da712af918f3ed54d7b commit
- git.kernel.org/stable/c/7b668a59ddfb32727e39b06fdf52b28e58c684e0 commit
- git.kernel.org/stable/c/c70dd353d37158e06bf8d450d4b31a7091609924 commit
- git.kernel.org/stable/c/5607a77a365df8c0fd5ff43ac424812b95775527 commit
- git.kernel.org/stable/c/fcee96924ba1596ca80a6770b2567ca546f9a482 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-49439 updated cvss 5.5
kernel: powerpc/fsl_rio: Fix refcount leak in fsl_rio_setup
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 13 mo ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/51e25fbf20c9152d84a34b7afac15a41fe5c9116
patch
-
git.kernel.org
/stable/c/5b8aa2ba38c010f47c965dd9bb5a8561813ed649
patch
-
git.kernel.org
/stable/c/bcb6c4c5eb4836a21411dfe8247bf9951eb6e7c3
patch
-
git.kernel.org
/stable/c/46fd994763cf6884b88a2da712af918f3ed54d7b
patch
-
git.kernel.org
/stable/c/7b668a59ddfb32727e39b06fdf52b28e58c684e0
patch
-
git.kernel.org
/stable/c/c70dd353d37158e06bf8d450d4b31a7091609924
patch
-
git.kernel.org
/stable/c/5607a77a365df8c0fd5ff43ac424812b95775527
patch
-
git.kernel.org
/stable/c/fcee96924ba1596ca80a6770b2567ca546f9a482
patch
Sources
- CVE List CVE-2022-49439
- NVD CVE-2022-49439
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.