LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71121: parisc: Do not reprogram affinitiy on ASP chip

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects a narrow class of old PA-RISC hardware using the ASP chip, such as HP 730 workstations. Reprogramming interrupt affinity can crash the system with a high-priority machine check. Business impact is mainly availability risk for legacy systems, not broad enterprise exposure.

Executive priority

Treat as low urgency unless the organization still operates legacy PA-RISC Linux systems. For affected environments, prioritize patching because the impact is system availability and recovery effort.

Technical view

The kernel fix avoids affinity reprogramming on ASP-chip PA-RISC systems by checking the system version. The source says ASP registers are not at the usual location and reprogramming is unnecessary because HP 730 is single-CPU. No CVSS, CWE, or exploit details are provided.

Likely exposure

Exposure appears limited to Linux deployments on legacy PA-RISC ASP-chip hardware. Modern x86, ARM, and typical cloud Linux systems are not indicated as affected by the provided sources.

Exploitation context

The bundle does not show CISA KEV listing, public exploitation, or weaponized details. The described failure mode is a crash during affinity reprogramming on specific legacy hardware.

Researcher notes

Evidence is narrow and kernel-specific. The record lacks CVSS, CWE, and trigger detail beyond affinity reprogramming on ASP. Map the referenced stable commits to distribution backports before declaring systems fixed.

Mitigation direction

  • Identify any Linux systems running on PA-RISC ASP-chip hardware.
  • Apply the relevant Linux stable or distribution kernel update containing the referenced fix.
  • Check vendor advisories for exact fixed package versions in your distribution.
  • Avoid affected custom kernels on ASP-chip PA-RISC systems until patched.

Validation and detection

  • Inventory kernel versions and hardware architecture for legacy PA-RISC hosts.
  • Confirm whether any systems use ASP-chip hardware such as HP 730 workstations.
  • Verify deployed kernels include one of the referenced stable fixes or vendor backports.
  • Monitor logs for HPMC crashes during interrupt affinity handling.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71121 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf7c35220305f273bddc0bdaf1e453b4ca280f145, f77f482ec31a1f38eb38079622ca367b4b7d7442, 939fc856676c266c3bc347c1c1661872a3725c0f, 939fc856676c266c3bc347c1c1661872a3725c0f, 939fc856676c266c3bc347c1c1661872a3725c0f, 939fc856676c266c3bc347c1c1661872a3725c0f, 939fc856676c266c3bc347c1c1661872a3725c0f, 52b66c46bb9f5fb270673327c41dec50171939c1, 3940ecfccfffec8385b64551fd73a12c02049437, bab8e3b4f68ac393c42da73d0bce891d281ded55, ff342de194ad311f905ce0b6b73db48db802e224, ef24e0a68b59ea8f59fedf5a9881fd9cf9f27370, 5.10.111, 5.15.34, 4.14.276, 4.19.238, 5.4.189, 5.16.20, 5.17.3unaffected
LinuxLinux5.18, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.