CVE-2024-26742

Kernel warning via incorrect queue-map registration

Published Apr 3, 2024 · Updated May 11, 2026

Incorrect queue mapping in the Linux kernel smartpqi driver allows local users to trigger a warning during driver initialization. When disable_managed_interrupts is enabled, the driver clears PCI_IRQ_AFFINITY but still calls blk_mq_pci_map_queues instead of blk_mq_map_queues. The issue requires a Smart Storage controller and this nondefault module setting; the documented outcome is a stack trace with otherwise unspecified undefined behavior.

CVSS severity7.8
High
EPSS probability0.24%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect queue mapping in the Linux kernel smartpqi driver allows local users to trigger a warning during driver initialization. When disable_managed_interrupts is enabled, the driver clears PCI_IRQ_AFFINITY but still calls blk_mq_pci_map_queues instead of blk_mq_map_queues. The issue requires a Smart Storage controller and this nondefault module setting; the documented outcome is a stack trace with otherwise unspecified undefined behavior.

The record

CVE
CVE-2024-26742
Published
Apr 3, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-787
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 3, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.0
  2. Affected versionversion=cf15c3e734e8d25de7b4d9170f5a69ace633a583 <3c31b18a8dd8b7bf36af1cd723d455853b8f94fe
  3. Affected versionversion=cf15c3e734e8d25de7b4d9170f5a69ace633a583 <4f5b15c15e6016efb3e14582d02cc4ddf57227df
  4. Affected versionversion=cf15c3e734e8d25de7b4d9170f5a69ace633a583 <5761eb9761d2d5fe8248a9b719efc4d8baf1f24a
  5. Affected versionversion=cf15c3e734e8d25de7b4d9170f5a69ace633a583 <b9433b25cb06c415c9cb24782599649a406c8d6d

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.0; version=cf15c3e734e8d25de7b4d9170f5a69ace633a583 <3c31b18a8dd8b7bf36af1cd723d455853b8f94fe; version=cf15c3e734e8d25de7b4d9170f5a69ace633a583 <4f5b15c15e6016efb3e14582d02cc4ddf57227df; version=cf15c3e734e8d25de7b4d9170f5a69ace633a583 <5761eb9761d2d5fe8248a9b719efc4d8baf1f24a; version=cf15c3e734e8d25de7b4d9170f5a69ace633a583 <b9433b25cb06c415c9cb24782599649a406c8d6d

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
5.5Amazon LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-787Out-of-bounds Write

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo