OESA-2025-1962 (CVE-2025-38424)

Vulnerability from osv_openeuler – Published: 2025-08-08 11:09 – Updated: 2026-08-06 11:09 – Source website
VLAI
Summary
kernel security update
Details

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

perf: Fix sample vs do_exit()

Baisheng Gao reported an ARM64 crash, which Mark decoded as being a synchronous external abort -- most likely due to trying to access MMIO in bad ways.

The crash further shows perf trying to do a user stack sample while in exit_mmap()'s tlb_finish_mmu() -- i.e. while tearing down the address space it is trying to access.

It turns out that we stop perf after we tear down the userspace mm; a receipie for disaster, since perf likes to access userspace for various reasons.

Flip this order by moving up where we stop perf in do_exit().

Additionally, harden PERF_SAMPLE_CALLCHAIN and PERF_SAMPLE_STACK_USER to abort when the current task does not have an mm (exit_mm() makes sure to set current->mm = NULL; before commencing with the actual teardown). Such that CPU wide events don't trip on this same problem.(CVE-2025-38424)


{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "bpftool-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "bpftool-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "kernel-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "kernel-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "kernel-debugsource-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "kernel-devel-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "kernel-source-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "kernel-tools-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "kernel-tools-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "kernel-tools-devel-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "perf-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "perf-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "python2-perf-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "python2-perf-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "python3-perf-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm",
          "python3-perf-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.aarch64.rpm"
        ],
        "src": [
          "kernel-4.19.90-2507.5.0.0338.oe2003sp4.src.rpm"
        ],
        "x86_64": [
          "bpftool-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "bpftool-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "kernel-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "kernel-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "kernel-debugsource-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "kernel-devel-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "kernel-source-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "kernel-tools-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "kernel-tools-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "kernel-tools-devel-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "perf-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "perf-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "python2-perf-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "python2-perf-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "python3-perf-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm",
          "python3-perf-debuginfo-4.19.90-2507.5.0.0338.oe2003sp4.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP4",
        "name": "kernel",
        "purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP4"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.19.90-2507.5.0.0338.oe2003sp4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "High"
  },
  "details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Fix sample vs do_exit()\n\nBaisheng Gao reported an ARM64 crash, which Mark decoded as being a\nsynchronous external abort -- most likely due to trying to access\nMMIO in bad ways.\n\nThe crash further shows perf trying to do a user stack sample while in\nexit_mmap()\u0026apos;s tlb_finish_mmu() -- i.e. while tearing down the address\nspace it is trying to access.\n\nIt turns out that we stop perf after we tear down the userspace mm; a\nreceipie for disaster, since perf likes to access userspace for\nvarious reasons.\n\nFlip this order by moving up where we stop perf in do_exit().\n\nAdditionally, harden PERF_SAMPLE_CALLCHAIN and PERF_SAMPLE_STACK_USER\nto abort when the current task does not have an mm (exit_mm() makes\nsure to set current-\u0026gt;mm = NULL; before commencing with the actual\nteardown). Such that CPU wide events don\u0026apos;t trip on this same problem.(CVE-2025-38424)",
  "id": "OESA-2025-1962",
  "modified": "2026-08-06T11:09:02Z",
  "published": "2025-08-08T11:09:02Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1962"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38424"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "kernel security update",
  "upstream": [
    "CVE-2025-38424"
  ]
}



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.