CVE-2026-89846

CVE CVE-2026-89846EUVD EUVD-2026-80446Published 2026-09-16T10:31:20.000ZLast changed 2026-09-16T14:39:14.000ZCVSS 9.1

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 5544213be7b4fb693730106a6d70a8cc1aa7cdf6 <125b12861c726e58448bb95d55b04851fb131d1f; patch: 6.1.188; 5544213be7b4fb693730106a6d70a8cc1aa7cdf6 <6b08c0cb110a1fba92f99d655020198489699815; 5544213be7b4fb693730106a6d70a8cc1aa7cdf6 <e57ace988bda5693f7b3645f652ea4b4220870ee; patch: 6.12.110; patch: 6.18.51; 5544213be7b4fb693730106a6d70a8cc1aa7cdf6 <d7f7746ff031ae45724881261804f4bf5317c985; patch: 7.2.5; patch: 0; 5544213be7b4fb693730106a6d70a8cc1aa7cdf6 <ebc41dfc59d190956e0113e8bd90c28f6f21e8b9; 5544213be7b4fb693730106a6d70a8cc1aa7cdf6 <f6e8977bce887481b2b2b0e2e14a791270741cfb; patch: 5.10.270; 2.6.36; patch: 7.3-rc1; 5544213be7b4fb693730106a6d70a8cc1aa7cdf6 <ca6d880d6c70cb7946e7b3e05d7285f271b6d99e; patch: 6.6.157; patch: 5.15.221; 5544213be7b4fb693730106a6d70a8cc1aa7cdf6 <be75ab791c9b3baca66c70ce03443afebc83acda

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.