CVE-2025-71121 json
parisc: Do not reprogram affinitiy on ASP chip
published 9mo ago modified 4mo ago also EUVD-2026-2495
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
parisc: Do not reprogram affinitiy on ASP chip
The ASP chip is a very old variant of the GSP chip and is used e.g. in HP 730 workstations. When trying to reprogram the affinity it will crash with a HPMC as the relevant registers don't seem to be at the usual location. Let's avoid the crash by checking the sversion. Also note, that reprogramming isn't necessary either, as the HP730 is a just a single-CPU machine.
Patch / fix
- Linux Linux 4.15, 4.20, 5.5, 5.10.248, 5.15.198, 5.17, 5.18, 6.1.160, 6.6.120, 6.12.64, 6.18.3, 6.19
- linux Debian 12 6.1.162-1
- linux Debian 13 6.12.69-1
- linux Debian 14 6.18.3-1
debian advisories DEBIAN-CVE-2025-71121
- linux Ubuntu 22.04 LTS 5.15.0-173.183
- linux Ubuntu 24.04 LTS 6.8.0-110.110
- linux Ubuntu 25.10 6.17.0-22.22
- linux-aws Ubuntu 22.04 LTS 5.15.0-1103.110
- linux-aws Ubuntu 24.04 LTS 6.8.0-1052.55
- linux-aws Ubuntu 25.10 6.17.0-1012.12
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1103.112
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1054.57
ubuntu advisories UBUNTU-CVE-2025-71121
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/845a92b74cf7a730200532ecb4482981cec9d006 commit
- git.kernel.org/stable/c/7a146f34e5be96330467397c9fd9d3d851b2cbbe commit
- git.kernel.org/stable/c/4d0858bbeea12a50bfb32137f74d4b74917ebadd commit
- git.kernel.org/stable/c/e09fd2eb6d4c993ee9eaae556cb51e30ec1042df commit
- git.kernel.org/stable/c/60560d13ff368415c96a0c1247bea16d427c0641 commit
- git.kernel.org/stable/c/c8f810e20f4bbe50b49f73429d9fa6efad00623e commit
- git.kernel.org/stable/c/dca7da244349eef4d78527cafc0bf80816b261f5 commit
Is CVE-2025-71121 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-71121 updated
kernel: parisc: Do not reprogram affinitiy on ASP chip
-
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.15% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 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/845a92b74cf7a730200532ecb4482981cec9d006
patch
-
git.kernel.org
/stable/c/7a146f34e5be96330467397c9fd9d3d851b2cbbe
patch
-
git.kernel.org
/stable/c/4d0858bbeea12a50bfb32137f74d4b74917ebadd
patch
-
git.kernel.org
/stable/c/e09fd2eb6d4c993ee9eaae556cb51e30ec1042df
patch
-
git.kernel.org
/stable/c/60560d13ff368415c96a0c1247bea16d427c0641
patch
-
git.kernel.org
/stable/c/c8f810e20f4bbe50b49f73429d9fa6efad00623e
patch
-
git.kernel.org
/stable/c/dca7da244349eef4d78527cafc0bf80816b261f5
patch
Sources
- CVE List CVE-2025-71121
- NVD CVE-2025-71121
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.