CVE-2025-38435 (GCVE-0-2025-38435)

Vulnerability from cvelistv5 – Published: 2025-07-25 14:32 – Updated: 2026-08-05 12:01
VLAI
Title
riscv: vector: Fix context save/restore with xtheadvector
Summary
In the Linux kernel, the following vulnerability has been resolved: riscv: vector: Fix context save/restore with xtheadvector Previously only v0-v7 were correctly saved/restored, and the context of v8-v31 are damanged. Correctly save/restore v8-v31 to avoid breaking userspace.
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: d863910eabaffc68eb28aaf476dd870fc3f7197d , < dd5ceea8d50e9e108a10d1e0d89fa2c9ff442ca2 (git)
Affected: d863910eabaffc68eb28aaf476dd870fc3f7197d , < 4262bd0d9cc704ea1365ac00afc1272400c2cbef (git)
Create a notification for this product.
Linux Linux Affected: 6.14
Unaffected: 0 , < 6.14 (semver)
Unaffected: 6.15.5 , ≤ 6.15.* (semver)
Unaffected: 6.16 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/riscv/include/asm/vector.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "dd5ceea8d50e9e108a10d1e0d89fa2c9ff442ca2",
              "status": "affected",
              "version": "d863910eabaffc68eb28aaf476dd870fc3f7197d",
              "versionType": "git"
            },
            {
              "lessThan": "4262bd0d9cc704ea1365ac00afc1272400c2cbef",
              "status": "affected",
              "version": "d863910eabaffc68eb28aaf476dd870fc3f7197d",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/riscv/include/asm/vector.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.14"
            },
            {
              "lessThan": "6.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.15.*",
              "status": "unaffected",
              "version": "6.15.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.16",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.15.5",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.16",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: vector: Fix context save/restore with xtheadvector\n\nPreviously only v0-v7 were correctly saved/restored,\nand the context of v8-v31 are damanged.\nCorrectly save/restore v8-v31 to avoid breaking userspace."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - Exploitation requires executing instructions on the affected hart to read and plant vector register values across a context switch; there is no remote or network-reachable path to the vector save/restore code.\nAC:L - On T-Head xtheadvector hardware the omission of v8-v31 from restore is unconditional and deterministic, so the attacker simply spins reading v8-v31 after each scheduling event; no race, memory layout, or uncontrolled state is involved, and the enabling config is default-y.\nPR:L - Any unprivileged local task can use vector (CONFIG_RISCV_ISA_V_DEFAULT_ENABLE=y, and riscv_v_vstate_ctrl_set_current() unconditionally allows PR_RISCV_V_VSTATE_CTRL_ON), so only a basic user account is needed.\nUI:N - The leak and corruption occur automatically on every context switch and signal return; no victim action beyond normal execution is required.\nS:U - The vulnerable code and the impacted processes are all governed by the same kernel security authority; no VM, IOMMU, or sandbox boundary is crossed, and guest vector is never enabled on xtheadvector hosts.\nC:H - v8-v31 are never restored, so an attacker task inherits 24 registers of another process\u0027s live vector state and can sample this continuously across context switches, harvesting arbitrary secret data that transits vectorized memcpy/string/crypto routines in privileged processes.\nI:H - The attacker can leave arbitrary chosen values in v8-v31 that a victim process then computes with, and for indexed/gather vector loads and stores those attacker-controlled values become addresses inside the victim, giving attacker-directed corruption of another process\u0027s data.\nA:H - Every vector-using process on the machine is deterministically resumed with damaged v8-v31, and an attacker can deliberately poison those registers so victims fault on indexed vector accesses, reliably crashing arbitrary processes including system daemons."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:01:52.506Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/dd5ceea8d50e9e108a10d1e0d89fa2c9ff442ca2"
        },
        {
          "url": "https://git.kernel.org/stable/c/4262bd0d9cc704ea1365ac00afc1272400c2cbef"
        }
      ],
      "title": "riscv: vector: Fix context save/restore with xtheadvector",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-38435",
    "datePublished": "2025-07-25T14:32:09.136Z",
    "dateReserved": "2025-04-16T04:51:24.016Z",
    "dateUpdated": "2026-08-05T12:01:52.506Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-38435",
      "date": "2026-11-19",
      "epss": "0.0017",
      "percentile": "0.06433"
    },
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-11-09T18:28:41+00:00",
      "cve": "CVE-2025-38435",
      "id": "CVE-2025-38435",
      "initial_release_date": "2025-07-25T00:00:00+00:00",
      "product_status:known_not_affected": "200",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: riscv: vector: Fix context save/restore with xtheadvector",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-38435.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.