# netfilter: allow exp not to be removed in nf_ct_find_expectation

CVE record · `CVE-2023-52927`

- **Identifiers:** `CVE-2023-52927`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 14 Mar 2025
- **Updated:** 10 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 14 Mar 2025, 14:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `1bc91a5ddf3eaea0e0ea957cccf3abdcfcace00e to before 3fa58a6fbd1e9e5682d09cdafb08fba004cb12ec` (git)
  - affected: `1bc91a5ddf3eaea0e0ea957cccf3abdcfcace00e to before 4914109a8e1e494c6aa9852f9e84ec77a5fc643f` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.18`
  - unaffected: `before 5.18` (semver)
  - unaffected: `6.1.130 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel netfilter connection tracking code is affected starting with version 5.18. The source gives few details on how an attacker could exploit this or what impact it has, though it is rated CVSS 3.1 7.8 (HIGH). Upgrade to Linux kernel 6.1.130 or later in the 6.1 series, or to 6.6 or later.

Written 19 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0032, the 25th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 14 Mar 2025, 14:25 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2023-52927)
- 14 Mar 2025, 15:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-52927)

## Sources

- [CVE List: CVE-2023-52927](https://www.cve.org/CVERecord?id=CVE-2023-52927)
- [NVD: CVE-2023-52927](https://nvd.nist.gov/vuln/detail/CVE-2023-52927)

### References from the CNA

- <https://git.kernel.org/stable/c/3fa58a6fbd1e9e5682d09cdafb08fba004cb12ec>
- <https://git.kernel.org/stable/c/4914109a8e1e494c6aa9852f9e84ec77a5fc643f>
- <https://seadragnol.github.io/posts/CVE-2023-52927/>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2023-52927>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2023-52927/>. Everything for agents: <https://agentprime.io/llms.txt>.
