Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89847scsi: qla2xxx: Avoid double completion in async IOCB timeout

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().

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89847, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.69% · top 46% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected f6145e86d21fccd59bbb87bc1e1eb076658fd79a – < 71a7b6e3c7f121439f51a058e53d4a8e05b63dec
    • affected f6145e86d21fccd59bbb87bc1e1eb076658fd79a – < 7257b5e1fb6c9387714f66e01b79ec82b717eede
    • affected f6145e86d21fccd59bbb87bc1e1eb076658fd79a – < f5b660e0b0d9190d8853c795c2522cc5f8c93003
    • affected f6145e86d21fccd59bbb87bc1e1eb076658fd79a – < 6e217a9482eabbd8b29847be334c74cf468d3544
    • affected f6145e86d21fccd59bbb87bc1e1eb076658fd79a – < d6d856c722f40f0694ff755208552e658db6dd42
    • affected f6145e86d21fccd59bbb87bc1e1eb076658fd79a – < 9fa1d71233a82416492d9c9de9756ebe140fe714
    • affected f6145e86d21fccd59bbb87bc1e1eb076658fd79a – < 845d4abd92cd2f97551356c8b281ad6e197acb07
    • affected f6145e86d21fccd59bbb87bc1e1eb076658fd79a – < bb45bc4bd53c95a7bf6f782577b5ede94c0f8aa8
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89847 badge
[![CVE-2026-89847](https://cveledger.app/badge/CVE-2026-89847.svg)](https://cveledger.app/cve/CVE-2026-89847)

Record last updated .