CVE-2026-89846

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-16. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read

In qla2x00_status_entry(), the FWI2 status path advances sense_data and shrinks par_sense_len by rsp_info_len:

if (IS_FWI2_CAPABLE(ha)) { sense_data += rsp_info_len; par_sense_len -= rsp_info_len; }

rsp_info_len is a 32-bit value taken directly from the target's FCP response (sf.rsp_data_len), while par_sense_len is the IOCB data area size (28 bytes for 24xx, 60 bytes for 29xx). A hostile or buggy target reporting an rsp_info_len larger than par_sense_len makes the unsigned subtraction underflow to a huge value and advances sense_data out of bounds.

The underflowed par_sense_len then defeats the cap in qla2x00_handle_sense():

if (sense_len > par_sense_len) sense_len = par_sense_len; memcpy(cp->sense_buffer, sense_data, sense_len);

so the memcpy reads up to SCSI_SENSE_BUFFERSIZE bytes from the out-of-bounds sense_data pointer, leaking adjacent response-ring/heap memory into the command's sense buffer.

Clamp rsp_info_len to par_sense_len before the subtraction so par_sense_len can never underflow and sense_data stays within the IOCB data area. The fix sits before the comp_status switch, covering both qla2x00_handle_sense() call sites.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
46
EG Risk 46/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

September 16, 2026

Advisory Details (8)

Auto-updated Sep 16, 2026
Patch available.
generic

scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ca6d880d6c70cb7946e7b3e05d7285f271b6d99e
generic

scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f6e8977bce887481b2b2b0e2e14a791270741cfb
generic

scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d7f7746ff031ae45724881261804f4bf5317c985
generic

scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ebc41dfc59d190956e0113e8bd90c28f6f21e8b9
generic

scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/be75ab791c9b3baca66c70ce03443afebc83acda
generic

scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b08c0cb110a1fba92f99d655020198489699815
generic

scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e57ace988bda5693f7b3645f652ea4b4220870ee
generic

scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/125b12861c726e58448bb95d55b04851fb131d1f

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-687.51.1.el9_82026-09-24redhat
redhatkernel-0:6.12.0-211.59.1.el10_22026-09-24redhat
redhatkernel-0:4.18.0-553.167.1.el8_102026-09-24redhat
redhatkernel-rt-0:4.18.0-553.167.1.rt7.508.el8_102026-09-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 87× in last 7d / 204× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 204 total refreshes for this CVE.

  1. 2026-10-05 08:45 UTCVendor advisory
  2. 2026-10-05 08:45 UTCGHSA enrichment
  3. 2026-10-05 04:24 UTCVendor advisory
  4. 2026-10-05 04:24 UTCGHSA enrichment
  5. 2026-10-05 00:03 UTCEG score recompute
  6. 2026-10-05 00:03 UTCVendor advisory
  7. 2026-10-05 00:03 UTCGHSA enrichment
  8. 2026-10-04 23:22 UTCEPSS rescore
  9. 2026-10-04 19:42 UTCVendor advisory
  10. 2026-10-04 19:42 UTCGHSA enrichment
  11. 2026-10-04 15:21 UTCVendor advisory
  12. 2026-10-04 15:21 UTCGHSA enrichment
  13. 2026-10-04 11:00 UTCVendor advisory
  14. 2026-10-04 10:59 UTCGHSA enrichment
  15. 2026-10-04 06:38 UTCVendor advisory
  16. 2026-10-04 06:38 UTCGHSA enrichment
  17. 2026-10-04 02:17 UTCVendor advisory
  18. 2026-10-04 02:17 UTCGHSA enrichment
  19. 2026-10-03 21:56 UTCVendor advisory
  20. 2026-10-03 21:56 UTCGHSA enrichment
  21. 2026-10-03 17:26 UTCEG score recompute
  22. 2026-10-03 17:26 UTCVendor advisory
  23. 2026-10-03 17:26 UTCGHSA enrichment
  24. 2026-10-03 13:05 UTCVendor advisory
  25. 2026-10-03 13:05 UTCGHSA enrichment
Show 75 more
  1. 2026-10-03 08:40 UTCVendor advisory
  2. 2026-10-03 08:40 UTCGHSA enrichment
  3. 2026-10-03 04:01 UTCVendor advisory
  4. 2026-10-03 04:01 UTCGHSA enrichment
  5. 2026-10-02 23:34 UTCVendor advisory
  6. 2026-10-02 23:34 UTCGHSA enrichment
  7. 2026-10-02 18:59 UTCEG score recompute
  8. 2026-10-02 18:59 UTCVendor advisory
  9. 2026-10-02 18:59 UTCGHSA enrichment
  10. 2026-10-02 14:38 UTCVendor advisory
  11. 2026-10-02 14:38 UTCGHSA enrichment
  12. 2026-10-02 10:03 UTCVendor advisory
  13. 2026-10-02 10:03 UTCGHSA enrichment
  14. 2026-10-02 05:42 UTCVendor advisory
  15. 2026-10-02 05:42 UTCGHSA enrichment
  16. 2026-10-02 00:54 UTCVendor advisory
  17. 2026-10-02 00:54 UTCGHSA enrichment
  18. 2026-10-01 20:32 UTCEG score recompute
  19. 2026-10-01 20:32 UTCVendor advisory
  20. 2026-10-01 20:32 UTCGHSA enrichment
  21. 2026-10-01 19:51 UTCEPSS rescore
  22. 2026-10-01 16:10 UTCVendor advisory
  23. 2026-10-01 16:10 UTCGHSA enrichment
  24. 2026-10-01 11:50 UTCVendor advisory
  25. 2026-10-01 11:50 UTCGHSA enrichment
  26. 2026-10-01 07:27 UTCVendor advisory
  27. 2026-10-01 07:27 UTCGHSA enrichment
  28. 2026-10-01 03:06 UTCVendor advisory
  29. 2026-10-01 03:06 UTCGHSA enrichment
  30. 2026-09-30 22:46 UTCVendor advisory
  31. 2026-09-30 22:46 UTCGHSA enrichment
  32. 2026-09-30 18:24 UTCEG score recompute
  33. 2026-09-30 18:24 UTCVendor advisory
  34. 2026-09-30 18:24 UTCGHSA enrichment
  35. 2026-09-30 15:04 UTCEPSS rescore
  36. 2026-09-30 14:03 UTCVendor advisory
  37. 2026-09-30 14:03 UTCGHSA enrichment
  38. 2026-09-30 09:41 UTCVendor advisory
  39. 2026-09-30 09:41 UTCGHSA enrichment
  40. 2026-09-30 05:20 UTCVendor advisory
  41. 2026-09-30 05:20 UTCGHSA enrichment
  42. 2026-09-30 00:55 UTCVendor advisory
  43. 2026-09-30 00:55 UTCGHSA enrichment
  44. 2026-09-29 16:15 UTCEG score recompute
  45. 2026-09-29 16:15 UTCVendor advisory
  46. 2026-09-29 16:14 UTCGHSA enrichment
  47. 2026-09-29 11:52 UTCVendor advisory
  48. 2026-09-29 11:52 UTCGHSA enrichment
  49. 2026-09-29 07:31 UTCVendor advisory
  50. 2026-09-29 07:31 UTCGHSA enrichment
  51. 2026-09-29 03:10 UTCVendor advisory
  52. 2026-09-29 03:10 UTCGHSA enrichment
  53. 2026-09-28 22:48 UTCEG score recompute
  54. 2026-09-28 22:48 UTCVendor advisory
  55. 2026-09-28 22:48 UTCGHSA enrichment
  56. 2026-09-28 18:25 UTCEG score recompute
  57. 2026-09-28 18:25 UTCVendor advisory
  58. 2026-09-28 18:25 UTCGHSA enrichment
  59. 2026-09-28 13:52 UTCEPSS rescore
  60. 2026-09-28 13:52 UTCEPSS rescore
  61. 2026-09-28 13:38 UTCVendor advisory
  62. 2026-09-28 13:38 UTCGHSA enrichment
  63. 2026-09-28 09:17 UTCVendor advisory
  64. 2026-09-28 09:17 UTCGHSA enrichment
  65. 2026-09-28 04:56 UTCVendor advisory
  66. 2026-09-28 04:56 UTCGHSA enrichment
  67. 2026-09-28 00:35 UTCVendor advisory
  68. 2026-09-28 00:35 UTCGHSA enrichment
  69. 2026-09-27 20:14 UTCVendor advisory
  70. 2026-09-27 20:14 UTCGHSA enrichment
  71. 2026-09-27 15:53 UTCEG score recompute
  72. 2026-09-27 15:53 UTCVendor advisory
  73. 2026-09-27 15:53 UTCGHSA enrichment
  74. 2026-09-27 13:49 UTCEPSS rescore
  75. 2026-09-27 11:32 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-89846?
CVE-2026-89846 is a critical vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Bound rspinfolen to avoid OOB sense-data read In qla2x00statusentry(), the FWI2 status path advances sense_data and shrinks parsenselen by rspinfolen: if (ISFWI2CAPABLE(ha)) { sensedata += rspinfo_len; parsenselen -=…
When was CVE-2026-89846 disclosed?
CVE-2026-89846 was first published on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89846 actively exploited?
CVE-2026-89846 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89846?
CVE-2026-89846 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89846?
A fix for CVE-2026-89846 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89846 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-89846

Explore →

Is Your Infrastructure Affected by CVE-2026-89846?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.