1673 matches found
CVE-2011-3901
Android SQLite Journal before 4.0.1 has an information disclosure vulnerability...
CVE-2019-19909
An issue was discovered in Public Knowledge Project PKP pkp-lib before 3.1.2-2, as used in Open Journal Systems OJS before 3.1.2-2. Code injection can occur in the OJS report generator if an authenticated Journal Manager user visits a crafted URL, because unserialize is used...
kernel: ext4: fix i_data_sem unlock order in ext4_ind_migrate()
A flaw was found in the kernel's ext4 filesystem. When an EXT4IOCMIGRATE ioctl input/output control operation, requiring synchronous updates, races with a write2 system call, it can lead to a deadlock. This deadlock occurs specifically when the CONFIGPROVELOCKING option is enabled, potentially...
kernel: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error
A flaw was found in the jbd2 component of the Linux kernel. When an input/output I/O error occurs during the journal cleanup process, the system may continue to wait for journal space that cannot be freed. This improper error handling can lead to a system becoming unresponsive or experiencing a...
SUSE CVE-2025-37839
In the Linux kernel, the following vulnerability has been resolved: jbd2: remove wrong sb-ssequence check Journal emptiness is not determined by sb-ssequence == 0 but rather by sb-sstart == 0 which is set a few lines above. Furthermore 0 is a valid transaction ID so the check can spuriously...
DEBIAN-CVE-2025-37839
In the Linux kernel, the following vulnerability has been resolved: jbd2: remove wrong sb-ssequence check Journal emptiness is not determined by sb-ssequence == 0 but rather by sb-sstart == 0 which is set a few lines above. Furthermore 0 is a valid transaction ID so the check can spuriously...
CVE-2025-37839
In the Linux kernel, the following vulnerability has been resolved: jbd2: remove wrong sb-ssequence check Journal emptiness is not determined by sb-ssequence == 0 but rather by sb-sstart == 0 which is set a few lines above. Furthermore 0 is a valid transaction ID so the check can spuriously...
UBUNTU-CVE-2025-37839
In the Linux kernel, the following vulnerability has been resolved: jbd2: remove wrong sb-ssequence check Journal emptiness is not determined by sb-ssequence == 0 but rather by sb-sstart == 0 which is set a few lines above. Furthermore 0 is a valid transaction ID so the check can spuriously...
CVE-2025-37839
CVE-2025-37839 (Linux kernel) fixes a journal-related logic flaw in jbd2. The root cause was the incorrect use of sb->s_sequence to determine journal emptiness; it should rely on sb->s_start, which is set earlier. Since 0 is a valid transaction ID, the previous check could spuriously trigge...
CVE-2023-53091
In the Linux kernel, the following vulnerability has been resolved: ext4: update sjournalinum if it changes after journal replay When mounting a crafted ext4 image, sjournalinum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the...
SUSE CVE-2023-53091
In the Linux kernel, the following vulnerability has been resolved: ext4: update sjournalinum if it changes after journal replay When mounting a crafted ext4 image, sjournalinum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the...
DEBIAN-CVE-2023-53091
In the Linux kernel, the following vulnerability has been resolved: ext4: update sjournalinum if it changes after journal replay When mounting a crafted ext4 image, sjournalinum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the...
CVE-2023-53091
In the Linux kernel, the following vulnerability has been resolved: ext4: update sjournalinum if it changes after journal replay When mounting a crafted ext4 image, sjournalinum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the...
UBUNTU-CVE-2023-53091
In the Linux kernel, the following vulnerability has been resolved: ext4: update sjournalinum if it changes after journal replay When mounting a crafted ext4 image, sjournalinum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the...
CVE-2023-53091 ext4: update s_journal_inum if it changes after journal replay
In the Linux kernel, the following vulnerability has been resolved: ext4: update sjournalinum if it changes after journal replay When mounting a crafted ext4 image, sjournalinum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the...
CVE-2023-53091
CVE-2023-53091 is an ext4 kernel issue fixed in EulerOS kernel advisories. When mounting a crafted ext4 image, s_journal_inum may change after journal replay, which could bypass checks in ext4_get_journal and trigger a null pointer dereference. The patch resolves this by ignoring the inum change ...
CVE-2023-53091 ext4: update s_journal_inum if it changes after journal replay
In the Linux kernel, the following vulnerability has been resolved: ext4: update sjournalinum if it changes after journal replay When mounting a crafted ext4 image, sjournalinum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the...
CVE-2023-53091: NULL Pointer Dereference
In the Linux kernel, the following vulnerability has been resolved: ext4: update sjournalinum if it changes after journal replay When mounting a crafted ext4 image, sjournalinum may change after journal replay, which is obviously unreasonable because we have successfully loaded and replayed the...
ocfs2 Heap Buffer Overflow DoS
The vulnerability of the ocfs2journalshutdown function in the ocfs2 component of the Linux operating system is related to the assignment of the NULL pointer. Exploiting this vulnerability could allow an attacker to cause a service failure...
Linux kernel 安全漏洞
Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in Linux kernel that stems from ext4 not updating sjournalinum after log replay...