BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2023-52926High confidence

io_uring/rw: split io_read() into a helper

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 107 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.24% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 107 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.123-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2023-52926 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: io_uring/rw: split io_read() into a helper
106 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • bpftool as a component of Red Hat Enterprise Linux 9
  • kernel as a component of Red Hat Enterprise Linux 9
  • kernel-64k as a component of Red Hat Enterprise Linux 9
  • kernel-64k-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-internal as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in the Linux kernel's `io_uring/rw` component. The `IORING_OP_READ` operation did not correctly manage the provided buffer list when read input/output (I/O) operations returned an error. This could potentially lead to a use-after-free vulnerability, where memory is accessed after it has been freed, which might cause system instability or crashes.
Remediation
Affected
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-4375

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 107 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: IORING_OP_READ did not correctly consume the provided buffer list when read i/o returned < 0 (except for -EAGAIN and -EIOCBQUEUED return). This can lead to a potential use-after-free when the completion via io_rw_done runs at separate context.

What

In the Linux kernel, the following vulnerability has been resolved: IORING_OP_READ did not correctly consume the provided buffer list when read i/o returned < 0 (except for -EAGAIN and -EIOCBQUEUED return). This can lead to a potential use-after-free when the completion via io_rw_done runs at separate context.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: IORING_OP_READ did not correctly consume the provided buffer list when read i/o returned < 0 (except for -EAGAIN and -EIOCBQUEUED return). This can lead to a potential use-after-free when the completion via io_rw_done runs at separate context.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-416
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-1439Dell Secure Connect Gateway: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-0430Linux Kernel: Schwachstelle ermöglicht nicht spezifizierten Angriff

Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250226Security Bulletin 26 Feb 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 26 Feb 2025, published on 26 February 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-52831 Référence CVE CVE-2023-52837 https://www.cve.org/CVERecord?id=CVE-2023-52837 Référence CVE CVE-2023-52857 https://www.cve.org/CVERecord?id=CVE-2023-52857 Référence CVE CVE-2023-52879 https://www.cve.org/CVERecord?id=CVE-2023-52879 Référence CVE CVE-2023-52888 https://www.cve.org/CVERecord?id=CVE-2023-52888 Référence CVE CVE-2023-52905 https://www.cve.org/CVERecord?id=CVE-2023-52905 Référence CVE CVE-2023-52916 https://www.cve.org/CVERecord?id=CVE-2023-52916 Référence CVE CVE-2023-52920 https://www.cve.org/CVERecord?id=CVE-2023-52920 Référence CVE CVE-2023-52921 https://www.cve.org/CVERecord?id=CVE-2023-52921 Référence CVE CVE-2023-52926 https://www.cve.org/CVERecord?id=CVE-2023-52926 Référence CVE CVE-2023-52939 https://www.cve.org/CVERecord?id=CVE-2023-52939 Référence CVE CVE-2023-52981 https://www.cve.org/CVERecord?id=CVE-2023-52981 Référence CVE CVE-2023-53002 https://www.cve.org/CVERecord?id=CVE-2023-53002 Référence CVE CVE-2023-53008 https://www.cve.org/CVERecord?id=CVE-2023-53008 Référence CVE CVE-2023-53009 https://www.cve.org/CVERecord?id=CVE-2023-53009 Référence CVE CVE-2023-53010 https://www.cve.org/CVERecord?id=CVE-2023-53010 Référence CVE CVE-2023-53036 https://www.cve.org/CVERecord?id=CVE-2023-53036 Référence CVE CVE-2023-53037 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-52831 Référence CVE CVE-2023-52837 https://www.cve.org/CVERecord?id=CVE-2023-52837 Référence CVE CVE-2023-52857 https://www.cve.org/CVERecord?id=CVE-2023-52857 Référence CVE CVE-2023-52879 https://www.cve.org/CVERecord?id=CVE-2023-52879 Référence CVE CVE-2023-52888 https://www.cve.org/CVERecord?id=CVE-2023-52888 Référence CVE CVE-2023-52905 https://www.cve.org/CVERecord?id=CVE-2023-52905 Référence CVE CVE-2023-52916 https://www.cve.org/CVERecord?id=CVE-2023-52916 Référence CVE CVE-2023-52920 https://www.cve.org/CVERecord?id=CVE-2023-52920 Référence CVE CVE-2023-52921 https://www.cve.org/CVERecord?id=CVE-2023-52921 Référence CVE CVE-2023-52926 https://www.cve.org/CVERecord?id=CVE-2023-52926 Référence CVE CVE-2023-52939 https://www.cve.org/CVERecord?id=CVE-2023-52939 Référence CVE CVE-2023-52981 https://www.cve.org/CVERecord?id=CVE-2023-52981 Référence CVE CVE-2023-53002 https://www.cve.org/CVERecord?id=CVE-2023-53002 Référence CVE CVE-2023-53008 https://www.cve.org/CVERecord?id=CVE-2023-53008 Référence CVE CVE-2023-53009 https://www.cve.org/CVERecord?id=CVE-2023-53009 Référence CVE CVE-2023-53010 https://www.cve.org/CVERecord?id=CVE-2023-53010 Référence CVE CVE-2023-53036 https://www.cve.org/CVERecord?id=CVE-2023-53036 Référence CVE CVE-2023-53037 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0509Multiples vulnérabilités dans le noyau Linux de SUSE

ord?id=CVE-2022-49922 Référence CVE CVE-2022-49923 https://www.cve.org/CVERecord?id=CVE-2022-49923 Référence CVE CVE-2022-49924 https://www.cve.org/CVERecord?id=CVE-2022-49924 Référence CVE CVE-2022-49925 https://www.cve.org/CVERecord?id=CVE-2022-49925 Référence CVE CVE-2022-49927 https://www.cve.org/CVERecord?id=CVE-2022-49927 Référence CVE CVE-2022-49928 https://www.cve.org/CVERecord?id=CVE-2022-49928 Référence CVE CVE-2022-49931 https://www.cve.org/CVERecord?id=CVE-2022-49931 Référence CVE CVE-2023-1990 https://www.cve.org/CVERecord?id=CVE-2023-1990 Référence CVE CVE-2023-52831 https://www.cve.org/CVERecord?id=CVE-2023-52831 Référence CVE CVE-2023-52926 https://www.cve.org/CVERecord?id=CVE-2023-52926 Référence CVE CVE-2023-52927 https://www.cve.org/CVERecord?id=CVE-2023-52927 Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CVE-2023-53034 Référence CVE CVE-2023-53035 https://www.cve.org/CVERecord?id=CVE-2023-53035 Référence CVE CVE-2023-53038 https://www.cve.org/CVERecord?id=CVE-2023-53038 Référence CVE CVE-2023-53039 https://www.cve.org/CVERecord?id=CVE-2023-53039 Référence CVE CVE-2023-53040 https://www.cve.org/CVERecord?id=CVE-2023-53040 Référence CVE CVE-2023-53041 https://www.cve.org/CVERecord?id=CVE-2023-53041 Référence CVE CVE-2023-53044 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0307Multiples vulnérabilités dans le noyau Linux de SUSE

CVERecord?id=CVE-2022-49753 Référence CVE CVE-2022-49755 https://www.cve.org/CVERecord?id=CVE-2022-49755 Référence CVE CVE-2022-49759 https://www.cve.org/CVERecord?id=CVE-2022-49759 Référence CVE CVE-2023-0179 https://www.cve.org/CVERecord?id=CVE-2023-0179 Référence CVE CVE-2023-1652 https://www.cve.org/CVERecord?id=CVE-2023-1652 Référence CVE CVE-2023-2162 https://www.cve.org/CVERecord?id=CVE-2023-2162 Référence CVE CVE-2023-28410 https://www.cve.org/CVERecord?id=CVE-2023-28410 Référence CVE CVE-2023-3567 https://www.cve.org/CVERecord?id=CVE-2023-3567 Référence CVE CVE-2023-52831 https://www.cve.org/CVERecord?id=CVE-2023-52831 Référence CVE CVE-2023-52926 https://www.cve.org/CVERecord?id=CVE-2023-52926 Référence CVE CVE-2023-52927 https://www.cve.org/CVERecord?id=CVE-2023-52927 Référence CVE CVE-2023-52930 https://www.cve.org/CVERecord?id=CVE-2023-52930 Référence CVE CVE-2023-52933 https://www.cve.org/CVERecord?id=CVE-2023-52933 Référence CVE CVE-2023-52935 https://www.cve.org/CVERecord?id=CVE-2023-52935 Référence CVE CVE-2023-52939 https://www.cve.org/CVERecord?id=CVE-2023-52939 Référence CVE CVE-2023-52941 https://www.cve.org/CVERecord?id=CVE-2023-52941 Référence CVE CVE-2023-52973 https://www.cve.org/CVERecord?id=CVE-2023-52973 Référence CVE CVE-2023-52974 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0184Multiples vulnérabilités dans le noyau Linux de Debian LTS

ulletin de sécurité Debian LTS DLA-4075-1 du 01 mars 2025 https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html Bulletin de sécurité Debian LTS DLA-4076-1 du 01 mars 2025 https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html Référence CVE CVE-2021-47469 https://www.cve.org/CVERecord?id=CVE-2021-47469 Référence CVE CVE-2022-49034 https://www.cve.org/CVERecord?id=CVE-2022-49034 Référence CVE CVE-2023-52530 https://www.cve.org/CVERecord?id=CVE-2023-52530 Référence CVE CVE-2023-52916 https://www.cve.org/CVERecord?id=CVE-2023-52916 Référence CVE CVE-2023-52917 https://www.cve.org/CVERecord?id=CVE-2023-52917 Référence CVE CVE-2023-52926 https://www.cve.org/CVERecord?id=CVE-2023-52926 Référence CVE CVE-2024-26595 https://www.cve.org/CVERecord?id=CVE-2024-26595 Référence CVE CVE-2024-26921 https://www.cve.org/CVERecord?id=CVE-2024-26921 Référence CVE CVE-2024-27017 https://www.cve.org/CVERecord?id=CVE-2024-27017 Référence CVE CVE-2024-27072 https://www.cve.org/CVERecord?id=CVE-2024-27072 Référence CVE CVE-2024-27407 https://www.cve.org/CVERecord?id=CVE-2024-27407 Référence CVE CVE-2024-35870 https://www.cve.org/CVERecord?id=CVE-2024-35870 Référence CVE CVE-2024-35956 https://www.cve.org/CVERecord?id=CVE-2024-35956 Référence CVE CVE-2024-35965 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-028490Linux の Linux Kernel における解放済みメモリの使用に関する脆弱性

Linux の Linux Kernel には、解放済みメモリの使用に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.1, 6.1.122 ≤ 6.1.*, 6.6.68 ≤ 6.6.*, 6.7 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 24 Feb 2025 · Last source change 5 Aug 2026, 09:12 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-4375
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-4375↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-52926 · cve.blacktree.nl