Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
that a slave mount receives propagation from. * A shared-slave mount is a slave mount to a peer group pg1 while also a peer in another peer group pg2. IOW, a peer group may receive propagation from another peer group. If a peer group pg1 is a slave to another peer group pg2 then all peers in peer group pg1 point to the same peer in peer group pg2 via ->mnt_master. IOW, all peers in peer group pg1 appear on the same ->mnt_slave_list. IOW, they cannot be slaves to different peer groups. * A pure slave mount is a slave mount that is a slave to a peer group but is not a peer in another peer group. * A propagation group denotes the set of mounts consisting of a single peer group pg1 and all slave
another peer group. * A propagation group denotes the set of mounts consisting of a single peer group pg1 and all slave mounts and shared-slave mounts that point to a peer in that peer group via ->mnt_master. IOW, all slave mounts such that @slave_mnt->mnt_master->mnt_group_id is equal to @shared_mnt->mnt_group_id. The concept of a propagation group makes it easier to talk about a single propagation level in a propagation tree. For example, in propagate_mnt() the immediate peers of @dest_mnt and all slaves of @dest_mnt's peer group form a propagation group pr ---truncated--- References: - https://git.kernel.org/stable/c/cad0d17fb2b0540180ab59e2cd48ad348cc1ee4c - https://git.kernel.org/stabl
-- References: - https://git.kernel.org/stable/c/cad0d17fb2b0540180ab59e2cd48ad348cc1ee4c - https://git.kernel.org/stable/c/cc997490be65da0af8c75a6244fc80bb66c53ce0 - https://git.kernel.org/stable/c/7f57df69de7f05302fad584eb8e3f34de39e0311 - https://git.kernel.org/stable/c/2dae4211b579ce98985876a73a78466e285238ff - https://git.kernel.org/stable/c/b591b2919d018ef91b4a9571edca94105bcad3df - https://git.kernel.org/stable/c/c24cc476acd8bccb5af54849aac5e779d8223bf5 - https://git.kernel.org/stable/c/e7c9f10c44a8919cd8bbd51b228c84d0caf7d518 - https://git.kernel.org/stable/c/784a4f995ee24460aa72e00b085612fad57ebce5 - https://git.kernel.org/stable/c/11933cf1d91d57da9e5c53822a540bbdc2656c16
CVE ID: CVE-2022-50281 State: PUBLISHED Published: 2025-09-15T14:21:17.759Z Last Updated: 2025-09-15T14:21:17.759Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: MIPS: SGI-IP27: Fix platform-device leak in bridge_platform_create() In error case in bridge_platform_create after calling platform_device_add()/platform_device_add_data()/ platform_device_add_resources(), release the failed 'pdev' or it will be leak, call platform_device_put() to fix this problem. Besides, 'pdev' is divided into 'pdev_wd' and 'pdev_bd', use platform_device_unregister() to release sgi_w1 resources when xtalk-bridge registration fails. References: - htt
d', use platform_device_unregister() to release sgi_w1 resources when xtalk-bridge registration fails. References: - https://git.kernel.org/stable/c/da2aecef866b476438d02c662507a0e4e818da9d - https://git.kernel.org/stable/c/93296e7ab774230b7c36541dead10b6da39b650f - https://git.kernel.org/stable/c/d7ac29e60d0ff71e9e414af595b8c92800f7fa90 - https://git.kernel.org/stable/c/48025893b3e31b917ad654d28d23fff66681cac4 - https://git.kernel.org/stable/c/11bec9cba4de06b3c0e9e4041453c2caaa1cbec1
CVE ID: CVE-2022-50282 State: PUBLISHED Published: 2025-09-15T14:21:18.658Z Last Updated: 2025-09-15T14:21:18.658Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: chardev: fix error handling in cdev_device_add() While doing fault injection test, I got the following report: ------------[ cut here ]------------ kobject: '(null)' (0000000039956980): is not initialized, yet kobject_put() is being called. WARNING: CPU: 3 PID: 6306 at kobject_put+0x23d/0x4e0 CPU: 3 PID: 6306 Comm: 283 Tainted: G W 6.1.0-rc2-00005-g307c1086d7c9 #1253 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:kobj
7c1086d7c9 #1253 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:kobject_put+0x23d/0x4e0 Call Trace: <TASK> cdev_device_add+0x15e/0x1b0 __iio_device_register+0x13b4/0x1af0 [industrialio] __devm_iio_device_register+0x22/0x90 [industrialio] max517_probe+0x3d8/0x6b4 [max517] i2c_device_probe+0xa81/0xc00 When device_add() is injected fault and returns error, if dev->devt is not set, cdev_add() is not called, cdev_del() is not needed. Fix this by checking dev->devt in error path. References: - https://git.kernel.org/stable/c/5d2146889fad4cb9e6c13e790d4cfd871486eca8 - https://git.kernel.org/stable/c/6acf8597c5b04f455ee0649e11e5f3bcd28f381e - https
146889fad4cb9e6c13e790d4cfd871486eca8 - https://git.kernel.org/stable/c/6acf8597c5b04f455ee0649e11e5f3bcd28f381e - https://git.kernel.org/stable/c/34d17b39bceef25e4cf9805cd59250ae05d0a139 - https://git.kernel.org/stable/c/d85b5247a79355b8432bfd9ac871f96117f750d4 - https://git.kernel.org/stable/c/c46db6088bccff5115674d583fef46ede80077a2 - https://git.kernel.org/stable/c/28dc61cc49c6e995121c6d86bef4b73df78dda80 - https://git.kernel.org/stable/c/b5de1eac71fec1af7723f1083d23a24789fd795c - https://git.kernel.org/stable/c/85a5660491b507d33662b8e81c142e6041e642eb - https://git.kernel.org/stable/c/11fa7fefe3d8fac7da56bc9aa3dd5fb3081ca797
CVE ID: CVE-2022-50283 State: PUBLISHED Published: 2025-09-15T14:21:19.574Z Last Updated: 2025-09-15T14:21:19.574Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mtd: core: add missing of_node_get() in dynamic partitions code This fixes unbalanced of_node_put(): [ 1.078910] 6 cmdlinepart partitions found on MTD device gpmi-nand [ 1.085116] Creating 6 MTD partitions on "gpmi-nand": [ 1.090181] 0x000000000000-0x000008000000 : "nandboot" [ 1.096952] 0x000008000000-0x000009000000 : "nandfit" [ 1.103547] 0x000009000000-0x00000b000000 : "nandkernel" [ 1.110317] 0x00000b000000-0x00000c000000 : "nanddtb" [ 1.115525] ------------[ cut h
0000-0x00000b000000 : "nandkernel" [ 1.110317] 0x00000b000000-0x00000c000000 : "nanddtb" [ 1.115525] ------------[ cut here ]------------ [ 1.120141] refcount_t: addition on 0; use-after-free. [ 1.125328] WARNING: CPU: 0 PID: 1 at lib/refcount.c:25 refcount_warn_saturate+0xdc/0x148 [ 1.133528] Modules linked in: [ 1.136589] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.0.0-rc7-next-20220930-04543-g8cf3f7 [ 1.146342] Hardware name: Freescale i.MX8DXL DDR3L EVK (DT) [ 1.151999] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1.158965] pc : refcount_warn_saturate+0xdc/0x148 [ 1.163760] lr : refcount_warn_saturate+0xdc/0x148 [ 1.168556] sp : ffff800009ddb080 [ 1.171866] x29: ffff
te+0xdc/0x148 [ 1.163760] lr : refcount_warn_saturate+0xdc/0x148 [ 1.168556] sp : ffff800009ddb080 [ 1.171866] x29: ffff800009ddb080 x28: ffff800009ddb35a x27: 0000000000000002 [ 1.179015] x26: ffff8000098b06ad x25: ffffffffffffffff x24: ffff0a00ffffff05 [ 1.186165] x23: ffff00001fdf6470 x22: ffff800009ddb367 x21: 0000000000000000 [ 1.193314] x20: ffff00001fdfebe8 x19: ffff00001fdfec50 x18: ffffffffffffffff [ 1.200464] x17: 0000000000000000 x16: 0000000000000118 x15: 0000000000000004 [ 1.207614] x14: 0000000000000fff x13: ffff800009bca248 x12: 0000000000000003 [ 1.214764] x11: 00000000ffffefff x10: c0000000ffffefff x9 : 4762cb2ccb52de00 [ 1.221914] x8 : 4762cb2ccb52de00 x7 : 205d313431303231
11: 00000000ffffefff x10: c0000000ffffefff x9 : 4762cb2ccb52de00 [ 1.221914] x8 : 4762cb2ccb52de00 x7 : 205d313431303231 x6 : 312e31202020205b [ 1.229063] x5 : ffff800009d55c1f x4 : 0000000000000001 x3 : 0000000000000000 [ 1.236213] x2 : 0000000000000000 x1 : ffff800009954be6 x0 : 000000000000002a [ 1.243365] Call trace: [ 1.245806] refcount_warn_saturate+0xdc/0x148 [ 1.250253] kobject_get+0x98/0x9c [ 1.253658] of_node_get+0x20/0x34 [ 1.257072] of_fwnode_get+0x3c/0x54 [ 1.260652] fwnode_get_nth_parent+0xd8/0xf4 [ 1.264926] fwnode_full_name_string+0x3c/0xb4 [ 1.269373] device_node_string+0x498/0x5b4 [ 1.273561] pointer+0x41c/0x5d0 [ 1.276793] vsnprintf+0x4d8/0x694 [ 1.280198] vprintk_store+0x
e_node_string+0x498/0x5b4 [ 1.273561] pointer+0x41c/0x5d0 [ 1.276793] vsnprintf+0x4d8/0x694 [ 1.280198] vprintk_store+0x164/0x528 [ 1.283951] vprintk_emit+0x98/0x164 [ 1.287530] vprintk_default+0x44/0x6c [ 1.291284] vprintk+0xf0/0x134 [ 1.294428] _printk+0x54/0x7c [ 1.297486] of_node_release+0xe8/0x128 [ 1.301326] kobject_put+0x98/0xfc [ 1.304732] of_node_put+0x1c/0x28 [ 1.308137] add_mtd_device+0x484/0x6d4 [ 1.311977] add_mtd_partitions+0xf0/0x1d0 [ 1.316078] parse_mtd_partitions+0x45c/0x518 [ 1.320439] mtd_device_parse_register+0xb0/0x274 [ 1.325147] gpmi_nand_probe+0x51c/0x650 [ 1.329074] platform_probe+0xa8/0xd0 [ 1.332740] really_probe+0x130/0x334 [ 1.336406] __driver_probe_device+0xb4/
/0x650 [ 1.329074] platform_probe+0xa8/0xd0 [ 1.332740] really_probe+0x130/0x334 [ 1.336406] __driver_probe_device+0xb4/0xe0 [ 1.340681] driver_probe_device+0x3c/0x1f8 [ 1.344869] __driver_attach+0xdc/0x1a4 [ 1.348708] bus_for_each_dev+0x80/0xcc [ 1.352548] driver_attach+0x24/0x30 [ 1.356127] bus_add_driver+0x108/0x1f4 [ 1.359967] driver_register+0x78/0x114 [ 1.363807] __platform_driver_register+0x24/0x30 [ 1.368515] gpmi_nand_driver_init+0x1c/0x28 [ 1.372798] do_one_initcall+0xbc/0x238 [ 1.376638] do_initcall_level+0x94/0xb4 [ 1.380565] do_initcalls+0x54/0x94 [ 1.384058] do_basic_setup+0x1c/0x28 [ 1.387724] kernel_init_freeable+0x110/0x188 [ 1.392084] kernel_init+0x20/0x1a0 [ 1.395578] ret_
o_basic_setup+0x1c/0x28 [ 1.387724] kernel_init_freeable+0x110/0x188 [ 1.392084] kernel_init+0x20/0x1a0 [ 1.395578] ret_from_fork+0x10/0x20 [ 1.399157] ---[ end trace 0000000000000000 ]--- [ 1.403782] ------------[ cut here ]------------ References: - https://git.kernel.org/stable/c/9e54ce00505d291ef88f2c05e5eef46269daf83c - https://git.kernel.org/stable/c/12b58961de0bd88b3c7dfa5d21f6d67f4678b780
CVE ID: CVE-2022-50284 State: PUBLISHED Published: 2025-09-15T14:21:20.612Z Last Updated: 2025-09-15T14:21:20.612Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ipc: fix memory leak in init_mqueue_fs() When setup_mq_sysctls() failed in init_mqueue_fs(), mqueue_inode_cachep is not released. In order to fix this issue, the release path is reordered. References: - https://git.kernel.org/stable/c/86273624a68d07f129dc182b8394f487ed4de484 - https://git.kernel.org/stable/c/28dad915abe46d38c5799a0c8130e9a2a1540385 - https://git.kernel.org/stable/c/12b677f2c697d61e5ddbcb6c1650050a39392f54
CVE ID: CVE-2022-50285 State: PUBLISHED Published: 2025-09-15T14:21:21.504Z Last Updated: 2025-09-15T14:21:21.504Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mm,hugetlb: take hugetlb_lock before decrementing h->resv_huge_pages The h->*_huge_pages counters are protected by the hugetlb_lock, but alloc_huge_page has a corner case where it can decrement the counter outside of the lock. This could lead to a corrupted value of h->resv_huge_pages, which we have observed on our systems. Take the hugetlb_lock before decrementing h->resv_huge_pages to avoid a potential race. References: - https://git.kernel.org/stable/c/3e50a07b6a5fc
e decrementing h->resv_huge_pages to avoid a potential race. References: - https://git.kernel.org/stable/c/3e50a07b6a5fcd39df1534d3fdaca4292a65efe6 - https://git.kernel.org/stable/c/629c986e19fe9481227c7cdfd9a105bbc104d245 - https://git.kernel.org/stable/c/2b35432d324898ec41beb27031d2a1a864a4d40e - https://git.kernel.org/stable/c/11993652d0b49e27272db0a37aa828d8a3a4b92b - https://git.kernel.org/stable/c/568e3812b1778b4c0c229649b59977d88f400ece - https://git.kernel.org/stable/c/112a005d1ded04a4b41b6d01833cc0bda90625cc - https://git.kernel.org/stable/c/c828fab903725279aa9dc6ae3d44bb7e4778f92c - https://git.kernel.org/stable/c/12df140f0bdfae5dcfc81800970dd7f6f632e00c
CVE ID: CVE-2022-50286 State: PUBLISHED Published: 2025-09-15T14:21:22.489Z Last Updated: 2025-09-15T14:21:22.489Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline When converting files with inline data to extents, delayed allocations made on a file system created with both the bigalloc and inline options can result in invalid extent status cache content, incorrect reserved cluster counts, kernel memory leaks, and potential kernel panics. With bigalloc, the code that determines whether a block must be delayed allocated searches the extent tree to see if tha
With bigalloc, the code that determines whether a block must be delayed allocated searches the extent tree to see if that block maps to a previously allocated cluster. If not, the block is delayed allocated, and otherwise, it isn't. However, if the inline option is also used, and if the file containing the block is marked as able to store data inline, there isn't a valid extent tree associated with the file. The current code in ext4_clu_mapped() calls ext4_find_extent() to search the non-existent tree for a previously allocated cluster anyway, which typically finds nothing, as desired. However, a side effect of the search can be to cache invalid content from the non-existent tree (garbage) i
as desired. However, a side effect of the search can be to cache invalid content from the non-existent tree (garbage) in the extent status tree, including bogus entries in the pending reservation tree. To fix this, avoid searching the extent tree when allocating blocks for bigalloc + inline files that are being converted from inline to extent mapped. References: - https://git.kernel.org/stable/c/6f4200ec76a0d31200c308ec5a71c68df5417004 - https://git.kernel.org/stable/c/9404839e0c9db5a517ea83c0ca3388b39d105fdf - https://git.kernel.org/stable/c/d440d6427a5e3a877c1c259b8d2b216ddb65e185 - https://git.kernel.org/stable/c/c0c8edbc8abbe8f16d80a1d794d1ba2c12b6f193 - https://git.kernel.org/stable/c/
6ddb65e185 - https://git.kernel.org/stable/c/c0c8edbc8abbe8f16d80a1d794d1ba2c12b6f193 - https://git.kernel.org/stable/c/81b915181c630ee1cffa052e52874fe4e1ba91ac - https://git.kernel.org/stable/c/131294c35ed6f777bd4e79d42af13b5c41bf2775
CVE ID: CVE-2022-50287 State: PUBLISHED Published: 2025-09-15T14:21:23.403Z Last Updated: 2025-09-15T14:21:23.403Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/i915/bios: fix a memory leak in generate_lfp_data_ptrs When (size != 0 || ptrs->lvds_ entries != 3), the program tries to free() the ptrs. However, the ptrs is not created by calling kzmalloc(), but is obtained by pointer offset operation. This may lead to memory leaks or undefined behavior. Fix this by replacing the arguments of kfree() with ptrs_block. (cherry picked from commit 7674cd0b7d28b952151c3df26bbfa7e07eb2b4ec) References: - https://git.kernel.org/stable
_block. (cherry picked from commit 7674cd0b7d28b952151c3df26bbfa7e07eb2b4ec) References: - https://git.kernel.org/stable/c/4758d04014cfe6cdb6e9b4738d1d6728487bbb3a - https://git.kernel.org/stable/c/7c852e8f93f04e57c1e3883caa72542469c6c4c4 - https://git.kernel.org/stable/c/1382901f75a5a7dc8eac05059fd0c7816def4eae
CVE ID: CVE-2022-50288 State: PUBLISHED Published: 2025-09-15T14:21:24.427Z Last Updated: 2025-09-15T14:21:24.427Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure adapter->dcb would get silently freed inside qlcnic_dcb_enable() in case qlcnic_dcb_attach() would return an error, which always happens under OOM conditions. This would lead to use-after-free because both of the existing callers invoke qlcnic_dcb_get_info() on the obtained pointer, which is potentially freed at that point. Propagate errors from qlcnic_dcb_enable(), and instead free the dcb pointer at
hich is potentially freed at that point. Propagate errors from qlcnic_dcb_enable(), and instead free the dcb pointer at callsite using qlcnic_dcb_free(). This also removes the now unused qlcnic_clear_dcb_ops() helper, which was a simple wrapper around kfree() also causing memory leaks for partially initialized dcb. Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool. References: - https://git.kernel.org/stable/c/36999236f0b12d5de21a6f40e93b570727b9ceb2 - https://git.kernel.org/stable/c/d12a7510293d3370b234b0b7c5eda33e58786768 - https://git.kernel.org/stable/c/8f97eeb02a553cdc78c83a0596448a370e1518c4 - https://git.kernel.org/stable/c/513787ff9a331b461115e
git.kernel.org/stable/c/8f97eeb02a553cdc78c83a0596448a370e1518c4 - https://git.kernel.org/stable/c/513787ff9a331b461115e8a145a983d650a84fcb - https://git.kernel.org/stable/c/95df720e64a6409d8152827a776c43f615e3321a - https://git.kernel.org/stable/c/8df1dc04ce0e4c03b51a756749c250a9cb17d707 - https://git.kernel.org/stable/c/a2a694e6edbdb3efb34e1613a31fdcf6cf444a55 - https://git.kernel.org/stable/c/13a7c8964afcd8ca43c0b6001ebb0127baa95362
CVE ID: CVE-2022-50289 State: PUBLISHED Published: 2025-09-15T14:21:25.275Z Last Updated: 2025-09-15T14:21:25.275Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix memory leak in ocfs2_stack_glue_init() ocfs2_table_header should be free in ocfs2_stack_glue_init() if ocfs2_sysfs_init() failed, otherwise kmemleak will report memleak. BUG: memory leak unreferenced object 0xffff88810eeb5800 (size 128): comm "modprobe", pid 4507, jiffies 4296182506 (age 55.888s) hex dump (first 32 bytes): c0 40 14 a0 ff ff ff ff 00 00 00 00 01 00 00 00 .@.............. 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtra
ff ff 00 00 00 00 01 00 00 00 .@.............. 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<000000001e59e1cd>] __register_sysctl_table+0xca/0xef0 [<00000000c04f70f7>] 0xffffffffa0050037 [<000000001bd12912>] do_one_initcall+0xdb/0x480 [<0000000064f766c9>] do_init_module+0x1cf/0x680 [<000000002ba52db0>] load_module+0x6441/0x6f20 [<000000009772580d>] __do_sys_finit_module+0x12f/0x1c0 [<00000000380c1f22>] do_syscall_64+0x3f/0x90 [<000000004cf473bc>] entry_SYSCALL_64_after_hwframe+0x63/0xcd References: - https://git.kernel.org/stable/c/0000281f019111526f7abccc61f2746d2eb626ca - https://git.kernel.org/stable/c/802abe2bc654e87334e6a0ab6c1adc2b6d5f6394 - https://git
19111526f7abccc61f2746d2eb626ca - https://git.kernel.org/stable/c/802abe2bc654e87334e6a0ab6c1adc2b6d5f6394 - https://git.kernel.org/stable/c/b0822faebd79971617abd495beb2d6f5356b88bf - https://git.kernel.org/stable/c/7c8bf45cea9c8d6fb3e14d8cd5ae60e0372f39b7 - https://git.kernel.org/stable/c/f5f2682d3a34dd8350bf63f232d885fd95f25b92 - https://git.kernel.org/stable/c/61d68cf2ba79128c48d4b3fa4d10c34dc18ba572 - https://git.kernel.org/stable/c/6f6c13776cbee4b6a515f4cd3b859f046be4f6f9 - https://git.kernel.org/stable/c/0b2128b70849f2728949babfc1c760096ef72f5d - https://git.kernel.org/stable/c/13b6269dd022aaa69ca8d1df374ab327504121cf
CVE ID: CVE-2022-50290 State: REJECTED Published: 2025-09-15T14:21:26.335Z Last Updated: 2025-09-16T09:12:18.037Z Description: No description available.
CVE ID: CVE-2022-50291 State: PUBLISHED Published: 2025-09-15T14:45:47.510Z Last Updated: 2025-09-15T14:45:47.510Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: kcm: annotate data-races around kcm->rx_psock kcm->rx_psock can be read locklessly in kcm_rfree(). Annotate the read and writes accordingly. We do the same for kcm->rx_wait in the following patch. syzbot reported: BUG: KCSAN: data-race in kcm_rfree / unreserve_rx_kcm write to 0xffff888123d827b8 of 8 bytes by task 2758 on cpu 1: unreserve_rx_kcm+0x72/0x1f0 net/kcm/kcmsock.c:313 kcm_rcv_strparser+0x2b5/0x3a0 net/kcm/kcmsock.c:373 __strp_recv+0x64c/0xd20 net/strparser/str
x1f0 net/kcm/kcmsock.c:313 kcm_rcv_strparser+0x2b5/0x3a0 net/kcm/kcmsock.c:373 __strp_recv+0x64c/0xd20 net/strparser/strparser.c:301 strp_recv+0x6d/0x80 net/strparser/strparser.c:335 tcp_read_sock+0x13e/0x5a0 net/ipv4/tcp.c:1703 strp_read_sock net/strparser/strparser.c:358 [inline] do_strp_work net/strparser/strparser.c:406 [inline] strp_work+0xe8/0x180 net/strparser/strparser.c:415 process_one_work+0x3d3/0x720 kernel/workqueue.c:2289 worker_thread+0x618/0xa70 kernel/workqueue.c:2436 kthread+0x1a9/0x1e0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 read to 0xffff888123d827b8 of 8 bytes by task 5859 on cpu 0: kcm_rfree+0x14c/0x220 net/kcm/kcmsock.c:181 skb_release
306 read to 0xffff888123d827b8 of 8 bytes by task 5859 on cpu 0: kcm_rfree+0x14c/0x220 net/kcm/kcmsock.c:181 skb_release_head_state+0x8e/0x160 net/core/skbuff.c:841 skb_release_all net/core/skbuff.c:852 [inline] __kfree_skb net/core/skbuff.c:868 [inline] kfree_skb_reason+0x5c/0x260 net/core/skbuff.c:891 kfree_skb include/linux/skbuff.h:1216 [inline] kcm_recvmsg+0x226/0x2b0 net/kcm/kcmsock.c:1161 ____sys_recvmsg+0x16c/0x2e0 ___sys_recvmsg net/socket.c:2743 [inline] do_recvmmsg+0x2f1/0x710 net/socket.c:2837 __sys_recvmmsg net/socket.c:2916 [inline] __do_sys_recvmmsg net/socket.c:2939 [inline] __se_sys_recvmmsg net/socket.c:2932 [inline] __x64_sys_recvmmsg+0xde/0x160 net/socket.c:2932 do_syscal
t.c:2939 [inline] __se_sys_recvmmsg net/socket.c:2932 [inline] __x64_sys_recvmmsg+0xde/0x160 net/socket.c:2932 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd value changed: 0xffff88812971ce00 -> 0x0000000000000000 Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 5859 Comm: syz-executor.3 Not tainted 6.0.0-syzkaller-12189-g19d17ab7c68b-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 References: - https://git.kernel.org/stable/c/13dba69e18d04c8eec7596369f2a0596b0260275 - https://git.kernel.org/stable/c/bf46af730e58d340f6f740bc69a07c5f6b85c65
ble/c/13dba69e18d04c8eec7596369f2a0596b0260275 - https://git.kernel.org/stable/c/bf46af730e58d340f6f740bc69a07c5f6b85c655 - https://git.kernel.org/stable/c/1b8a5692ab25db4ef1c2cc8e5d21f7a65dc3d079 - https://git.kernel.org/stable/c/e94395e916b48a5b912a0a04570981b5b091acb0 - https://git.kernel.org/stable/c/c325f92d8d9b223d5842609ca067e898e9d34566 - https://git.kernel.org/stable/c/342d918cf9a45df9cf11bbe7162b851adefd178f - https://git.kernel.org/stable/c/12a0eb340c9a22e0f8c00d2c0c1a60695ead926a - https://git.kernel.org/stable/c/15e4dabda11b0fa31d510a915d1a580f47dfc92e
CVE ID: CVE-2022-50292 State: PUBLISHED Published: 2025-09-15T14:45:48.427Z Last Updated: 2025-09-15T14:45:48.427Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/msm/dp: fix bridge lifetime Device-managed resources allocated post component bind must be tied to the lifetime of the aggregate DRM device or they will not necessarily be released when binding of the aggregate device is deferred. This can lead resource leaks or failure to bind the aggregate device when binding is later retried and a second attempt to allocate the resources is made. For the DP bridges, previously allocated bridges will leak on probe deferral. Fix t
t to allocate the resources is made. For the DP bridges, previously allocated bridges will leak on probe deferral. Fix this by amending the DP parser interface and tying the lifetime of the bridge device to the DRM device rather than DP platform device. Patchwork: https://patchwork.freedesktop.org/patch/502667/ References: - https://git.kernel.org/stable/c/7eda6977e8058dd45607a5bbc6517a0f42ccd6c9 - https://git.kernel.org/stable/c/16194958f888d63839042d1190f7001e5ddec47b