Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2022-50452 State: PUBLISHED Published: 2025-10-01T11:45:25.394Z Last Updated: 2025-10-01T11:45:25.394Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: sched: cake: fix null pointer access issue when cake_init() fails When the default qdisc is cake, if the qdisc of dev_queue fails to be inited during mqprio_init(), cake_reset() is invoked to clear resources. In this case, the tins is NULL, and it will cause gpf issue. The process is as follows: qdisc_create_dflt() cake_init() q->tins = kvcalloc(...) --->failed, q->tins is NULL ... qdisc_put() ... cake_reset() ... cake_dequeue_one() b = &q->tins[...] --->q->tins i
...) --->failed, q->tins is NULL ... qdisc_put() ... cake_reset() ... cake_dequeue_one() b = &q->tins[...] --->q->tins is NULL The following is the Call Trace information: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:cake_dequeue_one+0xc9/0x3c0 Call Trace: <TASK> cake_reset+0xb1/0x140 qdisc_reset+0xed/0x6f0 qdisc_destroy+0x82/0x4c0 qdisc_put+0x9e/0xb0 qdisc_create_dflt+0x2c3/0x4a0 mqprio_init+0xa71/0x1760 qdisc_create+0x3eb/0x1000 tc_modify_qdisc+0x408/0x1720 rtnetlink_rcv_msg+0x38e/0xac0 netlink_rcv_skb+0x12d/0x3a0 netlink_unicast+0x4a2/0x740 netli
tc_modify_qdisc+0x408/0x1720 rtnetlink_rcv_msg+0x38e/0xac0 netlink_rcv_skb+0x12d/0x3a0 netlink_unicast+0x4a2/0x740 netlink_sendmsg+0x826/0xcc0 sock_sendmsg+0xc5/0x100 ____sys_sendmsg+0x583/0x690 ___sys_sendmsg+0xe8/0x160 __sys_sendmsg+0xbf/0x160 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7f89e5122d04 </TASK> References: - https://git.kernel.org/stable/c/86aa1390898146f1de277bb6d2a8ed7fc7a43f12 - https://git.kernel.org/stable/c/bc8301ea7e7f1bb9d2ba2fcdf7b5ec2f0792b47e - https://git.kernel.org/stable/c/ae48bee2830bf216800e1447baca39541e27a12e - https://git.kernel.org/stable/c/154f4c06d9dbec1a14e91286c70b6305810302e0 - https://git.kernel.org/stable/c/1dc0a01955
- https://git.kernel.org/stable/c/154f4c06d9dbec1a14e91286c70b6305810302e0 - https://git.kernel.org/stable/c/1dc0a019550fd38ec6cab2d73c90df2bd659c96b - https://git.kernel.org/stable/c/51f9a8921ceacd7bf0d3f47fa867a64988ba1dcb
CVE ID: CVE-2022-50453 State: PUBLISHED Published: 2025-10-01T11:45:26.499Z Last Updated: 2025-10-01T11:45:26.499Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: fix NULL-pointer dereferences There are several places where we can crash the kernel by requesting lines, unbinding the GPIO device, then calling any of the system calls relevant to the GPIO character device's annonymous file descriptors: ioctl(), read(), poll(). While I observed it with the GPIO simulator, it will also happen for any of the GPIO devices that can be hot-unplugged - for instance any HID GPIO expander (e.g. CP2112). This affects both v1 an
f the GPIO devices that can be hot-unplugged - for instance any HID GPIO expander (e.g. CP2112). This affects both v1 and v2 uAPI. This fixes it partially by checking if gdev->chip is not NULL but it doesn't entirely remedy the situation as we still have a race condition in which another thread can remove the device after the check. References: - https://git.kernel.org/stable/c/6d79546622baab843172b52c3af035f83c1b21df - https://git.kernel.org/stable/c/7c755a2d6df511eeb5afba966ac28140f9ea5063 - https://git.kernel.org/stable/c/d66f68ac9e7ba46b6b90fbe25155723f2126088a - https://git.kernel.org/stable/c/ac6ce3cd7a3e10a2e37b8970bab81b4d33d5cfc3 - https://git.kernel.org/stable/c/533aae7c94dbc2b1430
//git.kernel.org/stable/c/ac6ce3cd7a3e10a2e37b8970bab81b4d33d5cfc3 - https://git.kernel.org/stable/c/533aae7c94dbc2b14301cfd68ae7e0e90f0c8438
CVE ID: CVE-2022-50454 State: PUBLISHED Published: 2025-10-01T11:45:27.337Z Last Updated: 2025-10-01T11:45:27.337Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix a use-after-free in nouveau_gem_prime_import_sg_table() nouveau_bo_init() is backed by ttm_bo_init() and ferries its return code back to the caller. On failures, ttm will call nouveau_bo_del_ttm() and free the memory.Thus, when nouveau_bo_init() returns an error, the gem object has already been released. Then the call to nouveau_bo_ref() will use the freed "nvbo->bo" and lead to a use-after-free bug. We should delete the call to nouveau_bo_ref() to avo
f() will use the freed "nvbo->bo" and lead to a use-after-free bug. We should delete the call to nouveau_bo_ref() to avoid the use-after-free. References: - https://git.kernel.org/stable/c/56ee9577915dc06f55309901012a9ef68dbdb5a8 - https://git.kernel.org/stable/c/5d6093c49c098d86c7b136aba9922df44aeb6944 - https://git.kernel.org/stable/c/861f085f81fd569b02cc2c11165a9e6cca144424 - https://git.kernel.org/stable/c/3aeda2fe6517cc52663d4ce3588dd43f0d4124a7 - https://git.kernel.org/stable/c/7d80473e9f12548ac05b36af4fb9ce80f2f73509 - https://git.kernel.org/stable/c/540dfd188ea2940582841c1c220bd035a7db0e51
CVE ID: CVE-2022-50455 State: REJECTED Published: 2025-10-01T11:45:28.159Z Last Updated: 2025-10-10T15:31:02.037Z Description: No description available.
CVE ID: CVE-2022-50456 State: PUBLISHED Published: 2025-10-01T11:45:29.587Z Last Updated: 2025-10-01T11:45:29.587Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix resolving backrefs for inline extent followed by prealloc If a file consists of an inline extent followed by a regular or prealloc extent, then a legitimate attempt to resolve a logical address in the non-inline region will result in add_all_parents reading the invalid offset field of the inline extent. If the inline extent item is placed in the leaf eb s.t. it is the first item, attempting to access the offset field will not only be meaningless, it will go
n the leaf eb s.t. it is the first item, attempting to access the offset field will not only be meaningless, it will go past the end of the eb and cause this panic: [17.626048] BTRFS warning (device dm-2): bad eb member end: ptr 0x3fd4 start 30834688 member offset 16377 size 8 [17.631693] general protection fault, probably for non-canonical address 0x5088000000000: 0000 [#1] SMP PTI [17.635041] CPU: 2 PID: 1267 Comm: btrfs Not tainted 5.12.0-07246-g75175d5adc74-dirty #199 [17.637969] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [17.641995] RIP: 0010:btrfs_get_64+0xe7/0x110 [17.649890] RSP: 0018:ffffc90001f73a08 EFLAGS: 00
uilt.qemu.org 04/01/2014 [17.641995] RIP: 0010:btrfs_get_64+0xe7/0x110 [17.649890] RSP: 0018:ffffc90001f73a08 EFLAGS: 00010202 [17.651652] RAX: 0000000000000001 RBX: ffff88810c42d000 RCX: 0000000000000000 [17.653921] RDX: 0005088000000000 RSI: ffffc90001f73a0f RDI: 0000000000000001 [17.656174] RBP: 0000000000000ff9 R08: 0000000000000007 R09: c0000000fffeffff [17.658441] R10: ffffc90001f73790 R11: ffffc90001f73788 R12: ffff888106afe918 [17.661070] R13: 0000000000003fd4 R14: 0000000000003f6f R15: cdcdcdcdcdcdcdcd [17.663617] FS: 00007f64e7627d80(0000) GS:ffff888237c80000(0000) knlGS:0000000000000000 [17.666525] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [17.668664] CR2: 000055d4a39152e8
) knlGS:0000000000000000 [17.666525] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [17.668664] CR2: 000055d4a39152e8 CR3: 000000010c596002 CR4: 0000000000770ee0 [17.671253] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [17.673634] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [17.676034] PKRU: 55555554 [17.677004] Call Trace: [17.677877] add_all_parents+0x276/0x480 [17.679325] find_parent_nodes+0xfae/0x1590 [17.680771] btrfs_find_all_leafs+0x5e/0xa0 [17.682217] iterate_extent_inodes+0xce/0x260 [17.683809] ? btrfs_inode_flags_to_xflags+0x50/0x50 [17.685597] ? iterate_inodes_from_logical+0xa1/0xd0 [17.687404] iterate_inodes_from_logical+0xa1/0xd0 [17.
ags+0x50/0x50 [17.685597] ? iterate_inodes_from_logical+0xa1/0xd0 [17.687404] iterate_inodes_from_logical+0xa1/0xd0 [17.689121] ? btrfs_inode_flags_to_xflags+0x50/0x50 [17.691010] btrfs_ioctl_logical_to_ino+0x131/0x190 [17.692946] btrfs_ioctl+0x104a/0x2f60 [17.694384] ? selinux_file_ioctl+0x182/0x220 [17.695995] ? __x64_sys_ioctl+0x84/0xc0 [17.697394] __x64_sys_ioctl+0x84/0xc0 [17.698697] do_syscall_64+0x33/0x40 [17.700017] entry_SYSCALL_64_after_hwframe+0x44/0xae [17.701753] RIP: 0033:0x7f64e72761b7 [17.709355] RSP: 002b:00007ffefb067f58 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [17.712088] RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f64e72761b7 [17.714667] RDX: 00007ffefb067fb0
00000010 [17.712088] RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f64e72761b7 [17.714667] RDX: 00007ffefb067fb0 RSI: 00000000c0389424 RDI: 0000000000000003 [17.717386] RBP: 00007ffefb06d188 R08: 000055d4a390d2b0 R09: 00007f64e7340a60 [17.719938] R10: 0000000000000231 R11: 0000000000000246 R12: 0000000000000001 [17.722383] R13: 0000000000000000 R14: 00000000c0389424 R15: 000055d4a38fd2a0 [17.724839] Modules linked in: Fix the bug by detecting the inline extent item in add_all_parents and skipping to the next extent item. References: - https://git.kernel.org/stable/c/c59ee1528b3432ec9dca220567f7eb507820917a - https://git.kernel.org/stable/c/0061ab5153fb8bc574b44fbb773680d0ede48c9c - h
/c59ee1528b3432ec9dca220567f7eb507820917a - https://git.kernel.org/stable/c/0061ab5153fb8bc574b44fbb773680d0ede48c9c - https://git.kernel.org/stable/c/99590f29b2b7567fda2b503aa3d81a0d3e09dce5 - https://git.kernel.org/stable/c/645e2dac6e97f756f28a2f82b2e7bf7f29a68827 - https://git.kernel.org/stable/c/a94b90ac1f251d1007c0c43ee289a61b50f2505f - https://git.kernel.org/stable/c/560840afc3e63bbe5d9c5ef6b2ecf8f3589adff6
CVE ID: CVE-2022-50457 State: PUBLISHED Published: 2025-10-01T11:45:30.263Z Last Updated: 2025-10-01T11:45:30.263Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mtd: core: Fix refcount error in del_mtd_device() del_mtd_device() will call of_node_put() to mtd_get_of_node(mtd), which is mtd->dev.of_node. However, memset(&mtd->dev, 0) is called before of_node_put(). As the result, of_node_put() won't do anything in del_mtd_device(), and causes the refcount leak. del_mtd_device() memset(&mtd->dev, 0, sizeof(mtd->dev) # clear mtd->dev of_node_put() mtd_get_of_node(mtd) # mtd->dev is cleared, can't locate of_node # of_node_put(NULL)
dev) # clear mtd->dev of_node_put() mtd_get_of_node(mtd) # mtd->dev is cleared, can't locate of_node # of_node_put(NULL) won't do anything Fix the error by caching the pointer of the device_node. OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/spi-sram@0 CPU: 3 PID: 275 Comm: python3 Tainted: G N 6.1.0-rc3+ #54 0d8a1edddf51f172ff5226989a7565c6313b08e2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x67/0x83 kobject_get+0x155/0x160 of_node_get+0x1f/0x30 of_fwnode_get+0x43/0x70 fwnode_handle_get+0x
ASK> dump_stack_lvl+0x67/0x83 kobject_get+0x155/0x160 of_node_get+0x1f/0x30 of_fwnode_get+0x43/0x70 fwnode_handle_get+0x54/0x80 fwnode_get_nth_parent+0xc9/0xe0 fwnode_full_name_string+0x3f/0xa0 device_node_string+0x30f/0x750 pointer+0x598/0x7a0 vsnprintf+0x62d/0x9b0 ... cfs_overlay_release+0x30/0x90 config_item_release+0xbe/0x1a0 config_item_put+0x5e/0x80 configfs_rmdir+0x3bd/0x540 vfs_rmdir+0x18c/0x320 do_rmdir+0x198/0x330 __x64_sys_rmdir+0x2c/0x40 do_syscall_64+0x37/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd [<miquel.raynal@bootlin.com>: Light reword of the commit log] References: - https://git.kernel.org/stable/c/f6016557f1ef7735963bd8691592d2797bbf91d2 - https://git.kernel.org/stable/
References: - https://git.kernel.org/stable/c/f6016557f1ef7735963bd8691592d2797bbf91d2 - https://git.kernel.org/stable/c/616dc895d982026f41f500c88d1bfea004938cc8 - https://git.kernel.org/stable/c/56570bdad5e31c5c538cd6efff5c4510256e1bb4
CVE ID: CVE-2022-50458 State: PUBLISHED Published: 2025-10-01T11:45:30.959Z Last Updated: 2025-10-01T11:45:30.959Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: clk: tegra: Fix refcount leak in tegra210_clock_init of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. References: - https://git.kernel.org/stable/c/a19360db83d29bd6b0de4ffad2c815d79246ba99 - https://git.kernel.org/stable/c/e715510adc20a4a07f157ece4e6d068e648a0383 - https://git.kernel.org/stable/c/ac010ec3484ba95c6ab3d946f9a83560005c13c6 -
c/e715510adc20a4a07f157ece4e6d068e648a0383 - https://git.kernel.org/stable/c/ac010ec3484ba95c6ab3d946f9a83560005c13c6 - https://git.kernel.org/stable/c/6d3ac23b952f374017e1a5249d1f03bdbc7f9878 - https://git.kernel.org/stable/c/f487137a53b1a0692211f7ae82c0a7f87c30bdbe - https://git.kernel.org/stable/c/417ed4432b1b40526b1cb50e535d46900505f6d9 - https://git.kernel.org/stable/c/1a6d97139b0a370a9d0809a00e91c41f5bcd3ef1 - https://git.kernel.org/stable/c/f38f34ba1e1029b927b81b9bf9d952f4ed4007bd - https://git.kernel.org/stable/c/56c78cb1f00a9dde8cd762131ce8f4c5eb046fbb
CVE ID: CVE-2022-50459 State: PUBLISHED Published: 2025-10-01T11:45:31.740Z Last Updated: 2025-10-01T11:45:31.740Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername() Fix a NULL pointer crash that occurs when we are freeing the socket at the same time we access it via sysfs. The problem is that: 1. iscsi_sw_tcp_conn_get_param() and iscsi_sw_tcp_host_get_param() take the frwd_lock and do sock_hold() then drop the frwd_lock. sock_hold() does a get on the "struct sock". 2. iscsi_sw_tcp_release_conn() does sockfd_put() which does the last put on the "struct socket" a
on the "struct sock". 2. iscsi_sw_tcp_release_conn() does sockfd_put() which does the last put on the "struct socket" and that does __sock_release() which sets the sock->ops to NULL. 3. iscsi_sw_tcp_conn_get_param() and iscsi_sw_tcp_host_get_param() then call kernel_getpeername() which accesses the NULL sock->ops. Above we do a get on the "struct sock", but we needed a get on the "struct socket". Originally, we just held the frwd_lock the entire time but in commit bcf3a2953d36 ("scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername()") we switched to refcount based because the network layer changed and started taking a mutex in that path, so we could no longer hold the fr
count based because the network layer changed and started taking a mutex in that path, so we could no longer hold the frwd_lock. Instead of trying to maintain multiple refcounts, this just has us use a mutex for accessing the socket in the interface code paths. References: - https://git.kernel.org/stable/c/884a788f065578bb640382279a83d1df433b13e6 - https://git.kernel.org/stable/c/a26b0658751bb0a3b28386fca715333b104d32a2 - https://git.kernel.org/stable/c/897dbbc57d71e8a34ec1af8e573a142de457da38 - https://git.kernel.org/stable/c/0a0b861fce2657ba08ec356a74346b37ca4b2008 - https://git.kernel.org/stable/c/57569c37f0add1b6489e1a1563c71519daf732cf
CVE ID: CVE-2022-50460 State: PUBLISHED Published: 2025-10-01T11:45:32.484Z Last Updated: 2025-10-01T11:45:32.484Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: cifs: Fix xid leak in cifs_flock() If not flock, before return -ENOLCK, should free the xid, otherwise, the xid will be leaked. References: - https://git.kernel.org/stable/c/2d08311aa3056a84bfdc09bc47777de6a9b16c30 - https://git.kernel.org/stable/c/8905d13b9ede4caa88c577faed832d6c7383f4fb - https://git.kernel.org/stable/c/f8c9b4a963fec5d0e37e3e8522bb19b0c28e1a73 - https://git.kernel.org/stable/c/575e079c782b9862ec2626403922d041a42e6ed6
CVE ID: CVE-2022-50461 State: PUBLISHED Published: 2025-10-01T11:45:33.300Z Last Updated: 2025-10-01T11:45:33.300Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: ethernet: ti: am65-cpsw: Fix PM runtime leakage in am65_cpsw_nuss_ndo_slave_open() Ensure pm_runtime_put() is issued in error path. References: - https://git.kernel.org/stable/c/2c14f5cf74c4995eaf284b496481866f012eba19 - https://git.kernel.org/stable/c/a8846b3398600a632696b6cf79f8a44a107eb226 - https://git.kernel.org/stable/c/5821504f5073983733465b8bc430049c4343bbd7
CVE ID: CVE-2022-50462 State: PUBLISHED Published: 2025-10-01T11:45:34.107Z Last Updated: 2025-10-01T11:45:34.107Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: MIPS: vpe-mt: fix possible memory leak while module exiting Afer commit 1fa5ae857bb1 ("driver core: get rid of struct device's bus_id string array"), the name of device is allocated dynamically, it need be freed when module exiting, call put_device() to give up reference, so that it can be freed in kobject_cleanup() when the refcount hit to 0. The vpe_device is static, so remove kfree() from vpe_device_release(). References: - https://git.kernel.org/stable/c/170e9913c2
_device is static, so remove kfree() from vpe_device_release(). References: - https://git.kernel.org/stable/c/170e9913c2ed5cfc37c0adf0fdbd368d2d8d8168 - https://git.kernel.org/stable/c/9d180e0bb21c57bd6cca2adeb672d3b522e910b5 - https://git.kernel.org/stable/c/851ae5640875f06494e40002cd503b11a634c6fb - https://git.kernel.org/stable/c/b3325a443525e3b89151879b834519b21c5e3011 - https://git.kernel.org/stable/c/48d42f4464d713fbdd79f334fdcd6e5be534cc67 - https://git.kernel.org/stable/c/e820a8192ff68570100347855b567512aec43819 - https://git.kernel.org/stable/c/b191dde84e40624d5577f64db0ec922c5c0ec57c - https://git.kernel.org/stable/c/ab3d47c1fd0202821abd473ca87580faafd47847 - https://git.kernel.org
f64db0ec922c5c0ec57c - https://git.kernel.org/stable/c/ab3d47c1fd0202821abd473ca87580faafd47847 - https://git.kernel.org/stable/c/5822e8cc84ee37338ab0bdc3124f6eec04dc232d
CVE ID: CVE-2022-50463 State: PUBLISHED Published: 2025-10-01T11:45:34.858Z Last Updated: 2025-10-01T11:45:34.858Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/52xx: Fix a resource leak in an error handling path The error handling path of mpc52xx_lpbfifo_probe() has a request_irq() that is not balanced by a corresponding free_irq(). Add the missing call, as already done in the remove function. References: - https://git.kernel.org/stable/c/be9caf2c936f15a9c3f9111e62bdde6357312f90 - https://git.kernel.org/stable/c/f4ad0a7f0e78d65d38921ab2bef234e49be78b10 - https://git.kernel.org/stable/c/e4002f293e5b44e57d2930513cca0dff
org/stable/c/f4ad0a7f0e78d65d38921ab2bef234e49be78b10 - https://git.kernel.org/stable/c/e4002f293e5b44e57d2930513cca0dff32249812 - https://git.kernel.org/stable/c/9bf842ffdd216b9f94d5b051b5d8b815f2426538 - https://git.kernel.org/stable/c/40b4be399e0db7073dec5a0de5ca9994f7e31e58 - https://git.kernel.org/stable/c/0accd460dc7bbe5f55e41a8867c63db9d07b3ec8 - https://git.kernel.org/stable/c/cbda93665a3857324f5c79e45769a83c78183199 - https://git.kernel.org/stable/c/fb3ef6a5af4b003502c940ea50c0f55b06ebbfc9 - https://git.kernel.org/stable/c/5836947613ef33d311b4eff6a32d019580a214f5
CVE ID: CVE-2022-50464 State: PUBLISHED Published: 2025-10-01T11:45:35.878Z Last Updated: 2025-10-01T11:45:35.878Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mt76: mt7915: Fix PCI device refcount leak in mt7915_pci_init_hif2() As comment of pci_get_device() says, it returns a pci_device with its refcount increased. We need to call pci_dev_put() to decrease the refcount. Save the return value of pci_get_device() and call pci_dev_put() to decrease the refcount. References: - https://git.kernel.org/stable/c/8abc6579667129afd13ff2ccb0319ba3f46e6995 - https://git.kernel.org/stable/c/2d4b9c7e81f3a4df27749ebecb426b145e68be2a - htt
abc6579667129afd13ff2ccb0319ba3f46e6995 - https://git.kernel.org/stable/c/2d4b9c7e81f3a4df27749ebecb426b145e68be2a - https://git.kernel.org/stable/c/5938196cc188ba4323bc6357f5ac55127d715888
CVE ID: CVE-2022-50465 State: PUBLISHED Published: 2025-10-01T11:45:36.647Z Last Updated: 2025-10-01T11:45:36.647Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ext4: fix leaking uninitialized memory in fast-commit journal When space at the end of fast-commit journal blocks is unused, make sure to zero it out so that uninitialized memory is not leaked to disk. References: - https://git.kernel.org/stable/c/b8b7922374b00a44137e5bcdd46ef86c8b065f27 - https://git.kernel.org/stable/c/871800770d7f2f952c7249ad52485c3564dab44e - https://git.kernel.org/stable/c/d9ba03eb03dc2dccb5450de388ea46bdcaaf8348 - https://git.kernel.org/stable/c/
3564dab44e - https://git.kernel.org/stable/c/d9ba03eb03dc2dccb5450de388ea46bdcaaf8348 - https://git.kernel.org/stable/c/7c1fb65e8ce85c281d2cba9c236f9edbbc4eaca6 - https://git.kernel.org/stable/c/594bc43b410316d70bb42aeff168837888d96810
CVE ID: CVE-2022-50466 State: PUBLISHED Published: 2025-10-01T11:45:37.376Z Last Updated: 2025-10-01T11:45:37.376Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: fs/binfmt_elf: Fix memory leak in load_elf_binary() There is a memory leak reported by kmemleak: unreferenced object 0xffff88817104ef80 (size 224): comm "xfs_admin", pid 47165, jiffies 4298708825 (age 1333.476s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 60 a8 b3 00 81 88 ff ff a8 10 5a 00 81 88 ff ff `.........Z..... backtrace: [<ffffffff819171e1>] __alloc_file+0x21/0x250 [<ffffffff81918061>] alloc_empty_file+0x41/0xf0
.........Z..... backtrace: [<ffffffff819171e1>] __alloc_file+0x21/0x250 [<ffffffff81918061>] alloc_empty_file+0x41/0xf0 [<ffffffff81948cda>] path_openat+0xea/0x3d30 [<ffffffff8194ec89>] do_filp_open+0x1b9/0x290 [<ffffffff8192660e>] do_open_execat+0xce/0x5b0 [<ffffffff81926b17>] open_exec+0x27/0x50 [<ffffffff81a69250>] load_elf_binary+0x510/0x3ed0 [<ffffffff81927759>] bprm_execve+0x599/0x1240 [<ffffffff8192a997>] do_execveat_common.isra.0+0x4c7/0x680 [<ffffffff8192b078>] __x64_sys_execve+0x88/0xb0 [<ffffffff83bbf0a5>] do_syscall_64+0x35/0x80 If "interp_elf_ex" fails to allocate memory in load_elf_binary(), the program will take the "out_free_ph" error handing path, resulting in "interpreter"
ate memory in load_elf_binary(), the program will take the "out_free_ph" error handing path, resulting in "interpreter" file resource is not released. Fix it by adding an error handing path "out_free_file", which will release the file resource when "interp_elf_ex" failed to allocate memory. References: - https://git.kernel.org/stable/c/706215300411d48db6b51a5832b872632a84bbc1 - https://git.kernel.org/stable/c/265b6fb780f57d10449a40e94219b28fa52479cc - https://git.kernel.org/stable/c/acd9b4914f1c5928c7ae8ebc623d6291eb1a573a - https://git.kernel.org/stable/c/594d2a14f2168c09b13b114c3d457aa939403e52
CVE ID: CVE-2022-50467 State: PUBLISHED Published: 2025-10-01T11:45:38.110Z Last Updated: 2025-10-01T11:45:38.110Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix null ndlp ptr dereference in abnormal exit path for GFT_ID An error case exit from lpfc_cmpl_ct_cmd_gft_id() results in a call to lpfc_nlp_put() with a null pointer to a nodelist structure. Changed lpfc_cmpl_ct_cmd_gft_id() to initialize nodelist pointer upon entry. References: - https://git.kernel.org/stable/c/04e7cd8c85636a329d1a6e5a269a7c8b6f71c41c - https://git.kernel.org/stable/c/82dc1fe4324e2c897f2ed1c66f4fcff03094ac3a - https://git.kernel.org/sta
269a7c8b6f71c41c - https://git.kernel.org/stable/c/82dc1fe4324e2c897f2ed1c66f4fcff03094ac3a - https://git.kernel.org/stable/c/59b7e210a522b836a01516c71ee85d1d92c1f075