CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2022-49177 – hwrng: cavium - fix NULL but dereferenced coccicheck error
https://notcve.org/view.php?id=CVE-2022-49177
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: hwrng: cavium - fix NULL but dereferenced coccicheck error Fix following coccicheck warning: ./drivers/char/hw_random/cavium-rng-vf.c:182:17-20: ERROR: pdev is NULL but dereferenced. • https://git.kernel.org/stable/c/e47b12f9415169eceda6770fcf45802e0c8d2a66 •
CVSS: -EPSS: %CPEs: 7EXPL: 0CVE-2022-49176 – bfq: fix use-after-free in bfq_dispatch_request
https://notcve.org/view.php?id=CVE-2022-49176
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: bfq: fix use-after-free in bfq_dispatch_request KASAN reports a use-after-free report when doing normal scsi-mq test [69832.239032] ================================================================== [69832.241810] BUG: KASAN: use-after-free in bfq_dispatch_request+0x1045/0x44b0 [69832.243267] Read of size 8 at addr ffff88802622ba88 by task kworker/3:1H/155 [69832.244656] [69832.245007] CPU: 3 PID: 155 Comm: kworker/3:1H Not tainted 5.10.0-1... • https://git.kernel.org/stable/c/74e610b5ee0d95e751280567100509eb11517efa •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2022-49175 – PM: core: keep irq flags in device_pm_check_callbacks()
https://notcve.org/view.php?id=CVE-2022-49175
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: PM: core: keep irq flags in device_pm_check_callbacks() The function device_pm_check_callbacks() can be called under the spin lock (in the reported case it happens from genpd_add_device() -> dev_pm_domain_set(), when the genpd uses spinlocks rather than mutexes. However this function uncoditionally uses spin_lock_irq() / spin_unlock_irq(), thus not preserving the CPU flags. Use the irqsave/irqrestore instead. The backtrace for the reference... • https://git.kernel.org/stable/c/3ec80d52b9b74b9e691997632a543c73eddfeba0 •
CVSS: -EPSS: %CPEs: 5EXPL: 0CVE-2022-49174 – ext4: fix ext4_mb_mark_bb() with flex_bg with fast_commit
https://notcve.org/view.php?id=CVE-2022-49174
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: fix ext4_mb_mark_bb() with flex_bg with fast_commit In case of flex_bg feature (which is by default enabled), extents for any given inode might span across blocks from two different block group. ext4_mb_mark_bb() only reads the buffer_head of block bitmap once for the starting block group, but it fails to read it again when the extent length boundary overflows to another block group. Then in this below loop it accesses memory beyond t... • https://git.kernel.org/stable/c/cd6d719534af993210306f8a13f9cb3e615f7c8d •
CVSS: -EPSS: %CPEs: 3EXPL: 0CVE-2022-49173 – spi: fsi: Implement a timeout for polling status
https://notcve.org/view.php?id=CVE-2022-49173
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: spi: fsi: Implement a timeout for polling status The data transfer routines must poll the status register to determine when more data can be shifted in or out. If the hardware gets into a bad state, these polling loops may never exit. Prevent this by returning an error if a timeout is exceeded. • https://git.kernel.org/stable/c/d4982ceb137e6ecd2b466a6de639790a148cf19a •
CVSS: -EPSS: %CPEs: 3EXPL: 0CVE-2022-49172 – parisc: Fix non-access data TLB cache flush faults
https://notcve.org/view.php?id=CVE-2022-49172
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: parisc: Fix non-access data TLB cache flush faults When a page is not present, we get non-access data TLB faults from the fdc and fic instructions in flush_user_dcache_range_asm and flush_user_icache_range_asm. When these occur, the cache line is not invalidated and potentially we get memory corruption. The problem was hidden by the nullification of the flush instructions. These faults also affect performance. With pa8800/pa8900 processors,... • https://git.kernel.org/stable/c/b3d6adb3a49d82e4e557c5fc16f50c9ff731da5d •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2022-49171 – ext4: don't BUG if someone dirty pages without asking ext4 first
https://notcve.org/view.php?id=CVE-2022-49171
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: don't BUG if someone dirty pages without asking ext4 first [un]pin_user_pages_remote is dirtying pages without properly warning the file system in advance. A related race was noted by Jan Kara in 2018[1]; however, more recently instead of it being a very hard-to-hit race, it could be reliably triggered by process_vm_writev(2) which was discovered by Syzbot[2]. This is technically a bug in mm/gup.c, but arguably ext4 is fragile in that... • https://git.kernel.org/stable/c/5db60e76edf5680ff1f3a7221036fc44b308f146 •
CVSS: -EPSS: %CPEs: 5EXPL: 0CVE-2022-49170 – f2fs: fix to do sanity check on curseg->alloc_type
https://notcve.org/view.php?id=CVE-2022-49170
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on curseg->alloc_type As Wenqing Liu reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215657 - Overview UBSAN: array-index-out-of-bounds in fs/f2fs/segment.c:3460:2 when mount and operate a corrupted image - Reproduce tested on kernel 5.17-rc4, 5.17-rc6 1. mkdir test_crash 2. cd test_crash 3. unzip tmp2.zip 4. mkdir mnt 5. ./single_test.sh f2fs 2 - Kernel dump [ 46.434454] loop0: detected capaci... • https://git.kernel.org/stable/c/498b7088db71f9707359448cd6800bbb1882f4c3 •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2022-49169 – f2fs: use spin_lock to avoid hang
https://notcve.org/view.php?id=CVE-2022-49169
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: f2fs: use spin_lock to avoid hang [14696.634553] task:cat state:D stack: 0 pid:1613738 ppid:1613735 flags:0x00000004 [14696.638285] Call Trace: [14696.639038]
CVSS: -EPSS: %CPEs: 3EXPL: 0CVE-2022-49168 – btrfs: do not clean up repair bio if submit fails
https://notcve.org/view.php?id=CVE-2022-49168
26 Feb 2025 — In the Linux kernel, the following vulnerability has been resolved: btrfs: do not clean up repair bio if submit fails The submit helper will always run bio_endio() on the bio if it fails to submit, so cleaning up the bio just leads to a variety of use-after-free and NULL pointer dereference bugs because we race with the endio function that is cleaning up the bio. Instead just return BLK_STS_OK as the repair function has to continue to process the rest of the pages, and the endio for the repair bio will do t... • https://git.kernel.org/stable/c/e76c78c48902dae6fa612749f59162bca0a79e0b •