CVE-2024-26617 fs/proc/task_mmu: move mmu notification mechanism inside mm lock

High 7.8 Published Updated

A race condition in the Linux kernel's mmu notification mechanism can lead to system instability or crashes, requiring a kernel patch.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2024-26617?

CVE-2024-26617 is a high-severity vulnerability in Linux kernel, published on 29 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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

fs/proc/task_mmu: move mmu notification mechanism inside mm lock

Move mmu notification mechanism inside mm lock to prevent race condition in other components which depend on it. The notifier will invalidate memory range. Depending upon the number of iterations, different memory ranges would be invalidated.

The following warning would be removed by this patch: WARNING: CPU: 0 PID: 5067 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:734 kvm_mmu_notifier_change_pte+0x860/0x960 arch/x86/kvm/../../../virt/kvm/kvm_main.c:734

There is no behavioural and performance change with this patch when there is no component registered with the mmu notifier.

[[email protected]: narrow the scope of `range', per Sean]

Weakness: CWE-362

Which versions are affected by CVE-2024-26617?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2024-26617?

Apply the vendor's patch.

Is CVE-2024-26617 being exploited?

There is no known exploitation of CVE-2024-26617 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2024-26617, GHSA-5gxq-j292-75cc, UBUNTU-CVE-2024-26617.

Is CVE-2024-26617 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free