Linux Kernel: Use-After-Free (CVE-2026-89847)
Published Last modified Sources: Debian LTS, Debian, Msrc Update Guide, CVE.org, BSI
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Avoid double completion in async IOCB timeout qla2x00_async_iocb_timeout() tries to abort a timed-out async IOCB. When qla24xx_async_abort_cmd() fails, both the SRB_LOGIN_CMD path and the SRB_CTRL_VP/default path scan outstanding_cmds[] for the SRB and then call sp->done(sp, QLA_FUNCTION_TIMEOUT) unconditionally, without checking whether the SRB was actually found and removed.
Update Linux Kernel to version 5.10.270, Linux Kernel to version 5.15.221, Linux Kernel to version 6.1.188.
- Affected
- Linux Kernel
lt 4.19..5.10.270 - Linux Kernel
lt 5.11..5.15.221 - Linux Kernel
lt 5.16..6.1.188 - Linux Kernel
lt 6.2..6.6.157 - Linux Kernel
lt 6.7..6.12.110 - Linux Kernel
lt 6.13..6.18.51 - Linux Kernel
lt 6.19..7.2.5
- Linux Kernel
- Fixed in
- Linux Kernel
5.10.270 - Linux Kernel
5.15.221 - Linux Kernel
6.1.188 - Linux Kernel
6.6.157 - Linux Kernel
6.12.110 - Linux Kernel
6.18.51 - Linux Kernel
7.2.5 - Linux Kernel
7.3
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
9.8
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: Debian LTS, Debian, Msrc Update Guide, CVE.org, BSI
0.7 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 52.7
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 98.95 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.7 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 52.7
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Avoid double completion in async IOCB timeout qla2x00_async_iocb_timeout() tries to abort a timed-out async IOCB. When qla24xx_async_abort_cmd() fails, both the SRB_LOGIN_CMD path and the SRB_CTRL_VP/default path scan outstanding_cmds[] for the SRB and then call sp->done(sp, QLA_FUNCTION_TIMEOUT) unconditionally, without checking whether the SRB was actually found and removed. If the response ISR completes the same handle first, it removes the SRB under qp_lock_ptr and runs sp->done() -> complete(sp->comp). The submitter qla24xx_control_vp() wakes from wait_for_completion(), clears sp->comp, drops its reference and returns, reclaiming the on-stack completion. The timer reference keeps the SRB alive across the timeout handler, but not the submitter's stack. The timeout then issues a second sp->done() -> qla_ctrlvp_sp_done(), which evaluates "if (sp->comp) complete(sp->comp)"; with the pointer loaded before the submitter's NULL store, complete() writes into the freed stack frame, a use-after-free. Track whether this path removed the SRB from outstanding_cmds and only call sp->done() when it did, so the command is completed exactly once by whichever path owns it. This mirrors the sp_found guard already used in qla24xx_abort_iocb_timeout().
Source: Debian LTS Advisories, Debian Security Advisories, Microsoft Security Update Guide, NVD (NIST), cvelistv5, BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | bookworm |
| Linux | debian | linux | trixie |
| Linux | debian | linux-6.12 | bookworm |
References & sources
- git.kernel.orgstable/c/71a7b6e3c7f121439f51a058e53d4a8e05b63dec
- git.kernel.orgstable/c/7257b5e1fb6c9387714f66e01b79ec82b717eede
- git.kernel.orgstable/c/f5b660e0b0d9190d8853c795c2522cc5f8c93003
- git.kernel.orgstable/c/6e217a9482eabbd8b29847be334c74cf468d3544
- git.kernel.orgstable/c/d6d856c722f40f0694ff755208552e658db6dd42
- git.kernel.orgstable/c/9fa1d71233a82416492d9c9de9756ebe140fe714
- git.kernel.orgstable/c/845d4abd92cd2f97551356c8b281ad6e197acb07
- git.kernel.orgstable/c/bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedLinux
1 individual change: Affected versions (publisher)
Show the original change
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/89xxx/CVE-2026-89847.json">CVE-2026-89847</a>Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedLinux
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Show the original change
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
ReceivedLinux
Description added or changed
New references:- https://git.kernel.org/stable/c/6e217a9482eabbd8b29847be334c74cf468d3544
- https://git.kernel.org/stable/c/71a7b6e3c7f121439f51a058e53d4a8e05b63dec
- https://git.kernel.org/stable/c/7257b5e1fb6c9387714f66e01b79ec82b717eede
- https://git.kernel.org/stable/c/845d4abd92cd2f97551356c8b281ad6e197acb07
and 4 more references
Show 10 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Avoid double completion in async IOCB timeout qla2x00_async_iocb_timeout() tries to abort a timed-out async IOCB. When qla24xx_async_abort_cmd() fails, both the SRB_LOGIN_CMD path and the SRB_CTRL_VP/default path scan outstanding_cmds[] for the SRB and then call sp->done(sp, QLA_FUNCTION_TIMEOUT) unconditionally, without checking whether the SRB was actually found and removed. If the response ISR completes the same handle first, it removes the SRB under qp_lock_ptr and runs sp->done() -> complete(sp->comp). The submitter qla24xx_control_vp() wakes from wait_for_completion(), clears sp->comp, drops its reference and returns, reclaiming the on-stack completion. The timer reference keeps the SRB alive across the timeout handler, but not the submitter's stack. The timeout then issues a second sp->done() -> qla_ctrlvp_sp_done(), which evaluates "if (sp->comp) complete(sp->comp)"; with the pointer loaded before the submitter's NULL store, complete() writes into the freed stack frame, a use-after-free. Track whether this path removed the SRB from outstanding_cmds and only call sp->done() when it did, so the command is completed exactly once by whichever path owns it. This mirrors the sp_found guard already used in qla24xx_abort_iocb_timeout().Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/89xxx/CVE-2026-89847.json">CVE-2026-89847</a>Reference added —https://git.kernel.org/stable/c/6e217a9482eabbd8b29847be334c74cf468d3544Reference added —https://git.kernel.org/stable/c/71a7b6e3c7f121439f51a058e53d4a8e05b63decReference added —https://git.kernel.org/stable/c/7257b5e1fb6c9387714f66e01b79ec82b717eedeReference added —https://git.kernel.org/stable/c/845d4abd92cd2f97551356c8b281ad6e197acb07Reference added —https://git.kernel.org/stable/c/9fa1d71233a82416492d9c9de9756ebe140fe714Reference added —https://git.kernel.org/stable/c/bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8Reference added —https://git.kernel.org/stable/c/d6d856c722f40f0694ff755208552e658db6dd42Reference added —https://git.kernel.org/stable/c/f5b660e0b0d9190d8853c795c2522cc5f8c93003Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-89847"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-89847.svg?lang=en" alt="CVE-2026-89847 – NEOSEC Intel" height="20"></a>