CVE-2023-53720

  • Published: 2025-10-22T14:15:46.700
  • Last modified: 1761167568

In the Linux kernel, the following vulnerability has been resolved:

net/mlx5e: Release the label when replacing existing ct entry

Cited commit doesn’t release the label mapping when replacing existing ct
entry which leads to following memleak report:

unreferenced object 0xffff8881854cf280 (size 96):
comm “kworker/u48:74”, 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:
[] __kmalloc+0x4b/0x1c0
[] mapping_add+0x6e8/0xc90 [mlx5_core]
[] mlx5_get_label_mapping+0x66/0xe0 [mlx5_core]
[] mlx5_tc_ct_entry_create_mod_hdr+0x1c4/0xf50 [mlx5_core]
[] mlx5_tc_ct_entry_add_rule+0x16f/0xaf0 [mlx5_core]
[] mlx5_tc_ct_block_flow_offload_add+0x10cb/0x1f90 [mlx5_core]
[] mlx5_tc_ct_block_flow_offload+0x14a/0x630 [mlx5_core]
[] nf_flow_offload_tuple+0x1a3/0x390 [nf_flow_table]
[] flow_offload_work_handler+0x257/0xd30 [nf_flow_table]
[] process_one_work+0x7c2/0x13e0
[] worker_thread+0x59d/0xec0
[] kthread+0x28f/0x330
[] ret_from_fork+0x1f/0x30

Fix the issue by correctly releasing the label mapping.

Related CVE by CWE

No related CWE found.

Top CVE for Vendor

No vendor taxonomy on this entry.

Recently Exploited Similar Vulnerabilities

No recent KEV-listed items for this vendor/product.

How to fix CVE-2023-53720

CVE-2023-53720 is a unknown severity vulnerability affecting the affected product.

Description: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Release the label when replacing existing ct entry Cited commit doesn’t release the label mapping when replacing existing ct entry which leads to following memleak report: unreferenced object 0xffff8881854cf280 (size 96): comm “kworker/u48:74”, pid 23093, jiffies 4296664564 (age 175.944s) hex dump (first 32 bytes): […]

Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public

How to Fix:

1 Identify affected systems

- Check if you're running the affected product

2 Immediate actions

- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access

3 Verification

- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)

4 Long-term prevention

- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations

Exploit Difficulty Assessment

HARD
⏱️ Time to Exploit: > 4 hours
🛠️ Skills Required: Advanced security expertise
💰 Public Exploits: Rare or not public

Vulnerability Timeline

Oct 22, 2025
Vulnerability Published

CVE details first published to NVD database

Jan 01, 1970
Last Modified

CVE details were updated

Oct 28, 2025
Imported to Database

Added to this CVE tracking system

Detection Rules & IOCs

No specific detection rules generated for this vulnerability type.

No vendor/product data available.