CVSS: 7.8EPSS: %CPEs: 3EXPL: 0CVE-2024-49568 – net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg
https://notcve.org/view.php?id=CVE-2024-49568
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg When receiving proposal msg in server, the fields v2_ext_offset/ eid_cnt/ism_gid_cnt in proposal msg are from the remote client and can not be fully trusted. Especially the field v2_ext_offset, once exceed the max value, there has the chance to access wrong address, and crash may happen. This patch checks the fields v2_ext_offset/eid_cnt/ism_gid_cnt before using th... • https://git.kernel.org/stable/c/8c3dca341aea885249e08856c4380300b75d2cf5 •
CVSS: 7.8EPSS: %CPEs: 5EXPL: 0CVE-2024-47408 – net/smc: check smcd_v2_ext_offset when receiving proposal msg
https://notcve.org/view.php?id=CVE-2024-47408
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: net/smc: check smcd_v2_ext_offset when receiving proposal msg When receiving proposal msg in server, the field smcd_v2_ext_offset in proposal msg is from the remote client and can not be fully trusted. Once the value of smcd_v2_ext_offset exceed the max value, there has the chance to access wrong address, and crash may happen. This patch checks the value of smcd_v2_ext_offset before using it. In the Linux kernel, the following vulnerability... • https://git.kernel.org/stable/c/5c21c4ccafe85906db809de3af391fd434df8a27 •
CVSS: 7.8EPSS: %CPEs: 4EXPL: 0CVE-2024-46896 – drm/amdgpu: don't access invalid sched
https://notcve.org/view.php?id=CVE-2024-46896
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: don't access invalid sched Since 2320c9e6a768 ("drm/sched: memset() 'job' in drm_sched_job_init()") accessing job->base.sched can produce unexpected results as the initialisation of (*job)->base.sched done in amdgpu_job_alloc is overwritten by the memset. This commit fixes an issue when a CS would fail validation and would be rejected after job->num_ibs is incremented. In this case, amdgpu_ib_free(ring->adev, ...) will be called... • https://git.kernel.org/stable/c/166df51487f46b6e997dfeea7ca0c2a970853f07 •
CVSS: 6.0EPSS: %CPEs: 2EXPL: 0CVE-2024-55642 – block: Prevent potential deadlocks in zone write plug error recovery
https://notcve.org/view.php?id=CVE-2024-55642
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: block: Prevent potential deadlocks in zone write plug error recovery Zone write plugging for handling writes to zones of a zoned block device always execute a zone report whenever a write BIO to a zone fails. The intent of this is to ensure that the tracking of a zone write pointer is always correct to ensure that the alignment to a zone write pointer of write BIOs can be checked on submission and that we can always correctly emulate zone a... • https://git.kernel.org/stable/c/dd291d77cc90eb6a86e9860ba8e6e38eebd57d12 •
CVSS: 7.8EPSS: %CPEs: 2EXPL: 0CVE-2024-55641 – xfs: unlock inodes when erroring out of xfs_trans_alloc_dir
https://notcve.org/view.php?id=CVE-2024-55641
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: xfs: unlock inodes when erroring out of xfs_trans_alloc_dir Debugging a filesystem patch with generic/475 caused the system to hang after observing the following sequences in dmesg: XFS (dm-0): metadata I/O error in "xfs_imap_to_bp+0x61/0xe0 [xfs]" at daddr 0x491520 len 32 error 5 XFS (dm-0): metadata I/O error in "xfs_btree_read_buf_block+0xba/0x160 [xfs]" at daddr 0x3445608 len 8 error 5 XFS (dm-0): metadata I/O error in "xfs_imap_to_bp+0... • https://git.kernel.org/stable/c/bd5562111d58392298a3c3b93caad71dff681b4b •
CVSS: 7.1EPSS: %CPEs: 3EXPL: 0CVE-2024-55639 – net: renesas: rswitch: avoid use-after-put for a device tree node
https://notcve.org/view.php?id=CVE-2024-55639
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: net: renesas: rswitch: avoid use-after-put for a device tree node The device tree node saved in the rswitch_device structure is used at several driver locations. So passing this node to of_node_put() after the first use is wrong. Move of_node_put() for this node to exit paths. In the Linux kernel, the following vulnerability has been resolved: net: renesas: rswitch: avoid use-after-put for a device tree node The device tree node saved in th... • https://git.kernel.org/stable/c/b46f1e5793298c67efc2f1b917350a2cefacf9d6 •
CVSS: 5.5EPSS: %CPEs: 3EXPL: 0CVE-2024-54683 – netfilter: IDLETIMER: Fix for possible ABBA deadlock
https://notcve.org/view.php?id=CVE-2024-54683
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: netfilter: IDLETIMER: Fix for possible ABBA deadlock Deletion of the last rule referencing a given idletimer may happen at the same time as a read of its file in sysfs: | ====================================================== | WARNING: possible circular locking dependency detected | 6.12.0-rc7-01692-g5e9a28f41134-dirty #594 Not tainted | ------------------------------------------------------ | iptables/3303 is trying to acquire lock: | fff... • https://git.kernel.org/stable/c/0902b469bd25065aa0688c3cee6f11744c817e7c •
CVSS: -EPSS: %CPEs: 3EXPL: 0CVE-2024-54460 – Bluetooth: iso: Fix circular lock in iso_listen_bis
https://notcve.org/view.php?id=CVE-2024-54460
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: Bluetooth: iso: Fix circular lock in iso_listen_bis This fixes the circular locking dependency warning below, by releasing the socket lock before enterning iso_listen_bis, to avoid any potential deadlock with hdev lock. [ 75.307983] ====================================================== [ 75.307984] WARNING: possible circular locking dependency detected [ 75.307985] 6.12.0-rc6+ #22 Not tainted [ 75.307987] ----------------------------------... • https://git.kernel.org/stable/c/02171da6e86a73e1b343b36722f5d9d5c04b3539 •
CVSS: 4.8EPSS: %CPEs: 3EXPL: 0CVE-2024-54191 – Bluetooth: iso: Fix circular lock in iso_conn_big_sync
https://notcve.org/view.php?id=CVE-2024-54191
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: Bluetooth: iso: Fix circular lock in iso_conn_big_sync This fixes the circular locking dependency warning below, by reworking iso_sock_recvmsg, to ensure that the socket lock is always released before calling a function that locks hdev. [ 561.670344] ====================================================== [ 561.670346] WARNING: possible circular locking dependency detected [ 561.670349] 6.12.0-rc6+ #26 Not tainted [ 561.670351] -------------... • https://git.kernel.org/stable/c/1360e5b6ce63d63d23223a659ca2bbafa30a53aa •
CVSS: 8.8EPSS: %CPEs: 2EXPL: 0CVE-2024-53689 – block: Fix potential deadlock while freezing queue and acquiring sysfs_lock
https://notcve.org/view.php?id=CVE-2024-53689
11 Jan 2025 — In the Linux kernel, the following vulnerability has been resolved: block: Fix potential deadlock while freezing queue and acquiring sysfs_lock For storing a value to a queue attribute, the queue_attr_store function first freezes the queue (->q_usage_counter(io)) and then acquire ->sysfs_lock. This seems not correct as the usual ordering should be to acquire ->sysfs_lock before freezing the queue. This incorrect ordering causes the following lockdep splat which we are able to reproduce always simply by acce... • https://git.kernel.org/stable/c/af2814149883e2c1851866ea2afcd8eadc040f79 •