CVE-2022-2327

What it is

io_uring use work_flags to determine which identity need to grab from the calling process to make sure it is consistent with the calling process when executing IORING_OP. Some operations are missing some types, which can lead to incorrect reference counts which can then lead to a double free. We recommend upgrading the kernel past commit df3f3bb5059d20ef094d6b2f0256c4bf4127a859

At a glance

Exploitability

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

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. 2022-07-22 10:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-14 13:17 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: 7.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2022-07-22 10:15 UTC

Last modified

2026-10-14 13:17 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-416 · Use after free

Record status

Modified

Affected

• Netapp h300s Firmware
• Netapp h500s Firmware
• Netapp h700s Firmware
• Netapp h410s Firmware
• Netapp h410c Firmware
• Linux Kernel < 5.10.125
• Linux Kernel < 5.12

Attack profile CVSS 3.1 · 7.5

Attack vector

Local

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

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-2022-2327.md and follow it. Check whether this project is affected by CVE-2022-2327. 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