Поиск уязвимостей
Количество 23
Количество 23
CVE-2022-49075
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the bytes_changed is set as "unsigned int", and it will overflow if we try to fallocate a range larger than 4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than 256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per extent limit, and caused the problem. The following example test script reproduces the problem: $ cat qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a 3GiB file. This should fail. ...
CVE-2022-49075
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the bytes_changed is set as "unsigned int", and it will overflow if we try to fallocate a range larger than 4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than 256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per extent limit, and caused the problem. The following example test script reproduces the problem: $ cat qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a 3GiB file. This should fail. ...
CVE-2022-49075
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the bytes_changed is set as "unsigned int", and it will overflow if we try to fallocate a range larger than 4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than 256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per extent limit, and caused the problem. The following example test script reproduces the problem: $ cat qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a 3Gi
CVE-2022-49075
In the Linux kernel, the following vulnerability has been resolved: b ...
GHSA-96wx-hqjc-pv4q
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the bytes_changed is set as "unsigned int", and it will overflow if we try to fallocate a range larger than 4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than 256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per extent limit, and caused the problem. The following example test script reproduces the problem: $ cat qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a ...
BDU:2025-06049
Уязвимость модуля fs/btrfs/extent_io.h файловой системы btrfs ядра операционной системы Linux, позволяющая нарушителю повысить свои привилегии
ROS-20250522-01
Множественные уязвимости kernel-lt
ALT-PU-2022-1735
ALT-PU-2022-1735: package `kernel-image-std-def` update to version 5.10.111-alt1
ALT-PU-2022-7802
ALT-PU-2022-7802: package `kernel-image-std-def` update to version 5.15.34-alt1
ALT-PU-2022-7696
ALT-PU-2022-7696: package `kernel-image-un-def` update to version 5.15.34-alt1
ALT-PU-2022-1692
ALT-PU-2022-1692: package `kernel-image-un-def` update to version 5.16.20-alt1
ALT-PU-2022-1830
ALT-PU-2022-1830: package `kernel-image-rpi-def` update to version 5.15.36-alt1
SUSE-SU-2025:1293-1
Security update for the Linux Kernel
ALT-PU-2022-7823
ALT-PU-2022-7823: package `kernel-image-xenomai` update to version 4.19.246-alt1.cip75.22
ALT-PU-2022-1881
ALT-PU-2022-1881: package `kernel-image-rt` update to version 5.10.115-alt1.rt67
ALT-PU-2022-1880
ALT-PU-2022-1880: package `kernel-image-rt` update to version 5.10.115-alt1.rt67
ALT-PU-2022-1907
ALT-PU-2022-1907: package `kernel-image-std-kvm` update to version 5.10.117-alt1
ALT-PU-2022-2344
ALT-PU-2022-2344: package `kernel-image-xenomai` update to version 4.19.252-alt1.cip78.23
ALT-PU-2022-1730
ALT-PU-2022-1730: package `kernel-image-mp` update to version 5.17.4-alt1
ALT-PU-2022-1833
ALT-PU-2022-1833: package `kernel-image-rpi-def` update to version 5.15.36-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2022-49075 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the bytes_changed is set as "unsigned int", and it will overflow if we try to fallocate a range larger than 4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than 256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per extent limit, and caused the problem. The following example test script reproduces the problem: $ cat qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a 3GiB file. This should fail. ... | CVSS3: 5.5 | 1% Низкий | больше 1 года назад | |
CVE-2022-49075 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the bytes_changed is set as "unsigned int", and it will overflow if we try to fallocate a range larger than 4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than 256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per extent limit, and caused the problem. The following example test script reproduces the problem: $ cat qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a 3GiB file. This should fail. ... | 1% Низкий | больше 1 года назад | ||
CVE-2022-49075 In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the bytes_changed is set as "unsigned int", and it will overflow if we try to fallocate a range larger than 4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than 256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per extent limit, and caused the problem. The following example test script reproduces the problem: $ cat qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a 3Gi | CVSS3: 5.5 | 1% Низкий | больше 1 года назад | |
CVE-2022-49075 In the Linux kernel, the following vulnerability has been resolved: b ... | CVSS3: 5.5 | 1% Низкий | больше 1 года назад | |
GHSA-96wx-hqjc-pv4q In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the bytes_changed is set as "unsigned int", and it will overflow if we try to fallocate a range larger than 4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than 256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per extent limit, and caused the problem. The following example test script reproduces the problem: $ cat qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a ... | CVSS3: 5.5 | 1% Низкий | около 1 года назад | |
BDU:2025-06049 Уязвимость модуля fs/btrfs/extent_io.h файловой системы btrfs ядра операционной системы Linux, позволяющая нарушителю повысить свои привилегии | CVSS3: 5.5 | 1% Низкий | больше 4 лет назад | |
ROS-20250522-01 Множественные уязвимости kernel-lt | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2022-1735 ALT-PU-2022-1735: package `kernel-image-std-def` update to version 5.10.111-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-7802 ALT-PU-2022-7802: package `kernel-image-std-def` update to version 5.15.34-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-7696 ALT-PU-2022-7696: package `kernel-image-un-def` update to version 5.15.34-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1692 ALT-PU-2022-1692: package `kernel-image-un-def` update to version 5.16.20-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1830 ALT-PU-2022-1830: package `kernel-image-rpi-def` update to version 5.15.36-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
SUSE-SU-2025:1293-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2022-7823 ALT-PU-2022-7823: package `kernel-image-xenomai` update to version 4.19.246-alt1.cip75.22 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1881 ALT-PU-2022-1881: package `kernel-image-rt` update to version 5.10.115-alt1.rt67 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1880 ALT-PU-2022-1880: package `kernel-image-rt` update to version 5.10.115-alt1.rt67 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1907 ALT-PU-2022-1907: package `kernel-image-std-kvm` update to version 5.10.117-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-2344 ALT-PU-2022-2344: package `kernel-image-xenomai` update to version 4.19.252-alt1.cip78.23 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1730 ALT-PU-2022-1730: package `kernel-image-mp` update to version 5.17.4-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1833 ALT-PU-2022-1833: package `kernel-image-rpi-def` update to version 5.15.36-alt1 | CVSS3: 9.8 | больше 4 лет назад |
Уязвимостей на страницу