CVE-2025-22054 json
arcnet: Add NULL check in com20020pci_probe()
published last yr. modified 4mo ago also EUVD-2025-11243
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
arcnet: Add NULL check in com20020pci_probe()
devm_kasprintf() returns NULL when memory allocation fails. Currently, com20020pci_probe() does not check for this case, which results in a NULL pointer dereference.
Add NULL check after devm_kasprintf() to prevent this issue and ensure no resources are left allocated.
Patch / fix
- Linux Linux 4.20, 5.4.292, 5.10.236, 5.15.180, 6.1.134, 6.6.87, 6.12.23, 6.13.11, 6.14.2, 6.15
- linux Debian 12 6.1.135-1
- linux Debian 14, Debian 13 6.12.25-1
debian advisories DEBIAN-CVE-2025-22054
- linux Ubuntu 22.04 LTS 5.15.0-142.152
- linux Ubuntu 24.04 LTS 6.8.0-86.87
- linux-aws Ubuntu 22.04 LTS 5.15.0-1086.93
- linux-aws Ubuntu 24.04 LTS 6.8.0-1041.43
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1085.94
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1042.45
- linux-gke Ubuntu 22.04 LTS 5.15.0-1083.89
- linux-gke Ubuntu 24.04 LTS 6.8.0-1038.43
ubuntu advisories UBUNTU-CVE-2025-22054
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/661cf5d102949898c931e81fd4e1c773afcdeafa commit
- git.kernel.org/stable/c/905a34dc1ad9a53a8aaaf8a759ea5dbaaa30418d commit
- git.kernel.org/stable/c/ef8b29398ea6061ac8257f3e45c9be45cc004ce2 commit
- git.kernel.org/stable/c/be8a0decd0b59a52a07276f9ef3b33ef820b2179 commit
- git.kernel.org/stable/c/ececf8eff6c25acc239fa8f0fd837c76bc770547 commit
- git.kernel.org/stable/c/ebebeb58d48e25525fa654f2c53a24713fe141c3 commit
- git.kernel.org/stable/c/a654f31b33515d39bb56c75fd8b26bef025ced7e commit
- git.kernel.org/stable/c/887226163504494ea7e58033a97c2d2ab12e05d4 commit
- git.kernel.org/stable/c/fda8c491db2a90ff3e6fbbae58e495b4ddddeca3 commit
Is CVE-2025-22054 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-22054 updated cvss 5.5
kernel: arcnet: Add NULL check in com20020pci_probe()
-
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
- last yr.
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-09).
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/661cf5d102949898c931e81fd4e1c773afcdeafa
patch
-
git.kernel.org
/stable/c/905a34dc1ad9a53a8aaaf8a759ea5dbaaa30418d
patch
-
git.kernel.org
/stable/c/ef8b29398ea6061ac8257f3e45c9be45cc004ce2
patch
-
git.kernel.org
/stable/c/be8a0decd0b59a52a07276f9ef3b33ef820b2179
patch
-
git.kernel.org
/stable/c/ececf8eff6c25acc239fa8f0fd837c76bc770547
patch
-
git.kernel.org
/stable/c/ebebeb58d48e25525fa654f2c53a24713fe141c3
patch
-
git.kernel.org
/stable/c/a654f31b33515d39bb56c75fd8b26bef025ced7e
patch
-
git.kernel.org
/stable/c/887226163504494ea7e58033a97c2d2ab12e05d4
patch
-
git.kernel.org
/stable/c/fda8c491db2a90ff3e6fbbae58e495b4ddddeca3
patch
- lists.debian.org /debian-lts-announce/2025/05/msg00045.html
- lists.debian.org /debian-lts-announce/2025/05/msg00030.html
Sources
- CVE List CVE-2025-22054
- NVD CVE-2025-22054
Fencer Intel 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.