CVE-2022-50522 json
mcb: mcb-parse: fix error handing in chameleon_parse_gdd()
published 2025-10-07 13 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-32046
- cvss
- 3.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
mcb: mcb-parse: fix error handing in chameleon_parse_gdd()
If mcb_device_register() returns error in chameleon_parse_gdd(), the refcount of bus and device name are leaked. Fix this by calling put_device() to give up the reference, so they can be released in mcb_release_dev() and kobject_cleanup().
Patch / fix
- Linux Linux 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2
- linux Debian 14, Debian 13, Debian 12 6.1.4-1
debian advisories DEBIAN-CVE-2022-50522
- linux Ubuntu 18.04 LTS 4.15.0-208.220
- linux Ubuntu 20.04 LTS 5.4.0-144.161
- linux Ubuntu 22.04 LTS 5.15.0-69.76
- linux-aws Ubuntu 18.04 LTS 4.15.0-1153.166
- linux-aws Ubuntu 20.04 LTS 5.4.0-1097.105
- linux-aws Ubuntu 22.04 LTS 5.15.0-1033.37
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1101.110
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1031.38
ubuntu advisories UBUNTU-CVE-2022-50522
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/891f606ae0765bc9ca99f5276735be4d338f0255 commit
- git.kernel.org/stable/c/cf6e70c0ced50b52415ac0c88eba1fb09c500a5a commit
- git.kernel.org/stable/c/fd85ece416fd7edb945203e59d4cd94952f77e7c commit
- git.kernel.org/stable/c/110dc34c9fa33d37f55b394b1199ea6c0ad1ee84 commit
- git.kernel.org/stable/c/7b289b791a59386dc23a00d3cf17a0db984b40d3 commit
- git.kernel.org/stable/c/43bfc7c2402a22d3b4eb08c040f274ba2b76461a commit
- git.kernel.org/stable/c/b948baa29394ec5f4e6ec28486e7d06a76caee91 commit
- git.kernel.org/stable/c/4a9f1a8b3af287581ffb690d0e1593c681729ddb commit
- git.kernel.org/stable/c/728ac3389296caf68638628c987aeae6c8851e2d 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-50522 updated
kernel: mcb: mcb-parse: fix error handing in chameleon_parse_gdd()
-
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
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/891f606ae0765bc9ca99f5276735be4d338f0255
patch
-
git.kernel.org
/stable/c/cf6e70c0ced50b52415ac0c88eba1fb09c500a5a
patch
-
git.kernel.org
/stable/c/fd85ece416fd7edb945203e59d4cd94952f77e7c
patch
-
git.kernel.org
/stable/c/110dc34c9fa33d37f55b394b1199ea6c0ad1ee84
patch
-
git.kernel.org
/stable/c/7b289b791a59386dc23a00d3cf17a0db984b40d3
patch
-
git.kernel.org
/stable/c/43bfc7c2402a22d3b4eb08c040f274ba2b76461a
patch
-
git.kernel.org
/stable/c/b948baa29394ec5f4e6ec28486e7d06a76caee91
patch
-
git.kernel.org
/stable/c/4a9f1a8b3af287581ffb690d0e1593c681729ddb
patch
-
git.kernel.org
/stable/c/728ac3389296caf68638628c987aeae6c8851e2d
patch
Sources
- CVE List CVE-2022-50522
- NVD CVE-2022-50522
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.