{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-53720 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53720 is a memory corruption vulnerability in Linux, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-53720 and fix it if it is affected.\n\nWhat it is: CVE-2023-53720 is a memory corruption vulnerability in Linux, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-53720 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-53720/ (Markdown: https://insights.sbomify.com/CVE-2023-53720/index.md)","id":"CVE-2023-53720","markdown":"https://insights.sbomify.com/CVE-2023-53720/index.md","name":"CVE-2023-53720","record":{"aliases":["BELL-CVE-2023-53720","GHSA-2q63-477w-qcv2","UBUNTU-CVE-2023-53720"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A memory leak in the Linux kernel mlx5e driver allows local attackers to cause denial of service by exhausting kernel memory.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Release the label when replacing existing ct entry\n\nCited commit doesn't release the label mapping when replacing existing ct\nentry which leads to following memleak report:\n\nunreferenced object 0xffff8881854cf280 (size 96):\n  comm \"kworker/u48:74\", pid 23093, jiffies 4296664564 (age 175.944s)\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace:\n    [\u003c000000002722d368\u003e] __kmalloc+0x4b/0x1c0\n    [\u003c00000000cc44e18f\u003e] mapping_add+0x6e8/0xc90 [mlx5_core]\n    [\u003c000000003ad942a7\u003e] mlx5_get_label_mapping+0x66/0xe0 [mlx5_core]\n    [\u003c00000000266308ac\u003e] mlx5_tc_ct_entry_create_mod_hdr+0x1c4/0xf50 [mlx5_core]\n    [\u003c000000009a768b4f\u003e] mlx5_tc_ct_entry_add_rule+0x16f/0xaf0 [mlx5_core]\n    [\u003c00000000a178f3e5\u003e] mlx5_tc_ct_block_flow_offload_add+0x10cb/0x1f90 [mlx5_core]\n    [\u003c000000007b46c496\u003e] mlx5_tc_ct_block_flow_offload+0x14a/0x630 [mlx5_core]\n    [\u003c00000000a9a18ac5\u003e] nf_flow_offload_tuple+0x1a3/0x390 [nf_flow_table]\n    [\u003c00000000d0881951\u003e] flow_offload_work_handler+0x257/0xd30 [nf_flow_table]\n    [\u003c000000009e4935a4\u003e] process_one_work+0x7c2/0x13e0\n    [\u003c00000000f5cd36a7\u003e] worker_thread+0x59d/0xec0\n    [\u003c00000000baed1daf\u003e] kthread+0x28f/0x330\n    [\u003c0000000063d282a4\u003e] ret_from_fork+0x1f/0x30\n\nFix the issue by correctly releasing the label mapping.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"net/mlx5e: Release the label when replacing existing ct entry","id":"CVE-2023-53720","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"wifi: ath12k: Fix a NULL pointer dereference in ath12k_mac_op_hw_scan()","id":"CVE-2023-53721"},"packages":[],"prev":{"headline":"serial: arc_uart: fix of_iomap leak in `arc_serial_probe`","id":"CVE-2023-53719"},"products":["Linux"],"published":"2025-10-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel mlx5e driver allows local attackers to cause denial of service by exhausting kernel memory.","url":"https://insights.sbomify.com/CVE-2023-53720/"}