https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 19:46:58 +0000 https://vulnerability.circl.lu/vuln/cve-2023-53720 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/mlx5e: Release the label when replacing existing ct entry</p> <p>Cited commit doesn&#39;t release the label mapping when replacing existing ct entry which leads to following memleak report:</p> <p>unreferenced object 0xffff8881854cf280 (size 96): comm &#34;kworker/u48:74&#34;, pid 23093, jiffies 4296664564 (age 175.944s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [&lt;000000002722d368&gt;] __kmalloc+0x4b/0x1c0 [&lt;00000000cc44e18f&gt;] mapping_add+0x6e8/0xc90 [mlx5_core] [&lt;000000003ad942a7&gt;] mlx5_get_label_mapping+0x66/0xe0 [mlx5_core] [&lt;00000000266308ac&gt;] mlx5_tc_ct_entry_create_mod_hdr+0x1c4/0xf50 [mlx5_core] [&lt;000000009a768b4f&gt;] mlx5_tc_ct_entry_add_rule+0x16f/0xaf0 [mlx5_core] [&lt;00000000a178f3e5&gt;] mlx5_tc_ct_block_flow_offload_add+0x10cb/0x1f90 [mlx5_core] [&lt;000000007b46c496&gt;] mlx5_tc_ct_block_flow_offload+0x14a/0x630 [mlx5_core] [&lt;00000000a9a18ac5&gt;] nf_flow_offload_tuple+0x1a3/0x390 [nf_flow_table] [&lt;00000000d0881951&gt;] flow_offload_work_handler+0x257/0xd30 [nf_flow_table] [&lt;000000009e4935a4&gt;] process_one_work+0x7c2/0x13e0 [&lt;00000000f5cd36a7&gt;] worker_thread+0x59d/0xec0 [&lt;00000000baed1daf&gt;] kthread+0x28f/0x330 [&lt;0000000063d282a4&gt;] ret_from_fork+0x1f/0x30</p> <p>Fix the issue by correctly releasing the label mapping.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/mlx5e: Release the label when replacing existing ct entry</p> <p>Cited commit doesn&#39;t release the label mapping when replacing existing ct entry which leads to following memleak report:</p> <p>unreferenced object 0xffff8881854cf280 (size 96): comm &#34;kworker/u48:74&#34;, pid 23093, jiffies 4296664564 (age 175.944s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [&lt;000000002722d368&gt;] __kmalloc+0x4b/0x1c0 [&lt;00000000cc44e18f&gt;] mapping_add+0x6e8/0xc90 [mlx5_core] [&lt;000000003ad942a7&gt;] mlx5_get_label_mapping+0x66/0xe0 [mlx5_core] [&lt;00000000266308ac&gt;] mlx5_tc_ct_entry_create_mod_hdr+0x1c4/0xf50 [mlx5_core] [&lt;000000009a768b4f&gt;] mlx5_tc_ct_entry_add_rule+0x16f/0xaf0 [mlx5_core] [&lt;00000000a178f3e5&gt;] mlx5_tc_ct_block_flow_offload_add+0x10cb/0x1f90 [mlx5_core] [&lt;000000007b46c496&gt;] mlx5_tc_ct_block_flow_offload+0x14a/0x630 [mlx5_core] [&lt;00000000a9a18ac5&gt;] nf_flow_offload_tuple+0x1a3/0x390 [nf_flow_table] [&lt;00000000d0881951&gt;] flow_offload_work_handler+0x257/0xd30 [nf_flow_table] [&lt;000000009e4935a4&gt;] process_one_work+0x7c2/0x13e0 [&lt;00000000f5cd36a7&gt;] worker_thread+0x59d/0xec0 [&lt;00000000baed1daf&gt;] kthread+0x28f/0x330 [&lt;0000000063d282a4&gt;] ret_from_fork+0x1f/0x30</p> <p>Fix the issue by correctly releasing the label mapping.</p> https://vulnerability.circl.lu/vuln/cve-2023-53720