Page 108 of 6917 results (0.009 seconds)

CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0

16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: caif: fix memory leak in cfctrl_linkup_request() When linktype is unknown or kzalloc failed in cfctrl_linkup_request(), pkt is not released. Add release process to error path. This update provides the initial livepatch for this kernel update. This update does not contain any fixes and will be updated with livepatches later. • https://git.kernel.org/stable/c/b482cd2053e3b90a7b33a78c63cdb6badf2ec383 • CWE-401: Missing Release of Memory after Effective Lifetime •

CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0

16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: powerpc: Don't try to copy PPR for task with NULL pt_regs powerpc sets up PF_KTHREAD and PF_IO_WORKER with a NULL pt_regs, which from my (arguably very short) checking is not commonly done for other archs. This is fine, except when PF_IO_WORKER's have been created and the task does something that causes a coredump to be generated. Then we get this crash: Kernel attempted to read user page (160) - exploit attempt? (uid: 1000) BUG: Kernel NUL... • https://git.kernel.org/stable/c/fa439810cc1b3c927ec24ede17d02467e1b143a1 • CWE-476: NULL Pointer Dereference •

CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0

16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Don't leak some plane state Apparently no one noticed that mdp5 plane states leak like a sieve ever since we introduced plane_state->commit refcount a few years ago in 21a01abbe32a ("drm/atomic: Fix freeing connector/plane state too early by tracking commits, v3.") Fix it by using the right helpers. Patchwork: https://patchwork.freedesktop.org/patch/551236/ This update provides the initial livepatch for this kernel update. Thi... • https://git.kernel.org/stable/c/21a01abbe32a3cbeb903378a24e504bfd9fe0648 •

CVSS: 7.8EPSS: 0%CPEs: 8EXPL: 0

16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Wait for io return on terminate rport System crash due to use after free. Current code allows terminate_rport_io to exit before making sure all IOs has returned. For FCP-2 device, IO's can hang on in HW because driver has not tear down the session in FW at first sign of cable pull. When dev_loss_tmo timer pops, terminate_rport_io is called and upper layer is about to free various resources. Terminate_rport_io trigger qla to d... • https://git.kernel.org/stable/c/715848ca6fffeb6362a50887d9c26245bd5dfba9 • CWE-416: Use After Free •

CVSS: 7.1EPSS: 0%CPEs: 6EXPL: 0

16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211_hwsim: drop short frames While technically some control frames like ACK are shorter and end after Address 1, such frames shouldn't be forwarded through wmediumd or similar userspace, so require the full 3-address header to avoid accessing invalid memory if shorter frames are passed in. This update provides the initial livepatch for this kernel update. This update does not contain any fixes and will be updated with livepatches... • https://git.kernel.org/stable/c/05d610af3e71a782fa28a1351b687da982d208ee • CWE-1220: Insufficient Granularity of Access Control •

CVSS: 5.5EPSS: 0%CPEs: 10EXPL: 0

16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: recordmcount: Fix memory leaks in the uwrite function Common realloc mistake: 'file_append' nulled but not freed upon failure • https://git.kernel.org/stable/c/a50bd43935586420fb75f4558369eb08566fac5e • CWE-401: Missing Release of Memory after Effective Lifetime •

CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0

16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: fix WARNING in mb_find_extent Syzbot found the following issue: EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioread_nolock, O_DIRECT and fast_commit support! EXT4-fs (loop0): orphan cleanup on readonly fs ------------[ cut here ]------------ WARNING: CPU: 1 PID: 5067 at fs/ext4/mballoc.c:1869 mb_find_extent+0x8a1/0xe30 Modules linked in: CPU: 1 PID: 5067 Comm: syz-executor307 Not tainted 6.2.0-rc1-syzkall... • https://git.kernel.org/stable/c/abcb2947c91130426539f209f7a473a67a1f6663 •

CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0

16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: fbdev/ep93xx-fb: Do not assign to struct fb_info.dev Do not assing the Linux device to struct fb_info.dev. The call to register_framebuffer() initializes the field to the fbdev device. Drivers should not override its value. Fixes a bug where the driver incorrectly decreases the hardware device's reference counter and leaks the fbdev device. v2: * add Fixes tag (Dan) This update provides the initial livepatch for this kernel update. This upd... • https://git.kernel.org/stable/c/88017bda96a5fd568a982b01546c8fb1782dda62 •

CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0

16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix wrong setting of max_corr_read_errors There is no input check when echo md/max_read_errors and overflow might occur. Add check of input number. This update provides the initial livepatch for this kernel update. This update does not contain any fixes and will be updated with livepatches later. • https://git.kernel.org/stable/c/1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d •

CVSS: 7.8EPSS: 0%CPEs: 8EXPL: 0

16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput During unmount process of nilfs2, nothing holds nilfs_root structure after nilfs2 detaches its writer in nilfs_detach_log_writer(). Previously, nilfs_evict_inode() could cause use-after-free read for nilfs_root if inodes are left in "garbage_list" and released by nilfs_dispose_list at the end of nilfs_detach_log_writer(), and this bug was fixed by commit 9b5a04ac3ad9 ("nil... • https://git.kernel.org/stable/c/0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 • CWE-416: Use After Free •