What is CVE-2026-93137?

CVE-2026-93137 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 5.17 onward and patched in 6.1.188, 6.6.157, 6.12.110 and others. CVE-2026-93137 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-93137?

CVE-2026-93137 has a CVSS score of 7.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-93137?

Yes, CVE-2026-93137 has been patched. Fixed versions include 6.1.188, 6.6.157, 6.12.110 and others. If you are running Linux kernel 5.17 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-93137 actively exploited?

CVE-2026-93137 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-93137

High

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix use-after-free on mm_struct in bpf_find_vma() bpf_find_vma() 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. For the current task, task->mm is stable. For a foreign task, pin the mm under task->alloc_lock and release it with mmput_async(), mirroring commit d8e27d2d22b6 ("bpf: fix mm lifecycle in open-coded task_vma iterator"). Use spin_trylock() instead of get_task_mm() so BPF context does not block on alloc_lock. Reject irqs-disabled contexts and !CONFIG_MMU on the foreign-task path because dropping the mm reference is not safe there. Race: CPU0 (BPF program) CPU1 (exiting task) ============================ ========================== bpf_find_vma(foreign_task): mm = task->mm exit_mm(): task->mm = NULL mmput(mm) -> frees mm_struct mmap_read_trylock(mm) // UAF on mm

Package Linux Kernel

Published 2026-09-17

Last modified 2026-09-18

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 5.17 and later are affected. Fixed in 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, 7.3-rc1 and their respective stable series.

Affected from

≥ 5.17

Fixed in

✓ 6.1.188 6.1.x ✓ 6.6.157 6.6.x ✓ 6.12.110 6.12.x ✓ 6.18.52 6.18.x ✓ 7.2.6 7.2.x ✓ 7.3-rc1

References

6 total

Showing 5 of 6 references View all on NVD

Details

CVE ID CVE-2026-93137

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-09-17

Modified 2026-09-18

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-93137?

CVE-2026-93137 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 5.17 onward and has been patched in 6.1.188, 6.6.157, 6.12.110 and others. CVE-2026-93137 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-93137?

CVE-2026-93137 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-93137?

Yes. CVE-2026-93137 has been patched. Fixed versions include 6.1.188, 6.6.157, 6.12.110 and others. If you are running Linux kernel 5.17 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-93137 actively exploited?

No. CVE-2026-93137 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.