4079 matches found
UBUNTU-CVE-2025-21722
In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if buffer is referenced Patch series "nilfs2: protect busy buffer heads from being force-cleared". This series fixes the buffer head state inconsistency issues reported by syzbot that occurs when...
CVE-2025-21722 nilfs2: do not force clear folio if buffer is referenced
In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if buffer is referenced Patch series "nilfs2: protect busy buffer heads from being force-cleared". This series fixes the buffer head state inconsistency issues reported by syzbot that occurs when...
CVE-2025-21722 nilfs2: do not force clear folio if buffer is referenced
In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if buffer is referenced Patch series "nilfs2: protect busy buffer heads from being force-cleared". This series fixes the buffer head state inconsistency issues reported by syzbot that occurs when...
CVE-2025-21722
CVE-2025-21722 concerns the NILFS2 filesystem in the Linux kernel. When filesystem corruption triggers a read-only fallback, buffer state inconsistencies can occur: one path is when mark_buffer_dirty() marks data/metadata dirty but the buffer isn’t uptodate, and another path is nilfs_btree_propag...
CVE-2025-21722 nilfs2: do not force clear folio if buffer is referenced
In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if buffer is referenced Patch series "nilfs2: protect busy buffer heads from being force-cleared". This series fixes the buffer head state inconsistency issues reported by syzbot that occurs when...
CVE-2025-21722
In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if buffer is referenced Patch series "nilfs2: protect busy buffer heads from being force-cleared". This series fixes the buffer head state inconsistency issues reported by syzbot that occurs when...
CVE-2024-54957
Nagios XI version 2024R1.2.2 is susceptible to an open redirect flaw located on the Tools page . This vulnerability can be exploited by users with read-only permissions to craft malicious links that redirect other users to arbitrary external URLs without their consent. As a temporary workaround, ...
CVE-2024-54957
Nagios XI 2024R1.2.2 is vulnerable to an open redirect flaw on the Tools page, exploitable by users with read-only permissions. This vulnerability allows an attacker to craft a malicious link that redirects users to an arbitrary external URL without their consent...
CVE-2024-54957
Nagios XI 2024R1.2.2 is vulnerable to an open redirect flaw on the Tools page, exploitable by users with read-only permissions. This vulnerability allows an attacker to craft a malicious link that redirects users to an arbitrary external URL without their consent...
CVE-2024-54957: URL Redirection to Untrusted Site
Nagios XI 2024R1.2.2 is vulnerable to an open redirect flaw on the Tools page, exploitable by users with read-only permissions. This vulnerability allows an attacker to craft a malicious link that redirects users to an arbitrary external URL without their consent...
CVE-2025-21722: Use After Free
In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if buffer is referenced Patch series "nilfs2: protect busy buffer heads from being force-cleared". This series fixes the buffer head state inconsistency issues reported by syzbot that occurs when...
PT-2025-8984
Name of the Vulnerable Software and Affected Versions Nagios XI version 2024R1.2.2 Description The issue is an open redirect flaw located on the Tools page, which can be exploited by users with read-only permissions. This allows an attacker to craft a malicious link that redirects users to an...
AZL-67682 CVE-2022-49178 affecting package kernel 5.15.200.1-1
In the Linux kernel, the following vulnerability has been resolved: memstick/msproblock: fix handling of read-only devices Use setdiskro to propagate the read-only state to the block layer instead of checking for it in -open and leaking a reference in case of a read-only device...
DEBIAN-CVE-2022-49178
In the Linux kernel, the following vulnerability has been resolved: memstick/msproblock: fix handling of read-only devices Use setdiskro to propagate the read-only state to the block layer instead of checking for it in -open and leaking a reference in case of a read-only device...
CVE-2022-49178
In the Linux kernel, the following vulnerability has been resolved: memstick/msproblock: fix handling of read-only devices Use setdiskro to propagate the read-only state to the block layer instead of checking for it in -open and leaking a reference in case of a read-only device...
UBUNTU-CVE-2022-49178
In the Linux kernel, the following vulnerability has been resolved: memstick/msproblock: fix handling of read-only devices Use setdiskro to propagate the read-only state to the block layer instead of checking for it in -open and leaking a reference in case of a read-only device...
CVE-2022-49178 memstick/mspro_block: fix handling of read-only devices
In the Linux kernel, the following vulnerability has been resolved: memstick/msproblock: fix handling of read-only devices Use setdiskro to propagate the read-only state to the block layer instead of checking for it in -open and leaking a reference in case of a read-only device...
CVE-2022-49178 memstick/mspro_block: fix handling of read-only devices
In the Linux kernel, the following vulnerability has been resolved: memstick/msproblock: fix handling of read-only devices Use setdiskro to propagate the read-only state to the block layer instead of checking for it in -open and leaking a reference in case of a read-only device...
CVE-2022-49178
CVE-2022-49178 affects the Linux kernel memstick driver (memstick/mspro_block). The issue relates to how read-only devices are handled in the mspro_block code path. Root cause: improper propagation of the read-only state through the block layer during open, leading to a potential reference leak w...
CVE-2022-49178
In the Linux kernel, the following vulnerability has been resolved: memstick/msproblock: fix handling of read-only devices Use setdiskro to propagate the read-only state to the block layer instead of checking for it in -open and leaking a reference in case of a read-only device...