Lucene search
K

5 matches found

SUSE CVE
SUSE CVE
added 2026/03/25 4:54 p.m.1 views

SUSE CVE-2026-23388

In the Linux kernel, the following vulnerability has been resolved: Squashfs: check metadata block offset is within range Syzkaller reports a "general protection fault in squashfscopydata" This is ultimately caused by a corrupted index look-up table, which produces a negative metadata block offse...

5.7AI score0.00018EPSS
Exploits0References3
NVD
NVD
added 2026/03/25 11:16 a.m.2 views

CVE-2026-23388

In the Linux kernel, the following vulnerability has been resolved: Squashfs: check metadata block offset is within range Syzkaller reports a "general protection fault in squashfscopydata" This is ultimately caused by a corrupted index look-up table, which produces a negative metadata block offse...

7.1CVSS0.00018EPSS
Exploits0References8
ATTACKERKB
ATTACKERKB
added 2026/03/25 10:28 a.m.0 views

CVE-2026-23388

In the Linux kernel, the following vulnerability has been resolved: Squashfs: check metadata block offset is within range Syzkaller reports a "general protection fault in squashfscopydata" This is ultimately caused by a corrupted index look-up table, which produces a negative metadata block offse...

5.7AI score0.00018EPSS
Exploits0References9Affected Software1
OSV
OSV
added 2026/03/25 10:28 a.m.1 views

CVE-2026-23388 Squashfs: check metadata block offset is within range

In the Linux kernel, the following vulnerability has been resolved: Squashfs: check metadata block offset is within range Syzkaller reports a "general protection fault in squashfscopydata" This is ultimately caused by a corrupted index look-up table, which produces a negative metadata block offse...

7.1CVSS5.7AI score0.00018EPSS
Exploits0References9
Positive Technologies
Positive Technologies
added 2026/03/25 12:0 a.m.2 views

PT-2026-27753

In the Linux kernel, the following vulnerability has been resolved: Squashfs: check metadata block offset is within range Syzkaller reports a "general protection fault in squashfs copy data" This is ultimately caused by a corrupted index look-up table, which produces a negative metadata block...

5.7AI score0.00018EPSS
Exploits0References7
Rows per page
Query Builder