CVE-2023-1872: Use-after-free in Linux kernel's io_uring subsystem
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to kernel 5.17 or later upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
A use-after-free vulnerability in the Linux Kernel io_uring system can be exploited to achieve local privilege escalation. The io_file_get_fixed function lacks the presence of ctx->uring_lock which can lead to a Use-After-Free vulnerability due a race condition with fixed files getting unregistered. We recommend upgrading past commit da24142b1ef9fd5d36b76e36bab328a5b27523e8.
- weakness
- CWE-416 Use After Free
- affected
- Linux Kernel
- published ranges
- linux kernel >= 5.7 < 5.17; debian linux 10.0
- first unaffected version, by branch
- kernel 5.17
- severity
- 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- assigned by
- published
- 2023-04-12
check us git.kernel.org git.kernel.org lists.debian.org security.netapp.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 13 Apr 2023 | 0.0005 | |
| 20 Apr 2023 | 0.00042 | |
| 17 Mar 2025 | 0.00015 | scoring model v2025.03.14 |
| 29 Mar 2025 | 0.00037 | |
| 15 Jun 2026 | 0.00306 | scoring model v2026.06.15 |
| 29 Sep 2026 | 0.00285 | |
| 2 Oct 2026 | 0.00306 | |
| 7 Oct 2026 | 0.00285 | |
| 16 Oct 2026 | 0.00306 |
29 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-10-16 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: kernel 5.17. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2023-1872', '2026-10-30T23:59:59.999999Z', now());