# CVE-2023-1829: Use-after-free in tcindex (traffic control index filter) in the Linux Kernel > A local attacker can exploit a use-after-free in the Linux Kernel tcindex filter to escalate privileges to root. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Apr 2023 - **Updated:** 29 Jul 2026 - **Also known as:** AZL-26169, DEBIAN-CVE-2023-1829, GHSA-4x82-r4q4-7g8x, SUSE-SU-2023:4097-1, SUSE-SU-2023:4264-1, SUSE-SU-2023:4774-1, SUSE-SU-2023:4804-1, SUSE-SU-2023:4845-1, SUSE-SU-2024:0377-1, SUSE-SU-2024:0394-1, SUSE-SU-2024:0410-1, SUSE-SU-2024:0665-1, SUSE-SU-2024:0695-1, SUSE-SU-2024:1275-1, SUSE-SU-2024:2149-1, UBUNTU-CVE-2023-1829, USN-6047-1, USN-6052-1, USN-6058-1, USN-6069-1, openSUSE-SU-2024:13281-1 ## What is CVE-2023-1829? CVE-2023-1829 is a high-severity use after free vulnerability in Linux kernel, published on 12 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A use-after-free vulnerability in the Linux Kernel traffic control index filter (tcindex) can be exploited to achieve local privilege escalation. The tcindex_delete function which does not properly deactivate filters in case of a perfect hashes while deleting the underlying structure which can later lead to double freeing the structure. A local attacker user can use this vulnerability to elevate its privileges to root. We recommend upgrading past commit 8c710f75256bb3cf05ac7b1672c82b92c43f3d28 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/ . Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2023-1829? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `suse-module-tools` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 15.2.18-150200.4.15.1 | | `kgraft-patch-SLE12-SP5_Update_50` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 2-2.1 | | `kgraft-patch-SLE12-SP5_Update_52` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 2-2.1 | | `kgraft-patch-SLE12-SP5_Update_53` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 2-2.1 | | `kgraft-patch-SLE12-SP5_Update_54` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 2-8.10.1 | | `kernel-livepatch-SLE15-SP1_Update_45` | SUSE:Linux Enterprise Live Patching 15 SP1 | All versions | 2-150100.2.1 | | `kernel-livepatch-SLE15-SP1_Update_47` | SUSE:Linux Enterprise Live Patching 15 SP1 | All versions | 2-150100.2.1 | | `kernel-livepatch-SLE15-SP2_Update_41` | SUSE:Linux Enterprise Live Patching 15 SP2 | All versions | 2-150200.2.1 | | `kernel-livepatch-SLE15-SP2_Update_42` | SUSE:Linux Enterprise Live Patching 15 SP2 | All versions | 2-150200.2.1 | | `kernel-livepatch-SLE15-SP2_Update_44` | SUSE:Linux Enterprise Live Patching 15 SP2 | All versions | 2-150200.2.1 | | `kernel-livepatch-SLE15-SP2_Update_45` | SUSE:Linux Enterprise Live Patching 15 SP2 | All versions | 2-150200.2.1 | | `kernel-livepatch-SLE15-SP2_Update_48` | SUSE:Linux Enterprise Live Patching 15 SP2 | All versions | 2-150200.5.6.2 | | `kernel-livepatch-SLE15-SP3_Update_37` | SUSE:Linux Enterprise Live Patching 15 SP3 | All versions | 2-150300.2.2 | | `kernel-livepatch-SLE15-SP3_Update_38` | SUSE:Linux Enterprise Live Patching 15 SP3 | All versions | 2-150300.2.1 | | `kernel-livepatch-SLE15-SP3_Update_40` | SUSE:Linux Enterprise Live Patching 15 SP3 | All versions | 2-150300.2.1 | | `kernel-livepatch-SLE15-SP3_Update_41` | SUSE:Linux Enterprise Live Patching 15 SP3 | All versions | 2-150300.2.1 | | `kernel-livepatch-SLE15-SP3_Update_44` | SUSE:Linux Enterprise Live Patching 15 SP3 | All versions | 2-150300.7.6.2 | | `suse-module-tools` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 15.2.18-150200.4.15.1 | | `suse-module-tools` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 15.2.18-150200.4.15.1 | | `suse-module-tools` | openSUSE:Tumbleweed | All versions | 16.0.36-1.1 | Products: Linux kernel. ## How do I fix CVE-2023-1829? Apply the vendor's patch. ## Is CVE-2023-1829 being exploited? There is no known exploitation of CVE-2023-1829 in the wild and no public exploit code. Public exploit code: - https://github.com/lanleft/CVE-2023-1829 (github_poc): https://github.com/lanleft/CVE-2023-1829 ## Other vulnerabilities in Linux kernel - [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild) - [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild) - [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild) - [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild) - [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-1829 and fix it if it is affected. What it is: CVE-2023-1829 is a high-severity use after free vulnerability in Linux kernel, published on 12 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-1829 in the wild and no public exploit code. Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-1829/ (Markdown: https://insights.sbomify.com/CVE-2023-1829/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-1829 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-1829 - OSV: https://osv.dev/vulnerability/CVE-2023-1829 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-1829/ Summaries are generated and may contain mistakes; the official description above is the record.