* [CVE-2026-97619][LOW] io_uring/rw: end write accounting from ->ki_complete [ Upstream
@ 2026-09-25 15:45 21% AL-KERNEL
0 siblings, 0 replies; 1+ results
From: AL-KERNEL @ 2026-09-25 15:45 UTC (permalink / raw)
To: kernel-cve
CVE: CVE-2026-97619
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: io_uring/rw: end write accounting from ->ki_complete [ Upstream
Commit: cc580cee4dfa2ec9099c30ecbd4d804cbb996432
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cc580cee4dfa2ec9099c30ecbd4d804cbb996432
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97619
Analysis date: Fri, 25 Sep 2026 11:45:02 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO
Summary:
No one-sentence report phrase was found.
======================================================================
ABOUT THIS REPORT
======================================================================
The original Linux kernel CVE announcement for CVE-2026-97619 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97619
The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.
This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.
The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.
Published priority for this report: LOW
Manual review required: NO
A detailed explanation of the methodology and priority rules is included
at the end of this message.
======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================
CVE-2026-97619 LOW https://www.kernelcve.org/list/?q=CVE-2026-97619 CHECK WITH IMPACT FROM ORIG NN IMPORTANT Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';*CWE-833;CWE-667;**CWE-400;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'A deadlock in io_uring write completion accounting can occur when write accounting is deferred to task_work owned by a process that subsequently blocks in freeze_super. The filesystem freeze waits for the outstanding sb_writers read side protection, while releasing that protection depends on task_work that cannot run until the blocked process resumes. This can stall filesystem shutdown or freeze operations and may block related filesystem activity, resulting in a local denial of service. For the CVSS the PR:L paranoid rating accounts for environments where a service account, delegated storage administrator, or reduced capability container root can control the io_uring workload and invoke the relevant freeze related operation. The issue is not network reachable. No confidentiality or integrity impact is indicated because the failure is a synchronization deadlock without a demonstrated memory corruption primitive.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) YES WRITE OOB INIT IO_URING SYZBOT LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 YES NO checked
======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================
ActionableScore=1
PrimitiveClass=NONE
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES
1. ActionableScore
* Raw conservative score: 1
* Conservative score: 1
* Raw paranoid score: 1
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate**::
The score is based on one concrete local denial of service signal. No floor or cap was applied.
2. Signal breakdown
* +1 Reliable filesystem freeze or shutdown denial of service. The patch establishes a deadlock where freeze_super waits for SB_FREEZE_WRITE accounting, while completion of that accounting is deferred to task_work of the same task blocked in freeze_super.
Important non-awarded signals:
* No UAF, stale object, double release, refcount misuse, OOB access, or invalid pointer dereference is established.
* No controlled reclaim, arbitrary write, controlled object replacement, callback influence, or post-free structured object use is demonstrated.
* No confidentiality or integrity impact is established.
* No remote reachability is established. The trigger requires local io_uring activity and a local filesystem freeze or shutdown operation.
* No Local unprivileged trigger point is awarded because the supplied context does not establish that the complete FS_IOC_SHUTDOWN or bdev_freeze operation is available to an ordinary user.
* No host-admin penalty is applied because the relevant capability check for the complete filesystem shutdown operation is not visible in the supplied patch and context.
* No hard-race penalty is applied. The issue is an ordered deadlock sequence involving asynchronous completion and deferred task_work, not an externally uncontrollable narrow lifetime race.
* No broad exposure point is awarded. io_uring is broadly deployed, but the vulnerable sequence additionally requires filesystem freeze or shutdown activity and is not a normal I O data-plane operation.
3. Reachability analysis
The evaluated attacker is a local process that owns an io_uring ring and submits an asynchronous write operation which completes through io-wq. The same task then invokes a filesystem shutdown or freeze operation before its queued task_work executes.
The supplied evidence establishes local reachability to io_uring but does not show the permission checks for FS_IOC_SHUTDOWN, bdev_freeze, or the relevant filesystem ioctl implementation. Therefore HostAdminRequired is UNKNOWN rather than YES or NO.
NamespaceScopedPrivilege is also UNKNOWN. No evidence establishes that the complete sequence, including filesystem shutdown or freeze of the affected backing filesystem, can be performed with capabilities scoped to an attacker-created namespace. There is no network trigger, special device requirement, boot-time prerequisite, or hardware dependency established by the patch.
The deadlock ordering is reproducible in principle when asynchronous write completion is delayed until after the caller enters freeze_super. However, it is not a memory-lifetime race and does not expose an attacker-controlled corruption primitive.
4. Primitive and severity interpretation
The exact primitive is a synchronization and accounting deadlock. An io_uring write acquires superblock write protection through sb_writers. Its release is incorrectly deferred to owner task_work. If the owner enters freeze_super first, freeze_super waits for the write-side reader to release its protection, but the owner cannot execute the queued task_work because it is sleeping in the freeze path.
This is not an active structured-object UAF, fixed stale storage issue, repeated release, refcount mutation, ownership violation, authorization bypass, or semantic reinterpretation issue. No first lifetime operation can free an object, and no second lifetime operation mutates freed storage.
The demonstrated consequence is a stalled filesystem freeze or shutdown operation and associated local availability impact. A broader kernel crash, confidentiality impact, integrity impact, privilege escalation, or persistent filesystem corruption is not supported by the patch.
PrimitiveClass is NONE because the bug is a deadlock without a meaningful corruption, lifetime, ownership, or authorization primitive. ImportantCandidate is NO and AutoDowngradeAllowed is YES because no unresolved exploitation leverage beyond the local denial of service is established.
5. One-sentence report phrase
A local io_uring write completion accounting deadlock can block filesystem freeze or shutdown operations when deferred task_work cannot run, causing denial of service without a demonstrated memory corruption primitive.
6. Manual review recommendation
NO MANUAL CHECK NEEDED
The patch establishes a local synchronization deadlock and availability impact only. No memory corruption, lifetime violation, authorization bypass, remote trigger, or unresolved exploitation primitive is present.
7. Call-site confidence
Call-site confidence: medium
======================================================================
UPSTREAM PATCH SUMMARY
======================================================================
Patch: io_uring/rw: end write accounting from ->ki_complete [ Upstream
Commit: cc580cee4dfa2ec9099c30ecbd4d804cbb996432
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cc580cee4dfa2ec9099c30ecbd4d804cbb996432
Changed files:
io_uring/rw.c
Diff excerpt:
Not included in this email. See the upstream URL for the full patch.
Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=cc580cee4dfa2ec9099c30ecbd4d804cbb996432
======================================================================
DETAILED REPORT METHODOLOGY
======================================================================
The original Linux kernel CVE announcement for CVE-2026-97619 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97619
The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.
The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.
This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.
The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.
Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:
Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
The Best / paranoid CVSS score: 4.7
The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.
CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.
A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.
Conservative ActionableScore: unknown
Paranoid ActionableScore: 1
The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.
For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:
ActionableScore below 5 -> MODERATE REGULAR
ActionableScore 5 or more -> MODERATE 7.0
The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.
There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).
KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.
AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW
These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).
Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is [email protected] (and both
send reply to CVE record itself too and see "reply" button below for howto reply).
^ permalink raw reply [relevance 21%]
Results 1-1 of 1 | reverse | sort options + mbox downloads above
-- links below jump to the message on this page --
2026-09-25 15:45 21% [CVE-2026-97619][LOW] io_uring/rw: end write accounting from ->ki_complete [ Upstream AL-KERNEL
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox