Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

Поиск уязвимостей

Количество 12

Количество 12

ubuntu логотип

CVE-2022-49547

больше 1 года назад

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between concurrent dio writes when low on free data space When reserving data space for a direct IO write we can end up deadlocking if we have multiple tasks attempting a write to the same file range, there are multiple extents covered by that file range, we are low on available space for data and the writes don't expand the inode's i_size. The deadlock can happen like this: 1) We have a file with an i_size of 1M, at offset 0 it has an extent with a size of 128K and at offset 128K it has another extent also with a size of 128K; 2) Task A does a direct IO write against file range [0, 256K), and because the write is within the i_size boundary, it takes the inode's lock (VFS level) in shared mode; 3) Task A locks the file range [0, 256K) at btrfs_dio_iomap_begin(), and then gets the extent map for the extent covering the range [0, 128K). At btrfs_get_blocks_direct_write(), it creates an ordered exte...

CVSS3: 5.5
EPSS: Низкий
redhat логотип

CVE-2022-49547

больше 1 года назад

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between concurrent dio writes when low on free data space When reserving data space for a direct IO write we can end up deadlocking if we have multiple tasks attempting a write to the same file range, there are multiple extents covered by that file range, we are low on available space for data and the writes don't expand the inode's i_size. The deadlock can happen like this: 1) We have a file with an i_size of 1M, at offset 0 it has an extent with a size of 128K and at offset 128K it has another extent also with a size of 128K; 2) Task A does a direct IO write against file range [0, 256K), and because the write is within the i_size boundary, it takes the inode's lock (VFS level) in shared mode; 3) Task A locks the file range [0, 256K) at btrfs_dio_iomap_begin(), and then gets the extent map for the extent covering the range [0, 128K). At btrfs_get_blocks_direct_write(), it creates an ordered exte...

CVSS3: 5.5
EPSS: Низкий
nvd логотип

CVE-2022-49547

больше 1 года назад

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between concurrent dio writes when low on free data space When reserving data space for a direct IO write we can end up deadlocking if we have multiple tasks attempting a write to the same file range, there are multiple extents covered by that file range, we are low on available space for data and the writes don't expand the inode's i_size. The deadlock can happen like this: 1) We have a file with an i_size of 1M, at offset 0 it has an extent with a size of 128K and at offset 128K it has another extent also with a size of 128K; 2) Task A does a direct IO write against file range [0, 256K), and because the write is within the i_size boundary, it takes the inode's lock (VFS level) in shared mode; 3) Task A locks the file range [0, 256K) at btrfs_dio_iomap_begin(), and then gets the extent map for the extent covering the range [0, 128K). At btrfs_get_blocks_direct_write(), it cr

CVSS3: 5.5
EPSS: Низкий
msrc логотип

CVE-2022-49547

около 1 года назад

btrfs: fix deadlock between concurrent dio writes when low on free data space

EPSS: Низкий
debian логотип

CVE-2022-49547

больше 1 года назад

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

CVSS3: 5.5
EPSS: Низкий
github логотип

GHSA-85q7-hhcq-pr4h

больше 1 года назад

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between concurrent dio writes when low on free data space When reserving data space for a direct IO write we can end up deadlocking if we have multiple tasks attempting a write to the same file range, there are multiple extents covered by that file range, we are low on available space for data and the writes don't expand the inode's i_size. The deadlock can happen like this: 1) We have a file with an i_size of 1M, at offset 0 it has an extent with a size of 128K and at offset 128K it has another extent also with a size of 128K; 2) Task A does a direct IO write against file range [0, 256K), and because the write is within the i_size boundary, it takes the inode's lock (VFS level) in shared mode; 3) Task A locks the file range [0, 256K) at btrfs_dio_iomap_begin(), and then gets the extent map for the extent covering the range [0, 128K). At btrfs_get_blocks_direct_write(), it...

CVSS3: 5.5
EPSS: Низкий
altlinux логотип

ALT-PU-2022-2131

больше 4 лет назад

ALT-PU-2022-2131: package `kernel-image-un-def` update to version 5.18.6-alt1

CVSS3: 8.8
EPSS: Низкий
altlinux логотип

ALT-PU-2022-2050

больше 4 лет назад

ALT-PU-2022-2050: package `kernel-image-mp` update to version 5.18.4-alt1

CVSS3: 8.8
EPSS: Низкий
altlinux логотип

ALT-PU-2023-1741

больше 3 лет назад

ALT-PU-2023-1741: package `kernel-image-un-def` update to version 6.1.26-alt1

CVSS3: 9.8
EPSS: Низкий
altlinux логотип

ALT-PU-2023-1684

больше 3 лет назад

ALT-PU-2023-1684: package `kernel-image-std-def` update to version 6.1.26-alt1

CVSS3: 9.8
EPSS: Низкий
altlinux логотип

ALT-PU-2022-2152

больше 4 лет назад

ALT-PU-2022-2152: package `kernel-image-rpi-un` update to version 5.18.7-alt1

CVSS3: 9.8
EPSS: Низкий
altlinux логотип

ALT-PU-2022-2155

больше 4 лет назад

ALT-PU-2022-2155: package `kernel-image-rpi-un` update to version 5.18.7-alt1

CVSS3: 9.8
EPSS: Низкий

Уязвимостей на страницу

Уязвимость
CVSS
EPSS
Опубликовано
ubuntu логотип
CVE-2022-49547

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between concurrent dio writes when low on free data space When reserving data space for a direct IO write we can end up deadlocking if we have multiple tasks attempting a write to the same file range, there are multiple extents covered by that file range, we are low on available space for data and the writes don't expand the inode's i_size. The deadlock can happen like this: 1) We have a file with an i_size of 1M, at offset 0 it has an extent with a size of 128K and at offset 128K it has another extent also with a size of 128K; 2) Task A does a direct IO write against file range [0, 256K), and because the write is within the i_size boundary, it takes the inode's lock (VFS level) in shared mode; 3) Task A locks the file range [0, 256K) at btrfs_dio_iomap_begin(), and then gets the extent map for the extent covering the range [0, 128K). At btrfs_get_blocks_direct_write(), it creates an ordered exte...

CVSS3: 5.5
0%
Низкий
больше 1 года назад
redhat логотип
CVE-2022-49547

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between concurrent dio writes when low on free data space When reserving data space for a direct IO write we can end up deadlocking if we have multiple tasks attempting a write to the same file range, there are multiple extents covered by that file range, we are low on available space for data and the writes don't expand the inode's i_size. The deadlock can happen like this: 1) We have a file with an i_size of 1M, at offset 0 it has an extent with a size of 128K and at offset 128K it has another extent also with a size of 128K; 2) Task A does a direct IO write against file range [0, 256K), and because the write is within the i_size boundary, it takes the inode's lock (VFS level) in shared mode; 3) Task A locks the file range [0, 256K) at btrfs_dio_iomap_begin(), and then gets the extent map for the extent covering the range [0, 128K). At btrfs_get_blocks_direct_write(), it creates an ordered exte...

CVSS3: 5.5
0%
Низкий
больше 1 года назад
nvd логотип
CVE-2022-49547

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between concurrent dio writes when low on free data space When reserving data space for a direct IO write we can end up deadlocking if we have multiple tasks attempting a write to the same file range, there are multiple extents covered by that file range, we are low on available space for data and the writes don't expand the inode's i_size. The deadlock can happen like this: 1) We have a file with an i_size of 1M, at offset 0 it has an extent with a size of 128K and at offset 128K it has another extent also with a size of 128K; 2) Task A does a direct IO write against file range [0, 256K), and because the write is within the i_size boundary, it takes the inode's lock (VFS level) in shared mode; 3) Task A locks the file range [0, 256K) at btrfs_dio_iomap_begin(), and then gets the extent map for the extent covering the range [0, 128K). At btrfs_get_blocks_direct_write(), it cr

CVSS3: 5.5
0%
Низкий
больше 1 года назад
msrc логотип
CVE-2022-49547

btrfs: fix deadlock between concurrent dio writes when low on free data space

0%
Низкий
около 1 года назад
debian логотип
CVE-2022-49547

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

CVSS3: 5.5
0%
Низкий
больше 1 года назад
github логотип
GHSA-85q7-hhcq-pr4h

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between concurrent dio writes when low on free data space When reserving data space for a direct IO write we can end up deadlocking if we have multiple tasks attempting a write to the same file range, there are multiple extents covered by that file range, we are low on available space for data and the writes don't expand the inode's i_size. The deadlock can happen like this: 1) We have a file with an i_size of 1M, at offset 0 it has an extent with a size of 128K and at offset 128K it has another extent also with a size of 128K; 2) Task A does a direct IO write against file range [0, 256K), and because the write is within the i_size boundary, it takes the inode's lock (VFS level) in shared mode; 3) Task A locks the file range [0, 256K) at btrfs_dio_iomap_begin(), and then gets the extent map for the extent covering the range [0, 128K). At btrfs_get_blocks_direct_write(), it...

CVSS3: 5.5
0%
Низкий
больше 1 года назад
altlinux логотип
ALT-PU-2022-2131

ALT-PU-2022-2131: package `kernel-image-un-def` update to version 5.18.6-alt1

CVSS3: 8.8
больше 4 лет назад
altlinux логотип
ALT-PU-2022-2050

ALT-PU-2022-2050: package `kernel-image-mp` update to version 5.18.4-alt1

CVSS3: 8.8
больше 4 лет назад
altlinux логотип
ALT-PU-2023-1741

ALT-PU-2023-1741: package `kernel-image-un-def` update to version 6.1.26-alt1

CVSS3: 9.8
больше 3 лет назад
altlinux логотип
ALT-PU-2023-1684

ALT-PU-2023-1684: package `kernel-image-std-def` update to version 6.1.26-alt1

CVSS3: 9.8
больше 3 лет назад
altlinux логотип
ALT-PU-2022-2152

ALT-PU-2022-2152: package `kernel-image-rpi-un` update to version 5.18.7-alt1

CVSS3: 9.8
больше 4 лет назад
altlinux логотип
ALT-PU-2022-2155

ALT-PU-2022-2155: package `kernel-image-rpi-un` update to version 5.18.7-alt1

CVSS3: 9.8
больше 4 лет назад

Уязвимостей на страницу