CVE-2023-52581

What it is

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix memleak when more than 255 elements expired When more than 255 elements expired we're supposed to switch to a new gc container structure. This never happens: u8 type will wrap before reaching the boundary and nft_trans_gc_space() always returns true. This means we recycle the initial gc container structure and lose track of the elements that came before. While at it, don't deref 'gc' after we've passed it to call_rcu.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, service disruption.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2024-03-02 22:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 06:43 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 6.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2024-03-02 22:15 UTC

Last modified

2026-06-17 06:43 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-401

Record status

Analyzed

Affected

• Linux Kernel < 6.5.6
• Linux Kernel 6.6

Attack profile CVSS 3.1 · 6.3

Attack vector

Local

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2023-52581.md and follow it. Check whether this project is affected by CVE-2023-52581. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge