CVE-2023-52927

Published Mar 14, 2025

Last updated a month ago

CVSS high 7.8
Linux Kernel

Overview

AI description

Automated description summarized from trusted sources.

CVE-2023-52927 is a vulnerability found in the Linux kernel's netfilter subsystem, specifically affecting the handling of connection tracking expectations. The vulnerability arises in the `nf_ct_find_expectation` function, where connection tracking expectations (`exp`) are prematurely removed from the hash table. This occurs when `nf_conntrack_in()` calls `nf_ct_find_expectation()`. The issue impacts scenarios where the created connection tracking entry is not immediately confirmed, such as in Open vSwitch (OVS) and TC conntrack setups. A patch was developed to address this by allowing the expectation to remain in the hash table by setting `IPS_CONFIRMED` in the status of the template. The fix involves modifications to files including `nfconntrackexpect.h`, `nfconntrackcore.c`, `nfconntrackexpect.c`, and `nft_ct.c`.

Description
In the Linux kernel, the following vulnerability has been resolved: netfilter: allow exp not to be removed in nf_ct_find_expectation Currently nf_conntrack_in() calling nf_ct_find_expectation() will remove the exp from the hash table. However, in some scenario, we expect the exp not to be removed when the created ct will not be confirmed, like in OVS and TC conntrack in the following patches. This patch allows exp not to be removed by setting IPS_CONFIRMED in the status of the tmpl.
Source
416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD status
Modified
Products
linux_kernel, debian_linux

Risk scores

CVSS 3.1

Type
Primary
Base score
7.8
Impact score
5.9
Exploitability score
1.8
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity
HIGH

Weaknesses

nvd@nist.gov
CWE-416

Social media

Hype score
Not currently trending
  1. CVE-2023-52927 - Turning a Forgotten Syzkaller Report into kCTF Exploit Article by @seadragnol about finding an unfixed netfilter use-after-free bug reported by syzbot. The researcher exploited it to pwn the kernelCTF COS instance. https://t.co/2KMWA3nJJM https://t.co/f2zkqa2hL

    @linkersec

    17 Jul 2025

    3908 Impressions

    30 Retweets

    99 Likes

    32 Bookmarks

    0 Replies

    0 Quotes

  2. Top 5 Trending CVEs: 1 - CVE-2022-38392 2 - CVE-2025-1727 3 - CVE-2023-52927 4 - CVE-2025-25257 5 - CVE-2025-5959 #cve #cvetrends #cveshield #cybersecurity https://t.co/4Fua3CAN6W

    @CVEShield

    13 Jul 2025

    11 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  3. CVE-2023-52927: Turning a Forgotten Syzkaller Report into kCTF Exploit by @seadragnol https://t.co/r2oAangpxq https://t.co/Tfhd3pi51w

    @alexjplaskett

    12 Jul 2025

    2605 Impressions

    8 Retweets

    34 Likes

    16 Bookmarks

    1 Reply

    0 Quotes

  4. 2025-07-06 の人気記事はコチラでした。(自動ツイート) #Hacker_Trends ――― CVE-2023-52927 - Turning a Forgotten Syzkaller Report into kCTF Exploit | SeaDragnoL https://t.co/gLofQDy1fg https://t.co/ubZzyhXX0Z

    @motikan2010

    7 Jul 2025

    112 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  5. Top 5 Trending CVEs: 1 - CVE-2023-20867 2 - CVE-2024-29745 3 - CVE-2025-5777 4 - CVE-2025-49826 5 - CVE-2023-52927 #cve #cvetrends #cveshield #cybersecurity https://t.co/4Fua3CAN6W

    @CVEShield

    6 Jul 2025

    14 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  6. CVE-2023-52927 - Turning a Forgotten Syzkaller Report into kCTF Exploit (authored by @seadragnol): https://t.co/IYF10fzvmo #cve #exploit #exploitation #vulnerability #linux #ctf #kctf https://t.co/P5kcIxH5SD

    @ale_sp_brazil

    6 Jul 2025

    1698 Impressions

    3 Retweets

    14 Likes

    8 Bookmarks

    0 Replies

    0 Quotes

  7. Writeup for my first kCTF - CVE-2023-52927😋 https://t.co/lyNPDbC6Lg

    @seadragnol

    6 Jul 2025

    9979 Impressions

    33 Retweets

    180 Likes

    69 Bookmarks

    4 Replies

    0 Quotes

  8. CVE-2023-52927 In the Linux kernel, the following vulnerability has been resolved: netfilter: allow exp not to be removed in nf_ct_find_expectation Currently nf_conntrack_in() cal… https://t.co/Dl8bo9r6Pt

    @CVEnew

    14 Mar 2025

    380 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

Configurations

  1. In the Linux kernel, the following vulnerability has been resolved: coresight: tmc-etr: Fix race condition between sysfs and perf mode When trying to run perf and sysfs mode simultaneously, the WARN_ON() in tmc_etr_enable_hw() is triggered sometimes: WARNING: CPU: 42 PID: 3911571 at drivers/hwtracing/coresight/coresight-tmc-etr.c:1060 tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc] [..snip..] Call trace: tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc] (P) tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc] (L) tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc] coresight_enable_path+0x1c8/0x218 [coresight] coresight_enable_sysfs+0xa4/0x228 [coresight] enable_source_store+0x58/0xa8 [coresight] dev_attr_store+0x20/0x40 sysfs_kf_write+0x4c/0x68 kernfs_fop_write_iter+0x120/0x1b8 vfs_write+0x2c8/0x388 ksys_write+0x74/0x108 __arm64_sys_write+0x24/0x38 el0_svc_common.constprop.0+0x64/0x148 do_el0_svc+0x24/0x38 el0_svc+0x3c/0x130 el0t_64_sync_handler+0xc8/0xd0 el0t_64_sync+0x1ac/0x1b0 ---[ end trace 0000000000000000 ]--- Since the enablement of sysfs mode is separeted into two critical regions, one for sysfs buffer allocation and another for hardware enablement, it's possible to race with the perf mode. Fix this by double check whether the perf mode's been used before enabling the hardware in sysfs mode. mode: [sysfs mode] [perf mode] tmc_etr_get_sysfs_buffer() spin_lock(&drvdata->spinlock) [sysfs buffer allocation] spin_unlock(&drvdata->spinlock) spin_lock(&drvdata->spinlock) tmc_etr_enable_hw() drvdata->etr_buf = etr_perf->etr_buf spin_unlock(&drvdata->spinlock) spin_lock(&drvdata->spinlock) tmc_etr_enable_hw() WARN_ON(drvdata->etr_buf) // WARN sicne etr_buf initialized at the perf side spin_unlock(&drvdata->spinlock) With this fix, we retain the check for CS_MODE_PERF in get_etr_sysfs_buf. This ensures we verify whether the perf mode's already running before we actually allocate the buffer. Then we can save the time of allocating/freeing the sysfs buffer if race with the perf mode.CVE-2026-46272