Linux Kernel up to 7.2.4 qla2xxx __qla_consume_iocb entry_count off-by-one

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$5k-$25k0.00+

Summaryinfo

A vulnerability marked as very critical has been reported in Linux Kernel up to 7.2.4. This issue affects the function __qla_consume_iocb of the component qla2xxx. The manipulation of the argument entry_count leads to off-by-one. This vulnerability is documented as CVE-2026-93242. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.2.4 and classified as very critical. This issue affects the function __qla_consume_iocb of the component qla2xxx. The manipulation of the argument entry_count with an unknown input leads to a off-by-one vulnerability. Using CWE to declare the problem leads to CWE-193. A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix response queue over-consumption in __qla_consume_iocb() qla24xx_process_response_queue() advances ring_ptr past the head IOCB before dispatching, so by the time __qla_consume_iocb() runs, ring_ptr already points at the first continuation IOCB. The function however looped purex->entry_count times starting at ring_ptr. As entry_count includes the head, this consumed one entry too many: it stamped RESPONSE_PROCESSED on the next, unrelated IOCB and advanced the ring past it, silently dropping a legitimate firmware response. The head IOCB's signature was also never marked. Mark the head processed and account for it, then consume only the entry_count - 1 continuation IOCBs, matching __qla_copy_purex_to_buffer().

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-93242 since 09/17/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/24/2026).

Upgrading to version 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, 7.2.5 or 7.3-rc1 eliminates this vulnerability. Applying the patch a136c311676fd1010b1bde3bcfd410caa2fa040f/d841707fafba5f80341b82e8c3a4c24fc5aa5132/6e3f129538c32d0019437197735912308c161843/bd1534d4afab47f13dfc27fff6f59dd859a0ac3a/31715d1e1cbf3a37ce3452635c5602f73fd7abd4/df86c27cf1ba9d66f737a1fa56479c6e7efafe4e/3ba019bdd89d931499d9476456b5d9c7ab7fa753 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.9
VulDB Meta Temp Score: 9.5

VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Off-by-one
CWE: CWE-193 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.221/6.1.188/6.6.157/6.12.110/6.18.51/7.2.5/7.3-rc1
Patch: a136c311676fd1010b1bde3bcfd410caa2fa040f/d841707fafba5f80341b82e8c3a4c24fc5aa5132/6e3f129538c32d0019437197735912308c161843/bd1534d4afab47f13dfc27fff6f59dd859a0ac3a/31715d1e1cbf3a37ce3452635c5602f73fd7abd4/df86c27cf1ba9d66f737a1fa56479c6e7efafe4e/3ba019bdd89d931499d9476456b5d9c7ab7fa753

Timelineinfo

09/17/2026 CVE reserved
09/24/2026 +7 days Advisory disclosed
09/24/2026 +0 days VulDB entry created
09/24/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-93242 (🔒)
GCVE (CVE): GCVE-0-2026-93242
GCVE (VulDB): GCVE-100-409721

Entryinfo

Created: 09/24/2026 20:28
Changes: 09/24/2026 20:28 (60)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!