36342 matches found
CVE-2026-17533
The All-in-One WP Migration and Backup WordPress plugin before 7.108 does not restrict its migration import functionality to network administrators on multisite installations, allowing an administrator of a single subsite to execute arbitrary PHP code across the entire network...
CVE-2026-74495
In the Linux kernel, the following vulnerability has been resolved: igbvf: Fix leak in TX DMA error cleanup If an error is encountered while mapping TX buffers, the driver should unmap any buffers already mapped for that skb. Because count is incremented before each frag mapping, it will always...
EUVD-2026-59688
In the Linux kernel, the following vulnerability has been resolved: igbvf: Fix leak in TX DMA error cleanup If an error is encountered while mapping TX buffers, the driver should unmap any buffers already mapped for that skb. Because count is incremented before each frag mapping, it will always...
CVE-2026-74495
CVE-2026-74495 affects the Linux kernel igbvf driver. The issue is a leak in TX DMA error cleanup: when mapping TX buffers, buffers already mapped for a skb must be unmapped. The root cause is an off-by-one error from decrementing the count before the dma_error loop, after the count had been incr...
CVE-2026-74495 igbvf: Fix leak in TX DMA error cleanup
In the Linux kernel, the following vulnerability has been resolved: igbvf: Fix leak in TX DMA error cleanup If an error is encountered while mapping TX buffers, the driver should unmap any buffers already mapped for that skb. Because count is incremented before each frag mapping, it will always...
CVE-2026-74495 igbvf: Fix leak in TX DMA error cleanup
In the Linux kernel, the following vulnerability has been resolved: igbvf: Fix leak in TX DMA error cleanup If an error is encountered while mapping TX buffers, the driver should unmap any buffers already mapped for that skb. Because count is incremented before each frag mapping, it will always...
CVE-2026-74404
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix snpfilterreservedmemregions off-by-one Sashiko notes: regarding the bounds check in snpfilterreservedmemregions called via walkiomemresdesc: does the check if rangelist-numelements 16 + 8 PAGESIZE allow an...
CVE-2026-72339
In the Linux kernel, the following vulnerability has been resolved: qede: fix off-by-one in BD ring consumption on buildskb failure qederxbuildskb and qedetparxbuildskb do not check for a NULL return from qedebuildskb. When it returns NULL under memory pressure, the functions still consume a BD...
CVE-2026-72345
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: LAG, Fix off-by-one in single-FDB error rollback On failure at index i, the reverse cleanup loop in mlx5lagcreatesinglefdb starts from i, so the failed index itself is rolled back. That can operate on uninitialized stat...
CVE-2026-72210
In the Linux kernel, the following vulnerability has been resolved: ntfs: fix off-by-one in mapping pairs decoding bounds checks In ntfsmappingpairsdecompress, attrend points one byte past the end of the attribute record: attrend = u8 attr + le32tocpuattr-length; The two bounds checks validating...
CVE-2026-74404
The CVE-2026-74404 issue affects the Linux kernel crypto/ccp path where snp_filter_reserved_mem_regions() bounds check could lead to an off-by-one heap overflow when constructing the iomem reservation descriptor. Specifically, for range_list->num_elements up to 255, (num_elements * 16 + 8) can...
EUVD-2026-59551
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix snpfilterreservedmemregions off-by-one Sashiko notes: regarding the bounds check in snpfilterreservedmemregions called via walkiomemresdesc: does the check if rangelist-numelements 16 + 8 PAGESIZE allow an...
CVE-2026-74404 crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix snpfilterreservedmemregions off-by-one Sashiko notes: regarding the bounds check in snpfilterreservedmemregions called via walkiomemresdesc: does the check if rangelist-numelements 16 + 8 PAGESIZE allow an...
CVE-2026-74404 crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix snpfilterreservedmemregions off-by-one Sashiko notes: regarding the bounds check in snpfilterreservedmemregions called via walkiomemresdesc: does the check if rangelist-numelements 16 + 8 PAGESIZE allow an...
CVE-2026-72345 net/mlx5: LAG, Fix off-by-one in single-FDB error rollback
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: LAG, Fix off-by-one in single-FDB error rollback On failure at index i, the reverse cleanup loop in mlx5lagcreatesinglefdb starts from i, so the failed index itself is rolled back. That can operate on uninitialized stat...
CVE-2026-72345 net/mlx5: LAG, Fix off-by-one in single-FDB error rollback
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: LAG, Fix off-by-one in single-FDB error rollback On failure at index i, the reverse cleanup loop in mlx5lagcreatesinglefdb starts from i, so the failed index itself is rolled back. That can operate on uninitialized stat...
EUVD-2026-59244
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: LAG, Fix off-by-one in single-FDB error rollback On failure at index i, the reverse cleanup loop in mlx5lagcreatesinglefdb starts from i, so the failed index itself is rolled back. That can operate on uninitialized stat...
CVE-2026-72345
CVE-2026-72345 affects the Linux kernel mlx5 LAG handling. The vulnerability arises in the single-FDB error rollback: on failure at index i, the reverse cleanup loop in mlx5_lag_create_single_fdb() starts from i, risking rollback of the failed index or double-tearing down a rule already self-roll...
CVE-2026-72339 qede: fix off-by-one in BD ring consumption on build_skb failure
In the Linux kernel, the following vulnerability has been resolved: qede: fix off-by-one in BD ring consumption on buildskb failure qederxbuildskb and qedetparxbuildskb do not check for a NULL return from qedebuildskb. When it returns NULL under memory pressure, the functions still consume a BD...