CVE-2024-50006
Last modified
CVE-2024-50006 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ext4: fix i_data_sem unlock order in ext4_ind_migrate() Fuzzing reports a possible deadlock in jbd2_log_wait_commit. This issue is triggered when an EXT4_IOC_MIGRATE ioctl is set to require synchronous updates because the file descriptor is opened with O_SYNC. This can lead to the jbd2_journal_stop() function calling jbd2_might_wait_for_commit(), potentially causing a deadlock if the EXT4_IOC_MIGRATE call races with a write(2) system call. This problem only arises when CONFIG_PROVE_LOCKING is enabled. In this case, the jbd2_might_wait_for_commit macro locks jbd2_handle in the jbd2_journal_stop function while i_data_sem is locked. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ext4: fix i_data_sem unlock order in ext4_ind_migrate() Fuzzing reports a possible deadlock in jbd2_log_wait_commit. This issue is triggered when an EXT4_IOC_MIGRATE ioctl is set to require synchronous updates because the file descriptor is opened with O_SYNC. This can lead to the jbd2_journal_stop() function calling jbd2_might_wait_for_commit(), potentially causing a deadlock if the EXT4_IOC_MIGRATE call races with a write(2) system call. This problem only arises when CONFIG_PROVE_LOCKING is enabled. In this case, the jbd2_might_wait_for_commit macro locks jbd2_handle in the jbd2_journal_stop function while i_data_sem is locked. This triggers lockdep because the jbd2_journal_start function might also lock the same jbd2_handle simultaneously. Found by Linux Verification Center (linuxtesting.org) with syzkaller. Rule: add
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 5.10.227 |
| Linux | Linux Kernel | >= 5.11, < 5.15.168 |
| Linux | Linux Kernel | >= 5.16, < 6.1.113 |
| Linux | Linux Kernel | >= 6.2, < 6.6.55 |
| Linux | Linux Kernel | >= 6.7, < 6.10.14 |
| Linux | Linux Kernel | >= 6.11, < 6.11.3 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-50006?
How severe is CVE-2024-50006?
How do I fix CVE-2024-50006?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-50000In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50001In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50002In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50003In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50004In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50005In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-50007In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-50008In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50009In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5001The Image Hover Effects for Elementor with Lightbox and Flip…5.4
- CVE-2024-50010In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-50011In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-50006?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
