CVE-2024-42149
Last modified
CVE-2024-42149 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: fs: don't misleadingly warn during thaw operations The block device may have been frozen before it was claimed by a filesystem. Concurrently another process might try to mount that frozen block device and has temporarily claimed the block device for that purpose causing a concurrent fs_bdev_thaw() to end up here. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: fs: don't misleadingly warn during thaw operations The block device may have been frozen before it was claimed by a filesystem. Concurrently another process might try to mount that frozen block device and has temporarily claimed the block device for that purpose causing a concurrent fs_bdev_thaw() to end up here. The mounter is already about to abort mounting because they still saw an elevanted bdev->bd_fsfreeze_count so get_bdev_super() will return NULL in that case. For example, P1 calls dm_suspend() which calls into bdev_freeze() before the block device has been claimed by the filesystem. This brings bdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() is required. Now P2 tries to mount that frozen block device. It claims it and checks bdev->bd_fsfreeze_count. As it's elevated it aborts mounting. In the meantime P3 called dm_resume(). P3 sees that the block device is already claimed by a filesystem and calls into fs_bdev_thaw(). P3 takes a passive reference and realizes that the filesystem isn't ready yet. P3 puts itself to sleep to wait for the filesystem to become ready. P2 now puts the last active reference to the filesystem and marks it as dying. P3 gets woken, sees that the filesystem is dying and get_bdev_super() fails.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.8, < 6.9.9 | — |
| Linux | Linux Kernel | 6.10 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-42149?
How severe is CVE-2024-42149?
How do I fix CVE-2024-42149?
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-42143Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2024-42144In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-42145In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-42146In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-42147In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-42148In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-4215pgAdmin <= 8.5 is affected by a multi-factor authentication …8.8
- CVE-2024-42150In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-42151In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-42152In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-42153In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-42154In the Linux kernel, the following vulnerability has been re…4.4
Are you affected by CVE-2024-42149?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
