io_uring/tctx: work around xa_store() allocation error issue
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3a84fa784710990964c1e35df743851ab2863898, 42882b583095dcf747da6e3af1daeff40e27033e, 7eb75ce7527129d7f1fee6951566af409a37a1c4.
Low priority for now. Upgrade to Linux Linux 3a84fa784710990964c1e35df743851ab2863898, 42882b583095dcf747da6e3af1daeff40e27033e, 7eb75ce7527129d7f1fee6951566af409a37a1c4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: io_uring/tctx: work around xa_store() allocation error issue syzbot triggered the following WARN_ON: WARNING: CPU: 0 PID: 16 at io_uring/tctx.c:51 __io_uring_free+0xfa/0x140 io_uring/tctx.c:51 which is the WARN_ON_ONCE(!xa_empty(&tctx->xa)); sanity check in __io_uring_free() when a io_uring_task is going through its final put. The syzbot test case includes injecting memory allocation failures, and it very much looks like xa_store() can fail one of its memory allocations and end up with ->head being non-NULL even though no entries exist in the xarray. Until this issue gets sorted out, work around it by attempting to iterate entries in our xarray, and WARN_ON_ONCE() if one is found.
- Published
- Dec 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-770
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.1 and later · before 6.1.120
- linux linux kernel6.2 and later · before 6.6.66
- linux linux kernel6.7 and later · before 6.12.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.1affected
- 2b188cc1bb857a9d4701ae59aa7768b5124e262e and later · before e05c070b401f6365c503e2b59f091331965c4fb9affected · git
- 2b188cc1bb857a9d4701ae59aa7768b5124e262e and later · before 3a84fa784710990964c1e35df743851ab2863898affected · git
- 2b188cc1bb857a9d4701ae59aa7768b5124e262e and later · before 94ad56f61b873ffeebcc620d451eacfbdf9d40f0affected · git
- 2b188cc1bb857a9d4701ae59aa7768b5124e262e and later · before 42882b583095dcf747da6e3af1daeff40e27033eaffected · git
- 2b188cc1bb857a9d4701ae59aa7768b5124e262e and later · before d5b2ddf1f90c7248eff9630b95895c8950f2f36daffected · git
- 2b188cc1bb857a9d4701ae59aa7768b5124e262e and later · before 7eb75ce7527129d7f1fee6951566af409a37a1c4affected · git
- before 5.1not affected · semver
- 5.10.253 and later · up to and including 5.10.*not affected · semver
- 5.15.203 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.123-1 | 6.1.123-1 |
| Debian:13 | linux | before 6.12.5-1 | 6.12.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2024-56582Dec 27, 2024 · btrfs: fix use-after-free in btrfs_encoded_read_endio()31Monitor
- ← EarlierCVE-2024-56583Dec 27, 2024 · sched/deadline: Fix warning in migrate_enable for boosted tasks22Monitor
- Later →CVE-2024-56585Dec 27, 2024 · LoongArch: Fix sleeping in atomic context for PREEMPT_RT22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3a84fa784710990964c1e35df743851ab2863898 | Vendor (CNA) |
| Linux Linux | 42882b583095dcf747da6e3af1daeff40e27033e | Vendor (CNA) |
| Linux Linux | 7eb75ce7527129d7f1fee6951566af409a37a1c4 | Vendor (CNA) |
| Linux Linux | 94ad56f61b873ffeebcc620d451eacfbdf9d40f0 | Vendor (CNA) |
| Linux Linux | d5b2ddf1f90c7248eff9630b95895c8950f2f36d | Vendor (CNA) |
| Linux Linux | e05c070b401f6365c503e2b59f091331965c4fb9 | Vendor (CNA) |
| debian:linux | 6.1.123-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2021-47137277 days apartnet: lantiq: fix memory corruption in RX ring39Monitor
- CVE-2024-35969221 days apartipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr35Monitor
- CVE-2024-34027186 days apartf2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock31Monitor
- CVE-2021-47551217 days apartdrm/amd/amdkfd: Fix kernel panic when reset failed and been triggered again31Monitor
- CVE-2026-43329497 days apartnetfilter: flowtable: strictly check for maximum number of actions31Monitor
- CVE-2021-47130287 days apartnvmet: fix freeing unallocated p2pmem30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/42882b583095dcf747da6e3af1daeff40e27033e
- git.kernel.org/stable/c/7eb75ce7527129d7f1fee6951566af409a37a1c4
- git.kernel.org/stable/c/94ad56f61b873ffeebcc620d451eacfbdf9d40f0
- git.kernel.org/stable/c/d5b2ddf1f90c7248eff9630b95895c8950f2f36d
- git.kernel.org/stable/c/e05c070b401f6365c503e2b59f091331965c4fb9
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.