PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-93137 Linux CVE debrief

A use-after-free vulnerability exists in the Linux kernel's bpf_find_vma() function, allowing for potential use-after-free when accessing the mm_struct of a foreign task. This vulnerability requires assessment and verification of Linux kernel configurations and BPF program usage to prevent potential exploitation. The bpf_find_vma() function reads task->mm and calls mmap_read_trylock(mm) without holding a reference on the mm. On a foreign task, a concurrent exit_mm() can free the mm_struct between the lockless read and the trylock, resulting in a use-after-free. mm_struct is not SLAB_TYPESAFE_BY_RCU.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-17
Original CVE updated
2026-09-18
Advisory published
2026-09-17
Advisory updated
2026-09-18

Who should care

Linux kernel developers, administrators, and users of BPF programs should assess exposure and prioritize verification of Linux kernel configurations and BPF program usage to prevent potential exploitation. This includes verifying Linux kernel configurations, reviewing BPF program usage, and monitoring system logs for potential exploitation attempts.

Why it matters

A use-after-free vulnerability in the Linux kernel's bpf_find_vma() function requires assessment and verification of Linux kernel configurations and BPF program usage to prevent potential exploitation.

  • Potential use-after-free when accessing mm_struct
  • Need to verify Linux kernel configurations and BPF program usage
  • Possible impact on system stability and security

Technical summary

The Linux kernel's bpf_find_vma() function has a use-after-free vulnerability when accessing the mm_struct of a foreign task. This occurs when a concurrent exit_mm() frees the mm_struct between the lockless read and the trylock. The vulnerability requires assessment and verification of Linux kernel configurations and BPF program usage to prevent potential exploitation. The fix involves pinning the mm under task->alloc_lock and releasing it with mmput_async(). Users should assess exposure and prioritize verification of Linux kernel configurations and BPF program usage.

Defensive priority

Assess exposure and prioritize verification of Linux kernel configurations and BPF program usage.

Recommended defensive actions

  • Assess Linux kernel configurations and BPF program usage
  • Verify mm_struct reference counting in bpf_find_vma()
  • Review system logs for potential exploitation attempts
  • Implement compensating controls for exposed systems
  • Monitor relevant logs for exposed assets
  • Track exceptions and retest remediated assets
  • Review vendor-supported updates or mitigations

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but evidence of exploitation is limited. Linux kernel developers, administrators, and users of BPF programs should assess exposure and prioritize verification of Linux kernel configurations and BPF program usage. The vulnerability has been resolved in the Linux kernel, but users should verify their configurations and BPF program usage to prevent potential exploitation.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-93137 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-93137

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-93137 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-93137

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/2b2a903bee56d312539046d9defa8023eec94760

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/47b079e2117a2ee52e21f8b72935900c702fc0b5

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/86d54cf069fc5ae2e111c87933bebf6eb527978e

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/8e1101fc4118019a69c96ced4aec93164f89cbd5

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/c7ad910e987008e125eeff448892e86852173384

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/db347840d6b6ee9bb9b8e4a985d4b4419f9f3200

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.