CVE-2025-40117 (GCVE-0-2025-40117)

Vulnerability from cvelistv5 – Published: 2025-11-12 10:23 – Updated: 2026-08-05 12:07
VLAI
Title
misc: pci_endpoint_test: Fix array underflow in pci_endpoint_test_ioctl()
Summary
In the Linux kernel, the following vulnerability has been resolved: misc: pci_endpoint_test: Fix array underflow in pci_endpoint_test_ioctl() Commit eefb83790a0d ("misc: pci_endpoint_test: Add doorbell test case") added NO_BAR (-1) to the pci_barno enum which, in practical terms, changes the enum from an unsigned int to a signed int. If the user passes a negative number in pci_endpoint_test_ioctl() then it results in an array underflow in pci_endpoint_test_bar().
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: eefb83790a0dda112d1755e4f5e213738d717e76 , < 6df3687922570f753574c40b35e83b26b32292d0 (git)
Affected: eefb83790a0dda112d1755e4f5e213738d717e76 , < 1ad82f9db13d85667366044acdfb02009d576c5a (git)
Create a notification for this product.
Linux Linux Affected: 6.17
Unaffected: 0 , < 6.17 (semver)
Unaffected: 6.17.3 , ≤ 6.17.* (semver)
Unaffected: 6.18 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/misc/pci_endpoint_test.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "6df3687922570f753574c40b35e83b26b32292d0",
              "status": "affected",
              "version": "eefb83790a0dda112d1755e4f5e213738d717e76",
              "versionType": "git"
            },
            {
              "lessThan": "1ad82f9db13d85667366044acdfb02009d576c5a",
              "status": "affected",
              "version": "eefb83790a0dda112d1755e4f5e213738d717e76",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/misc/pci_endpoint_test.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.17"
            },
            {
              "lessThan": "6.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.17.*",
              "status": "unaffected",
              "version": "6.17.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.18",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.17.3",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmisc: pci_endpoint_test: Fix array underflow in pci_endpoint_test_ioctl()\n\nCommit eefb83790a0d (\"misc: pci_endpoint_test: Add doorbell test case\")\nadded NO_BAR (-1) to the pci_barno enum which, in practical terms,\nchanges the enum from an unsigned int to a signed int.  If the user\npasses a negative number in pci_endpoint_test_ioctl() then it results in\nan array underflow in pci_endpoint_test_bar()."
        }
      ],
      "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 - The vulnerability is triggered by a PCITEST_BAR ioctl on the local misc device /dev/pci-endpoint-test.N, requiring local system access rather than any network or physical interaction.\nAC:L - A single ioctl with any negative argument deterministically defeats the signed `bar \u003e BAR_5` check; there is no race, no timing window, and no dependence on state outside the attacker\u0027s control.\nPR:L - The driver performs no capability check at all \u2014 no CAP_SYS_ADMIN, no .open hook, nothing \u2014 so any local user holding a descriptor to the test device node can trigger it, and on the PCI-endpoint test rigs where this driver is deployed the node is commonly exposed to the non-root test-automation account.\nUI:N - The attacker performs the entire attack via its own ioctl call; no victim action or cooperation is needed.\nS:U - The out-of-bounds accesses corrupt kernel memory and MMIO mappings within the same kernel security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The attacker-controlled negative index produces out-of-bounds reads of `pdev-\u003eresource[]`, of `struct pci_endpoint_test`, of `.rodata`, and a `memcpy_fromio()` of up to 1 MB from an OOB-derived pointer, and the resulting memory-corruption primitive can be leveraged for arbitrary kernel memory disclosure.\nI:H - `memcpy_toio(test-\u003ebar[barno] + offset, ...)` writes megabytes of pattern data to a destination pointer read from out-of-bounds memory at an attacker-chosen index, clobbering kernel heap objects (including `struct pci_dev`) or adjacent device MMIO registers \u2014 an arbitrary-write primitive exploitable for control-flow hijacking.\nA:H - The loop bound comes from a garbage `bar_size` read out of bounds, so the write runs far past any valid mapping and reliably faults, and the heap corruption itself guarantees a kernel oops or panic."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:07:53.958Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/6df3687922570f753574c40b35e83b26b32292d0"
        },
        {
          "url": "https://git.kernel.org/stable/c/1ad82f9db13d85667366044acdfb02009d576c5a"
        }
      ],
      "title": "misc: pci_endpoint_test: Fix array underflow in pci_endpoint_test_ioctl()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-40117",
    "datePublished": "2025-11-12T10:23:17.851Z",
    "dateReserved": "2025-04-16T07:20:57.168Z",
    "dateUpdated": "2026-08-05T12:07:53.958Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-40117",
      "date": "2026-11-19",
      "epss": "0.00153",
      "percentile": "0.04546"
    },
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-11-09T18:19:51+00:00",
      "cve": "CVE-2025-40117",
      "id": "CVE-2025-40117",
      "initial_release_date": "2025-11-12T00:00:00+00:00",
      "product_status:known_not_affected": "200",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: misc: pci_endpoint_test: Fix array underflow in pci_endpoint_test_ioctl()",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-40117.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.