CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2024-53174 – SUNRPC: make sure cache entry active before cache_show
https://notcve.org/view.php?id=CVE-2024-53174
In the Linux kernel, the following vulnerability has been resolved: SUNRPC: make sure cache entry active before cache_show The function `c_show` was called with protection from RCU. This only ensures that `cp` will not be freed. Therefore, the reference count for `cp` can drop to zero, which will trigger a refcount use-after-free warning when `cache_get` is called. To resolve this issue, use `cache_get_rcu` to ensure that `cp` remains active. ------------[ cut here ]------------ refcount_t: addition on 0; use-after-free. WARNING: CPU: 7 PID: 822 at lib/refcount.c:25 refcount_warn_saturate+0xb1/0x120 CPU: 7 UID: 0 PID: 822 Comm: cat Not tainted 6.12.0-rc3+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 RIP: 0010:refcount_warn_saturate+0xb1/0x120 Call Trace: <TASK> c_show+0x2fc/0x380 [sunrpc] seq_read_iter+0x589/0x770 seq_read+0x1e5/0x270 proc_reg_read+0xe1/0x140 vfs_read+0x125/0x530 ksys_read+0xc1/0x160 do_syscall_64+0x5f/0x170 entry_SYSCALL_64_after_hwframe+0x76/0x7e • https://git.kernel.org/stable/c/e9be26735d055c42543a4d047a769cc6d0fb1504 https://git.kernel.org/stable/c/02999e135b013d85c6df738746e8e24699befee4 https://git.kernel.org/stable/c/c7dac3af57e38b2054f990e573256d90bf887958 https://git.kernel.org/stable/c/068c0b50f3f700b94f78850834cd91ae3b34c2c1 https://git.kernel.org/stable/c/acfaf37888e0f0732fb6a50ff093dce6d99994d0 https://git.kernel.org/stable/c/ec305f303bf070b4f6896b7a76009f702956d402 https://git.kernel.org/stable/c/d882e2b7fad3f5e5fac66184a347f408813f654a https://git.kernel.org/stable/c/2862eee078a4d2d1f584e7f24fa50dddf •
CVSS: -EPSS: 0%CPEs: 9EXPL: 0CVE-2024-53173 – NFSv4.0: Fix a use-after-free problem in the asynchronous open()
https://notcve.org/view.php?id=CVE-2024-53173
In the Linux kernel, the following vulnerability has been resolved: NFSv4.0: Fix a use-after-free problem in the asynchronous open() Yang Erkun reports that when two threads are opening files at the same time, and are forced to abort before a reply is seen, then the call to nfs_release_seqid() in nfs4_opendata_free() can result in a use-after-free of the pointer to the defunct rpc task of the other thread. The fix is to ensure that if the RPC call is aborted before the call to nfs_wait_on_sequence() is complete, then we must call nfs_release_seqid() in nfs4_open_release() before the rpc_task is freed. • https://git.kernel.org/stable/c/24ac23ab88df5b21b5b2df8cde748bf99b289099 https://git.kernel.org/stable/c/1cfae9575296f5040cdc84b0730e79078c081d2d https://git.kernel.org/stable/c/7bf6bf130af8ee7d93a99c28a7512df3017ec759 https://git.kernel.org/stable/c/5237a297ffd374a1c4157a53543b7a69d7bbbc03 https://git.kernel.org/stable/c/2ab9639f16b05d948066a6c4cf19a0fdc61046ff https://git.kernel.org/stable/c/ba6e6c04f60fe52d91520ac4d749d372d4c74521 https://git.kernel.org/stable/c/229a30ed42bb87bcb044c5523fabd9e4f0e75648 https://git.kernel.org/stable/c/e2277a1d9d5cd0d625a4fd7c04fce2b53 •
CVSS: -EPSS: 0%CPEs: 9EXPL: 0CVE-2024-53165 – sh: intc: Fix use-after-free bug in register_intc_controller()
https://notcve.org/view.php?id=CVE-2024-53165
In the Linux kernel, the following vulnerability has been resolved: sh: intc: Fix use-after-free bug in register_intc_controller() In the error handling for this function, d is freed without ever removing it from intc_list which would lead to a use after free. To fix this, let's only add it to the list after everything has succeeded. • https://git.kernel.org/stable/c/2dcec7a988a1895540460a0bf5603bab63d5a3ed https://git.kernel.org/stable/c/3c7c806b3eafd94ae0f77305a174d63b69ec187c https://git.kernel.org/stable/c/d8de818df12d86a1a26a8efd7b4b3b9c6dc3c5cc https://git.kernel.org/stable/c/971b4893457788e0e123ea552f0bb126a5300e61 https://git.kernel.org/stable/c/c3f4f4547fb291982f5ef56c048277c4d5ccc4e4 https://git.kernel.org/stable/c/c43df7dae28fb9fce96ef088250c1e3c3a77c527 https://git.kernel.org/stable/c/b8b84dcdf3ab1d414304819f824b10efba64132c https://git.kernel.org/stable/c/6ba6e19912570b2ad68298be0be1dc779 •
CVSS: -EPSS: 0%CPEs: 9EXPL: 0CVE-2022-49034 – sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
https://notcve.org/view.php?id=CVE-2022-49034
In the Linux kernel, the following vulnerability has been resolved: sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning similar as below when showing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit) instead of NR_CPUS to iterate CPUs. [ 3.052463] ------------[ cut here ]------------ [ 3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0 [ 3.070072] Modules linked in: efivarfs autofs4 [ 3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052 [ 3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000 [ 3.109127] 9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430 [ 3.118774] 90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff [ 3.128412] 0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890 [ 3.138056] 0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa [ 3.147711] ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000 [ 3.157364] 900000000101c998 0000000000000004 9000000000ef7430 0000000000000000 [ 3.167012] 0000000000000009 000000000000006c 0000000000000000 0000000000000000 [ 3.176641] 9000000000d3de08 9000000001639390 90000000002086d8 00007ffff0080286 [ 3.186260] 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c [ 3.195868] ... [ 3.199917] Call Trace: [ 3.203941] [<90000000002086d8>] show_stack+0x38/0x14c [ 3.210666] [<9000000000cf846c>] dump_stack_lvl+0x60/0x88 [ 3.217625] [<900000000023d268>] __warn+0xd0/0x100 [ 3.223958] [<9000000000cf3c90>] warn_slowpath_fmt+0x7c/0xcc [ 3.231150] [<9000000000210220>] show_cpuinfo+0x5e8/0x5f0 [ 3.238080] [<90000000004f578c>] seq_read_iter+0x354/0x4b4 [ 3.245098] [<90000000004c2e90>] new_sync_read+0x17c/0x1c4 [ 3.252114] [<90000000004c5174>] vfs_read+0x138/0x1d0 [ 3.258694] [<90000000004c55f8>] ksys_read+0x70/0x100 [ 3.265265] [<9000000000cfde9c>] do_syscall+0x7c/0x94 [ 3.271820] [<9000000000202fe4>] handle_syscall+0xc4/0x160 [ 3.281824] ---[ end trace 8b484262b4b8c24c ]--- • https://git.kernel.org/stable/c/8fbb57eabfc8ae67115cb47f904614c99d626a89 https://git.kernel.org/stable/c/f8f26cf69003a37ffa947631fc0e6fe6daee624a https://git.kernel.org/stable/c/77755dc95ff2f9a3e473acc1e039f498629949ea https://git.kernel.org/stable/c/e2b91997db286a5dd3cca6d5d9c20004851f22eb https://git.kernel.org/stable/c/2b6b8e011fab680a223b5e07a3c64774156ec6fe https://git.kernel.org/stable/c/09faf32c682ea4a547200b8b9e04d8b3c8e84b55 https://git.kernel.org/stable/c/39373f6f89f52770a5405d30dddd08a27d097872 https://git.kernel.org/stable/c/701e32900683378d93693fec15d133e2c •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2024-53164 – net: sched: fix ordering of qlen adjustment
https://notcve.org/view.php?id=CVE-2024-53164
In the Linux kernel, the following vulnerability has been resolved: net: sched: fix ordering of qlen adjustment Changes to sch->q.qlen around qdisc_tree_reduce_backlog() need to happen _before_ a call to said function because otherwise it may fail to notify parent qdiscs when the child is about to become empty. • https://git.kernel.org/stable/c/489422e2befff88a1de52b2acebe7b333bded025 https://git.kernel.org/stable/c/97e13434b5da8e91bdf965352fad2141d13d72d3 https://git.kernel.org/stable/c/e3e54ad9eff8bdaa70f897e5342e34b76109497f https://git.kernel.org/stable/c/5eb7de8cd58e73851cd37ff8d0666517d9926948 •