CVE-2022-50270

Kernel-memory disclosure and crash via stale trace pointers

Published Sep 15, 2025 · Updated Sep 15, 2025

Use-after-free in Linux kernel f2fs 5.17 through 6.0.15 and 6.1 through 6.1.1 allows local users to read kernel memory or crash. The f2fs_direct_IO_enter trace event stores a kiocb pointer in the trace ring buffer and dereferences it after the object expires. Exploitation requires an f2fs mount, enabled affected tracepoints, direct I/O or unlink activity, and access to tracefs output; a formatted trace read exposes reused kernel memory or causes a kernel oops.

CVSS severity7.1
High
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in Linux kernel f2fs 5.17 through 6.0.15 and 6.1 through 6.1.1 allows local users to read kernel memory or crash. The f2fs_direct_IO_enter trace event stores a kiocb pointer in the trace ring buffer and dereferences it after the object expires. Exploitation requires an f2fs mount, enabled affected tracepoints, direct I/O or unlink activity, and access to tracefs output; a formatted trace read exposes reused kernel memory or causes a kernel oops.

The record

CVE
CVE-2022-50270
Published
Sep 15, 2025
Updated
Sep 15, 2025
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 15, 2025CVE publishedPublication date reported by the CVE source.
  2. Sep 15, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.17
  2. Affected versionversion=bd984c03097b8e9b7500cba7378040ac1c697dbb <0db18eec0d9a7ee525209e31e3ac2f673545b12f
  3. Affected versionversion=bd984c03097b8e9b7500cba7378040ac1c697dbb <b4244ca341ea95c52ee8fa93d04f5af3e584dd37
  4. Affected versionversion=bd984c03097b8e9b7500cba7378040ac1c697dbb <d555aa37566c5c3728f2e52047a9722eae2aed93

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.17; version=bd984c03097b8e9b7500cba7378040ac1c697dbb <0db18eec0d9a7ee525209e31e3ac2f673545b12f; version=bd984c03097b8e9b7500cba7378040ac1c697dbb <b4244ca341ea95c52ee8fa93d04f5af3e584dd37; version=bd984c03097b8e9b7500cba7378040ac1c697dbb <d555aa37566c5c3728f2e52047a9722eae2aed93

Published CVSS scores

7.1UbuntuCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
5.5Amazon LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
7.1NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo