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

exploitDog

Количество 24

Количество 24

ubuntu логотип

CVE-2025-37931

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

In the Linux kernel, the following vulnerability has been resolved: btrfs: adjust subpage bit start based on sectorsize When running machines with 64k page size and a 16k nodesize we started seeing tree log corruption in production. This turned out to be because we were not writing out dirty blocks sometimes, so this in fact affects all metadata writes. When writing out a subpage EB we scan the subpage bitmap for a dirty range. If the range isn't dirty we do bit_start++; to move onto the next bit. The problem is the bitmap is based on the number of sectors that an EB has. So in this case, we have a 64k pagesize, 16k nodesize, but a 4k sectorsize. This means our bitmap is 4 bits for every node. With a 64k page size we end up with 4 nodes per page. To make this easier this is how everything looks [0 16k 32k 48k ] logical address [0 4 8 12 ] radix tree offset [ 64k page ] folio [ 16k eb ][ 16k eb ][ ...

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

CVE-2025-37931

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

In the Linux kernel, the following vulnerability has been resolved: btrfs: adjust subpage bit start based on sectorsize When running machines with 64k page size and a 16k nodesize we started seeing tree log corruption in production. This turned out to be because we were not writing out dirty blocks sometimes, so this in fact affects all metadata writes. When writing out a subpage EB we scan the subpage bitmap for a dirty range. If the range isn't dirty we do bit_start++; to move onto the next bit. The problem is the bitmap is based on the number of sectors that an EB has. So in this case, we have a 64k pagesize, 16k nodesize, but a 4k sectorsize. This means our bitmap is 4 bits for every node. With a 64k page size we end up with 4 nodes per page. To make this easier this is how everything looks [0 16k 32k 48k ] logical address [0 4 8 12 ] radix tree offset [ 64k page ] folio [ 16k eb ][ 16k eb ][ ...

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

CVE-2025-37931

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

In the Linux kernel, the following vulnerability has been resolved: btrfs: adjust subpage bit start based on sectorsize When running machines with 64k page size and a 16k nodesize we started seeing tree log corruption in production. This turned out to be because we were not writing out dirty blocks sometimes, so this in fact affects all metadata writes. When writing out a subpage EB we scan the subpage bitmap for a dirty range. If the range isn't dirty we do bit_start++; to move onto the next bit. The problem is the bitmap is based on the number of sectors that an EB has. So in this case, we have a 64k pagesize, 16k nodesize, but a 4k sectorsize. This means our bitmap is 4 bits for every node. With a 64k page size we end up with 4 nodes per page. To make this easier this is how everything looks [0 16k 32k 48k ] logical address [0 4 8 12 ] radix tree offset [ 64k page ] folio [ 16k eb ][ 16k e

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

CVE-2025-37931

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

btrfs: adjust subpage bit start based on sectorsize

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

CVE-2025-37931

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

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

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

GHSA-v9hh-vwqw-fc9h

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

In the Linux kernel, the following vulnerability has been resolved: btrfs: adjust subpage bit start based on sectorsize When running machines with 64k page size and a 16k nodesize we started seeing tree log corruption in production. This turned out to be because we were not writing out dirty blocks sometimes, so this in fact affects all metadata writes. When writing out a subpage EB we scan the subpage bitmap for a dirty range. If the range isn't dirty we do bit_start++; to move onto the next bit. The problem is the bitmap is based on the number of sectors that an EB has. So in this case, we have a 64k pagesize, 16k nodesize, but a 4k sectorsize. This means our bitmap is 4 bits for every node. With a 64k page size we end up with 4 nodes per page. To make this easier this is how everything looks [0 16k 32k 48k ] logical address [0 4 8 12 ] radix tree offset [ 64k page ] folio [ 16k eb ][ 16...

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

BDU:2025-15159

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

Уязвимость компонента btrfs ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на целостность защищаемой информации

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

ROS-20260203-80-0023

8 месяцев назад

Уязвимость kernel-lt

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

ROS-20260203-73-0021

8 месяцев назад

Уязвимость kernel-lt

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

ALT-PU-2025-16508

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

ALT-PU-2025-16508: package `kernel-image-6.12` update to version 6.12.29-alt1

CVSS3: 8.8
EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2025:02000-1

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

Security update for the Linux Kernel

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2025:01965-1

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

Security update for the Linux Kernel

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

ALT-PU-2025-16454

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

ALT-PU-2025-16454: package `kernel-image-pine` update to version 6.12.28-alt2

CVSS3: 8.8
EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2025:02333-1

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

Security update for the Linux Kernel

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2025:02307-1

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

Security update for the Linux Kernel

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2025:02254-1

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

Security update for the Linux Kernel

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

ALT-PU-2025-16600

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

ALT-PU-2025-16600: package `kernel-image-un-def` update to version 6.1.151-alt1

CVSS3: 9.8
EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2025:01964-1

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

Security update for the Linux Kernel

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2025:02923-1

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

Security update for the Linux Kernel

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

ALT-PU-2025-8293

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

ALT-PU-2025-8293: package `kernel-image-rt` update to version 6.12.34-alt1

CVSS3: 8.8
EPSS: Низкий

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

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

In the Linux kernel, the following vulnerability has been resolved: btrfs: adjust subpage bit start based on sectorsize When running machines with 64k page size and a 16k nodesize we started seeing tree log corruption in production. This turned out to be because we were not writing out dirty blocks sometimes, so this in fact affects all metadata writes. When writing out a subpage EB we scan the subpage bitmap for a dirty range. If the range isn't dirty we do bit_start++; to move onto the next bit. The problem is the bitmap is based on the number of sectors that an EB has. So in this case, we have a 64k pagesize, 16k nodesize, but a 4k sectorsize. This means our bitmap is 4 bits for every node. With a 64k page size we end up with 4 nodes per page. To make this easier this is how everything looks [0 16k 32k 48k ] logical address [0 4 8 12 ] radix tree offset [ 64k page ] folio [ 16k eb ][ 16k eb ][ ...

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

In the Linux kernel, the following vulnerability has been resolved: btrfs: adjust subpage bit start based on sectorsize When running machines with 64k page size and a 16k nodesize we started seeing tree log corruption in production. This turned out to be because we were not writing out dirty blocks sometimes, so this in fact affects all metadata writes. When writing out a subpage EB we scan the subpage bitmap for a dirty range. If the range isn't dirty we do bit_start++; to move onto the next bit. The problem is the bitmap is based on the number of sectors that an EB has. So in this case, we have a 64k pagesize, 16k nodesize, but a 4k sectorsize. This means our bitmap is 4 bits for every node. With a 64k page size we end up with 4 nodes per page. To make this easier this is how everything looks [0 16k 32k 48k ] logical address [0 4 8 12 ] radix tree offset [ 64k page ] folio [ 16k eb ][ 16k eb ][ ...

0%
Низкий
больше 1 года назад
nvd логотип
CVE-2025-37931

In the Linux kernel, the following vulnerability has been resolved: btrfs: adjust subpage bit start based on sectorsize When running machines with 64k page size and a 16k nodesize we started seeing tree log corruption in production. This turned out to be because we were not writing out dirty blocks sometimes, so this in fact affects all metadata writes. When writing out a subpage EB we scan the subpage bitmap for a dirty range. If the range isn't dirty we do bit_start++; to move onto the next bit. The problem is the bitmap is based on the number of sectors that an EB has. So in this case, we have a 64k pagesize, 16k nodesize, but a 4k sectorsize. This means our bitmap is 4 bits for every node. With a 64k page size we end up with 4 nodes per page. To make this easier this is how everything looks [0 16k 32k 48k ] logical address [0 4 8 12 ] radix tree offset [ 64k page ] folio [ 16k eb ][ 16k e

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

btrfs: adjust subpage bit start based on sectorsize

CVSS3: 5.5
0%
Низкий
около 1 года назад
debian логотип
CVE-2025-37931

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

CVSS3: 7.3
0%
Низкий
больше 1 года назад
github логотип
GHSA-v9hh-vwqw-fc9h

In the Linux kernel, the following vulnerability has been resolved: btrfs: adjust subpage bit start based on sectorsize When running machines with 64k page size and a 16k nodesize we started seeing tree log corruption in production. This turned out to be because we were not writing out dirty blocks sometimes, so this in fact affects all metadata writes. When writing out a subpage EB we scan the subpage bitmap for a dirty range. If the range isn't dirty we do bit_start++; to move onto the next bit. The problem is the bitmap is based on the number of sectors that an EB has. So in this case, we have a 64k pagesize, 16k nodesize, but a 4k sectorsize. This means our bitmap is 4 bits for every node. With a 64k page size we end up with 4 nodes per page. To make this easier this is how everything looks [0 16k 32k 48k ] logical address [0 4 8 12 ] radix tree offset [ 64k page ] folio [ 16k eb ][ 16...

CVSS3: 5.5
0%
Низкий
больше 1 года назад
fstec логотип
BDU:2025-15159

Уязвимость компонента btrfs ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на целостность защищаемой информации

CVSS3: 5.5
0%
Низкий
больше 1 года назад
redos логотип
ROS-20260203-80-0023

Уязвимость kernel-lt

CVSS3: 5.5
0%
Низкий
8 месяцев назад
redos логотип
ROS-20260203-73-0021

Уязвимость kernel-lt

CVSS3: 5.5
0%
Низкий
8 месяцев назад
altlinux логотип
ALT-PU-2025-16508

ALT-PU-2025-16508: package `kernel-image-6.12` update to version 6.12.29-alt1

CVSS3: 8.8
больше 1 года назад
suse-cvrf логотип
SUSE-SU-2025:02000-1

Security update for the Linux Kernel

больше 1 года назад
suse-cvrf логотип
SUSE-SU-2025:01965-1

Security update for the Linux Kernel

больше 1 года назад
altlinux логотип
ALT-PU-2025-16454

ALT-PU-2025-16454: package `kernel-image-pine` update to version 6.12.28-alt2

CVSS3: 8.8
больше 1 года назад
suse-cvrf логотип
SUSE-SU-2025:02333-1

Security update for the Linux Kernel

около 1 года назад
suse-cvrf логотип
SUSE-SU-2025:02307-1

Security update for the Linux Kernel

около 1 года назад
suse-cvrf логотип
SUSE-SU-2025:02254-1

Security update for the Linux Kernel

около 1 года назад
altlinux логотип
ALT-PU-2025-16600

ALT-PU-2025-16600: package `kernel-image-un-def` update to version 6.1.151-alt1

CVSS3: 9.8
около 1 года назад
suse-cvrf логотип
SUSE-SU-2025:01964-1

Security update for the Linux Kernel

больше 1 года назад
suse-cvrf логотип
SUSE-SU-2025:02923-1

Security update for the Linux Kernel

около 1 года назад
altlinux логотип
ALT-PU-2025-8293

ALT-PU-2025-8293: package `kernel-image-rt` update to version 6.12.34-alt1

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

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