CVE-2022-49608 json
pinctrl: ralink: Check for null return of devm_kcalloc
published 2025-02-26 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2022-54624
- 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 19%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
pinctrl: ralink: Check for null return of devm_kcalloc
Because of the possible failure of the allocation, data->domains might be NULL pointer and will cause the dereference of the NULL pointer later. Therefore, it might be better to check it and directly return -ENOMEM without releasing data manually if fails, because the comment of the devm_kmalloc() says "Memory allocated with this function is automatically freed on driver detach.".
Patch / fix
- Linux Linux 4.19.254, 5.4.208, 5.10.134, 5.15.58, 5.18.15, 5.19
- linux Debian 14, Debian 13, Debian 12 5.18.16-1
debian advisories DEBIAN-CVE-2022-49608
- linux Ubuntu 20.04 LTS 5.4.0-128.144
- linux Ubuntu 22.04 LTS 5.15.0-50.56
- linux-aws Ubuntu 20.04 LTS 5.4.0-1086.93
- linux-aws Ubuntu 22.04 LTS 5.15.0-1021.25
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1090.98
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1019.25
- linux-gke Ubuntu 22.04 LTS 5.15.0-1017.20
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1034.38
ubuntu advisories UBUNTU-CVE-2022-49608
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/13596e6c9e541e90e5fc2c52b23f08b951370da9 commit
- git.kernel.org/stable/c/6194c021496addc11763d1ffa89ce5751889fe3c commit
- git.kernel.org/stable/c/5694b162f275fb9a9f89422701b2b963be11e496 commit
- git.kernel.org/stable/c/44016a85419ca0d4f1e4d0127b330f8e4e2a57d0 commit
- git.kernel.org/stable/c/5595d30c4dc27d939635c3188c68203b6ece1711 commit
- git.kernel.org/stable/c/c3b821e8e406d5650e587b7ac624ac24e9b780a8 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-49608 updated cvss 5.5
kernel: pinctrl: ralink: Check for null return of devm_kcalloc
-
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.27% chance of exploitation in the next 30 days, higher than 19% 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
- Weakness
-
- CWE-476 NULL Pointer Dereference
- Technology feeds
References
-
git.kernel.org
/stable/c/13596e6c9e541e90e5fc2c52b23f08b951370da9
patch
-
git.kernel.org
/stable/c/6194c021496addc11763d1ffa89ce5751889fe3c
patch
-
git.kernel.org
/stable/c/5694b162f275fb9a9f89422701b2b963be11e496
patch
-
git.kernel.org
/stable/c/44016a85419ca0d4f1e4d0127b330f8e4e2a57d0
patch
-
git.kernel.org
/stable/c/5595d30c4dc27d939635c3188c68203b6ece1711
patch
-
git.kernel.org
/stable/c/c3b821e8e406d5650e587b7ac624ac24e9b780a8
patch
Sources
- CVE List CVE-2022-49608
- NVD CVE-2022-49608
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.