Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-71121, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected f7c35220305f273bddc0bdaf1e453b4ca280f145 – < 845a92b74cf7a730200532ecb4482981cec9d006
    • affected f77f482ec31a1f38eb38079622ca367b4b7d7442 – < 7a146f34e5be96330467397c9fd9d3d851b2cbbe
    • affected 939fc856676c266c3bc347c1c1661872a3725c0f – < 4d0858bbeea12a50bfb32137f74d4b74917ebadd
    • affected 939fc856676c266c3bc347c1c1661872a3725c0f – < e09fd2eb6d4c993ee9eaae556cb51e30ec1042df
    • affected 939fc856676c266c3bc347c1c1661872a3725c0f – < 60560d13ff368415c96a0c1247bea16d427c0641
    • affected 939fc856676c266c3bc347c1c1661872a3725c0f – < c8f810e20f4bbe50b49f73429d9fa6efad00623e
    • affected 939fc856676c266c3bc347c1c1661872a3725c0f – < dca7da244349eef4d78527cafc0bf80816b261f5
    • affected 52b66c46bb9f5fb270673327c41dec50171939c1
    • affected 3940ecfccfffec8385b64551fd73a12c02049437
    • affected bab8e3b4f68ac393c42da73d0bce891d281ded55
    • affected ff342de194ad311f905ce0b6b73db48db802e224
    • affected ef24e0a68b59ea8f59fedf5a9881fd9cf9f27370
    • affected 5.10.111 – < 5.10.248
    • affected 5.15.34 – < 5.15.198
    • affected 4.14.276 – < 4.15
    • affected 4.19.238 – < 4.20
    • affected 5.4.189 – < 5.5
    • affected 5.16.20 – < 5.17
    • affected 5.17.3 – < 5.18
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.64 – ≤ 6.12.*
    • unaffected 6.18.3 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-71121 badge
[![CVE-2025-71121](https://cveledger.app/badge/CVE-2025-71121.svg)](https://cveledger.app/cve/CVE-2025-71121)

Record last updated .