Bug 1221294 (CVE-2024-26617) - VUL-0: CVE-2024-26617: kernel: fs/proc/task_mmu: move mmu notification mechanism inside mm lock
Summary: VUL-0: CVE-2024-26617: kernel: fs/proc/task_mmu: move mmu notification mechan...
Status: RESOLVED FIXED
Alias: CVE-2024-26617
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/397154/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-12 13:06 UTC by SMASH SMASH
Modified: 2024-06-10 12:25 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-03-12 13:06:17 UTC
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.

[akpm@linux-foundation.org: narrow the scope of `range', per Sean]

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-26617
https://git.kernel.org/stable/c/4cccb6221cae6d020270606b9e52b1678fc8b71a
https://www.cve.org/CVERecord?id=CVE-2024-26617
https://git.kernel.org/stable/c/05509adf297924f51e1493aa86f9fcde1433ed80
Comment 1 Gabriele Sonnu 2024-03-12 13:08:47 UTC
Offending commit (52526ca7fdb9) is only in stable, that also contain the fix (05509adf2979). @kernel-team, please add the reference.
Comment 2 Oscar Salvador 2024-04-17 03:05:26 UTC
Nothing to do.
Back to sec-team.
Comment 3 Gabriele Sonnu 2024-06-10 12:25:34 UTC
All done, closing.