In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
Inthe Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing aconcurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by afilesystem and calls into fs_bdev_thaw().P3 takes apassive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
In the Linux kernel, the following vulnerability has been resolved:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
| linux | | https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 | https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causinga concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed bya filesystem and calls into fs_bdev_thaw().P3 takesa passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
