LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38696: MIPS: Don't crash in stack_top() for tasks without ABI or vDSO

In the Linux kernel, the following vulnerability has been resolved: MIPS: Don't crash in stack_top() for tasks without ABI or vDSO Not all tasks have an ABI associated or vDSO mapped, for example kthreads never do. If such a task ever ends up calling stack_top(), it will derefence the NULL ABI pointer and crash. This can for example happen when using kunit: mips_stack_top+0x28/0xc0 arch_pick_mmap_layout+0x190/0x220 kunit_vm_mmap_init+0xf8/0x138 __kunit_add_resource+0x40/0xa8 kunit_vm_mmap+0x88/0xd8 usercopy_test_init+0xb8/0x240 kunit_try_run_case+0x5c/0x1a8 kunit_generic_run_threadfn_adapter+0x28/0x50 kthread+0x118/0x240 ret_from_kernel_thread+0x14/0x1c Only dereference the ABI point if it is set. The GIC page is also included as it is specific to the vDSO. Also move the randomization adjustment into the same conditional.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel reliability flaw on MIPS systems. Certain kernel tasks without normal user ABI or vDSO state can trigger a NULL pointer dereference and crash. The public record describes a fix, but provides no CVSS score and no evidence of active exploitation.

Executive priority

Treat as a targeted maintenance issue, not an emergency, unless your environment depends on exposed MIPS-based Linux appliances. Patch through normal kernel or vendor update channels and verify affected embedded systems are not overlooked.

Technical view

In MIPS stack_top(), the kernel dereferenced the task ABI pointer even when no ABI or vDSO was present. Kernel threads, including a cited KUnit path, can reach this logic through mmap layout setup. The fix only dereferences ABI-dependent values when present and keeps vDSO-specific GIC and randomization handling inside that condition.

Likely exposure

Exposure appears limited to Linux systems using affected MIPS kernel versions or downstream products that include those kernels. The source bundle lists multiple Linux stable branches and fix commits, plus a Debian LTS advisory. Non-MIPS kernels are not identified as affected in the supplied evidence.

Exploitation context

The supplied sources describe a kernel crash condition, not privilege escalation, remote code execution, or data exposure. KEV is false, and no source in the bundle states active exploitation. Evidence points to denial-of-service style impact if the vulnerable path is reachable.

Researcher notes

The public evidence is narrow: a MIPS stack_top NULL dereference involving tasks without ABI or vDSO, demonstrated through a KUnit-related path. Impact and reachability outside kernel test or internal paths are not fully established in the supplied bundle.

Mitigation direction

  • Update affected Linux kernels to vendor-supported fixed builds.
  • Prioritize MIPS systems and appliances using listed affected kernel branches.
  • Review Debian LTS and device-vendor advisories for packaged fixes.
  • If no package is available, track upstream stable fix commits with the vendor.
  • Avoid custom backports without kernel regression testing.

Validation and detection

  • Inventory systems running Linux on MIPS architecture.
  • Map kernel versions against vendor advisories and fixed stable commits.
  • Check package changelogs for CVE-2025-38696 or the referenced MIPS fix.
  • Confirm rebooted systems are running the updated kernel.
  • Review crash logs for stack_top or mips_stack_top NULL dereference traces.
Prepared
Confidence
medium
Sources
12

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-38696 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
2ADP providers
12Source 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.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxea7e0480a4b695d0aa6b3fa99bd658a003122113, ea7e0480a4b695d0aa6b3fa99bd658a003122113, ea7e0480a4b695d0aa6b3fa99bd658a003122113, ea7e0480a4b695d0aa6b3fa99bd658a003122113, ea7e0480a4b695d0aa6b3fa99bd658a003122113, ea7e0480a4b695d0aa6b3fa99bd658a003122113, ea7e0480a4b695d0aa6b3fa99bd658a003122113, ea7e0480a4b695d0aa6b3fa99bd658a003122113, ea7e0480a4b695d0aa6b3fa99bd658a003122113, 86717a97f9218de798c6d33e0014ab9325e18f56, e4882348eaa9f5f052cb21d2a5aa99a063e4308b, 4.14.77, 4.18.15unaffected
LinuxLinux4.19, 0, 5.4.297, 5.10.241, 5.15.190, 6.1.149, 6.6.103, 6.12.43, 6.15.11, 6.16.2, 6.17affected
Weakness

CWE details

No CWE listed

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