CVE-2021-33640

6.2 MEDIUM 0.7% exploit odds Fix listed

What it is

After tar_close(), libtar.c releases the memory pointed to by pointer t. After tar_close() is called in the list() function, it continues to use pointer t: free_longlink_longname(t->th_buf) . As a result, the released memory is used (use-after-free).

At a glance

Exploitability: Can be exploited locally on the machine without logging in. High risk of service disruption.
Exploit odds: 0.7% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2022-12-19 16:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-17 03:54 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.7% in the next 30 days (EPSS).
Severity: 6.2 MEDIUM (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2022-12-19 16:15 UTC
Last modified: 2026-06-17 03:54 UTC
Exploit probability: 0.7% · EPSS, next 30 days
Weakness: CWE-416 · Use after free
Record status: Modified

Affected

Openatom Openeuler 20.03
Openatom Openeuler 22.03
Fedoraproject Fedora 36
Fedoraproject Fedora 37

Attack profile CVSS 3.1 · 6.2

Attack vector: Local
Complexity: Low
Privileges needed: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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-2021-33640.md and follow it. Check whether this project is affected by CVE-2021-33640. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record