CVE-2024-26742: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Fix disable_managed_interrupts Correct blk-mq registration issue with module parameter disable_managed_interrupts enabled. When we turn off the default PCI_IRQ_AFFINITY flag, the driver needs to register with blk-mq using blk_mq_map_queues(). The driver is currently calling blk_mq_pci_map_queues() which results in a stack trace and possibly undefined behavior. Stack Trace: [ 7.860089] scsi host2: smartpqi [ 7.871934] WARNING: CPU: 0 PID: 238 at block/blk-mq-pci.c:52 blk_mq_pci_map_queues+0xca/0xd0 [ 7.889231] Modules linked in: sd_mod t10_pi sg uas smartpqi(+) crc32c_intel scsi_transport_sas usb_storage dm_mirror dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse [ 7.924755] CPU: 0 PID: 238 Comm: kworker/0:3 Not tainted 4.18.0-372.88.1.el8_6_smartpqi_test.x86_64 #1 [ 7.944336] Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 03/08/2022 [ 7.963026] Workqueue: events work_for_cpu_fn [ 7.978275] RIP: 0010:blk_mq_pci_map_queues+0xca/0xd0 [ 7.978278] Code: 48 89 de 89 c7 e8 f6 0f 4f 00 3b 05 c4 b7 8e 01 72 e1 5b 31 c0 5d 41 5c 41 5d 41 5e 41 5f e9 7d df 73 00 31 c0 e9 76 df 73 00 <0f> 0b eb bc 90 90 0f 1f 44 00 00 41 57 49 89 ff 41 56 41 55 41 54 [ 7.978280] RSP: 0018:ffffa95fc3707d50 EFLAGS: 00010216 [ 7.978283] RAX: 00000000ffffffff RBX: 0000000000000000 RCX: 0000000000000010 [ 7.978284] RDX: 0000000000000004 RSI: 0000000000000000 RDI: ffff9190c32d4310 [ 7.978286] RBP: 0000000000000000 R08: ffffa95fc3707d38 R09: ffff91929b81ac00 [ 7.978287] R10: 0000000000000001 R11: ffffa95fc3707ac0 R12: 0000000000000000 [ 7.978288] R13: ffff9190c32d4000 R14: 00000000ffffffff R15: ffff9190c4c950a8 [ 7.978290] FS: 0000000000000000(0000) GS:ffff9193efc00000(0000) knlGS:0000000000000000 [ 7.978292] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 8.172814] CR2: 000055d11166c000 CR3: 00000002dae10002 CR4: 00000000007706f0 [ 8.172816] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 8.172817] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 8.172818] PKRU: 55555554 [ 8.172819] Call Trace: [ 8.172823] blk_mq_alloc_tag_set+0x12e/0x310 [ 8.264339] scsi_add_host_with_dma.cold.9+0x30/0x245 [ 8.279302] pqi_ctrl_init+0xacf/0xc8e [smartpqi] [ 8.294085] ? pqi_pci_probe+0x480/0x4c8 [smartpqi] [ 8.309015] pqi_pci_probe+0x480/0x4c8 [smartpqi] [ 8.323286] local_pci_probe+0x42/0x80 [ 8.337855] work_for_cpu_fn+0x16/0x20 [ 8.351193] process_one_work+0x1a7/0x360 [ 8.364462] ? create_worker+0x1a0/0x1a0 [ 8.379252] worker_thread+0x1ce/0x390 [ 8.392623] ? create_worker+0x1a0/0x1a0 [ 8.406295] kthread+0x10a/0x120 [ 8.418428] ? set_kthread_struct+0x50/0x50 [ 8.431532] ret_from_fork+0x1f/0x40 [ 8.444137] ---[ end trace 1bf0173d39354506 ]---
AI Analysis
Technical Summary
CVE-2024-26742 is a vulnerability identified in the Linux kernel specifically affecting the smartpqi SCSI driver, which is used primarily for managing storage controllers, notably those from Hewlett Packard Enterprise (HPE) ProLiant servers. The issue arises when the module parameter 'disable_managed_interrupts' is enabled. Under this condition, the driver incorrectly calls blk_mq_pci_map_queues() instead of the appropriate blk_mq_map_queues() function to register with the block multi-queue (blk-mq) subsystem. This incorrect function call leads to a kernel stack trace and potentially undefined behavior, including system instability or crashes. The vulnerability manifests as a kernel warning and stack trace during device initialization, as shown in the provided logs, indicating a failure in queue mapping for block devices. The root cause is tied to the handling of PCI interrupt affinity flags, where disabling the default PCI_IRQ_AFFINITY flag requires a different registration approach that the driver fails to implement correctly. This bug affects Linux kernel versions incorporating the smartpqi driver with the specified module parameter enabled, and it is particularly relevant for systems running on HPE ProLiant DL380 Gen10 hardware or similar platforms using this driver. While no known exploits are currently reported in the wild, the vulnerability could lead to denial of service (DoS) conditions due to kernel panics or crashes triggered by the improper queue registration. The issue has been publicly disclosed and patched in recent Linux kernel updates, but the absence of a CVSS score suggests it is a relatively new finding still under evaluation.
Potential Impact
For European organizations, especially those relying on HPE ProLiant servers or other hardware utilizing the smartpqi driver, this vulnerability poses a risk of system instability and potential denial of service. Data centers, cloud providers, and enterprises with critical infrastructure running Linux on affected hardware could experience unexpected reboots or service interruptions if the vulnerable driver is used with the disable_managed_interrupts parameter enabled. This could impact availability of storage services, leading to operational disruptions and potential data access delays. Although the vulnerability does not directly expose confidentiality or integrity risks, the resulting system crashes could indirectly affect business continuity and service level agreements. Organizations in sectors such as finance, healthcare, telecommunications, and government, which often deploy HPE hardware in their European data centers, may face increased risk. The lack of known exploits reduces immediate threat but does not eliminate the risk of future exploitation, especially in targeted attacks or insider threat scenarios where kernel-level stability is critical.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Apply the latest Linux kernel updates that include the patch for CVE-2024-26742 as soon as they become available from their Linux distribution vendors. 2) Audit systems running the smartpqi driver to identify if the disable_managed_interrupts module parameter is enabled; if not required, disable this parameter to avoid triggering the faulty code path. 3) For environments where disable_managed_interrupts must remain enabled, consider temporarily disabling or blacklisting the smartpqi driver until patched versions are deployed. 4) Implement robust monitoring of kernel logs and system stability metrics to detect early signs of kernel warnings or crashes related to the smartpqi driver. 5) Engage with hardware vendors such as HPE to confirm firmware and driver compatibility and receive guidance on safe configurations. 6) Test kernel updates in staging environments replicating production hardware to ensure stability before wide deployment. These steps go beyond generic patching advice by emphasizing configuration auditing, proactive monitoring, and vendor coordination tailored to the affected hardware and driver.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden, Belgium
CVE-2024-26742: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Fix disable_managed_interrupts Correct blk-mq registration issue with module parameter disable_managed_interrupts enabled. When we turn off the default PCI_IRQ_AFFINITY flag, the driver needs to register with blk-mq using blk_mq_map_queues(). The driver is currently calling blk_mq_pci_map_queues() which results in a stack trace and possibly undefined behavior. Stack Trace: [ 7.860089] scsi host2: smartpqi [ 7.871934] WARNING: CPU: 0 PID: 238 at block/blk-mq-pci.c:52 blk_mq_pci_map_queues+0xca/0xd0 [ 7.889231] Modules linked in: sd_mod t10_pi sg uas smartpqi(+) crc32c_intel scsi_transport_sas usb_storage dm_mirror dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse [ 7.924755] CPU: 0 PID: 238 Comm: kworker/0:3 Not tainted 4.18.0-372.88.1.el8_6_smartpqi_test.x86_64 #1 [ 7.944336] Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 03/08/2022 [ 7.963026] Workqueue: events work_for_cpu_fn [ 7.978275] RIP: 0010:blk_mq_pci_map_queues+0xca/0xd0 [ 7.978278] Code: 48 89 de 89 c7 e8 f6 0f 4f 00 3b 05 c4 b7 8e 01 72 e1 5b 31 c0 5d 41 5c 41 5d 41 5e 41 5f e9 7d df 73 00 31 c0 e9 76 df 73 00 <0f> 0b eb bc 90 90 0f 1f 44 00 00 41 57 49 89 ff 41 56 41 55 41 54 [ 7.978280] RSP: 0018:ffffa95fc3707d50 EFLAGS: 00010216 [ 7.978283] RAX: 00000000ffffffff RBX: 0000000000000000 RCX: 0000000000000010 [ 7.978284] RDX: 0000000000000004 RSI: 0000000000000000 RDI: ffff9190c32d4310 [ 7.978286] RBP: 0000000000000000 R08: ffffa95fc3707d38 R09: ffff91929b81ac00 [ 7.978287] R10: 0000000000000001 R11: ffffa95fc3707ac0 R12: 0000000000000000 [ 7.978288] R13: ffff9190c32d4000 R14: 00000000ffffffff R15: ffff9190c4c950a8 [ 7.978290] FS: 0000000000000000(0000) GS:ffff9193efc00000(0000) knlGS:0000000000000000 [ 7.978292] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 8.172814] CR2: 000055d11166c000 CR3: 00000002dae10002 CR4: 00000000007706f0 [ 8.172816] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 8.172817] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 8.172818] PKRU: 55555554 [ 8.172819] Call Trace: [ 8.172823] blk_mq_alloc_tag_set+0x12e/0x310 [ 8.264339] scsi_add_host_with_dma.cold.9+0x30/0x245 [ 8.279302] pqi_ctrl_init+0xacf/0xc8e [smartpqi] [ 8.294085] ? pqi_pci_probe+0x480/0x4c8 [smartpqi] [ 8.309015] pqi_pci_probe+0x480/0x4c8 [smartpqi] [ 8.323286] local_pci_probe+0x42/0x80 [ 8.337855] work_for_cpu_fn+0x16/0x20 [ 8.351193] process_one_work+0x1a7/0x360 [ 8.364462] ? create_worker+0x1a0/0x1a0 [ 8.379252] worker_thread+0x1ce/0x390 [ 8.392623] ? create_worker+0x1a0/0x1a0 [ 8.406295] kthread+0x10a/0x120 [ 8.418428] ? set_kthread_struct+0x50/0x50 [ 8.431532] ret_from_fork+0x1f/0x40 [ 8.444137] ---[ end trace 1bf0173d39354506 ]---
AI-Powered Analysis
Technical Analysis
CVE-2024-26742 is a vulnerability identified in the Linux kernel specifically affecting the smartpqi SCSI driver, which is used primarily for managing storage controllers, notably those from Hewlett Packard Enterprise (HPE) ProLiant servers. The issue arises when the module parameter 'disable_managed_interrupts' is enabled. Under this condition, the driver incorrectly calls blk_mq_pci_map_queues() instead of the appropriate blk_mq_map_queues() function to register with the block multi-queue (blk-mq) subsystem. This incorrect function call leads to a kernel stack trace and potentially undefined behavior, including system instability or crashes. The vulnerability manifests as a kernel warning and stack trace during device initialization, as shown in the provided logs, indicating a failure in queue mapping for block devices. The root cause is tied to the handling of PCI interrupt affinity flags, where disabling the default PCI_IRQ_AFFINITY flag requires a different registration approach that the driver fails to implement correctly. This bug affects Linux kernel versions incorporating the smartpqi driver with the specified module parameter enabled, and it is particularly relevant for systems running on HPE ProLiant DL380 Gen10 hardware or similar platforms using this driver. While no known exploits are currently reported in the wild, the vulnerability could lead to denial of service (DoS) conditions due to kernel panics or crashes triggered by the improper queue registration. The issue has been publicly disclosed and patched in recent Linux kernel updates, but the absence of a CVSS score suggests it is a relatively new finding still under evaluation.
Potential Impact
For European organizations, especially those relying on HPE ProLiant servers or other hardware utilizing the smartpqi driver, this vulnerability poses a risk of system instability and potential denial of service. Data centers, cloud providers, and enterprises with critical infrastructure running Linux on affected hardware could experience unexpected reboots or service interruptions if the vulnerable driver is used with the disable_managed_interrupts parameter enabled. This could impact availability of storage services, leading to operational disruptions and potential data access delays. Although the vulnerability does not directly expose confidentiality or integrity risks, the resulting system crashes could indirectly affect business continuity and service level agreements. Organizations in sectors such as finance, healthcare, telecommunications, and government, which often deploy HPE hardware in their European data centers, may face increased risk. The lack of known exploits reduces immediate threat but does not eliminate the risk of future exploitation, especially in targeted attacks or insider threat scenarios where kernel-level stability is critical.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Apply the latest Linux kernel updates that include the patch for CVE-2024-26742 as soon as they become available from their Linux distribution vendors. 2) Audit systems running the smartpqi driver to identify if the disable_managed_interrupts module parameter is enabled; if not required, disable this parameter to avoid triggering the faulty code path. 3) For environments where disable_managed_interrupts must remain enabled, consider temporarily disabling or blacklisting the smartpqi driver until patched versions are deployed. 4) Implement robust monitoring of kernel logs and system stability metrics to detect early signs of kernel warnings or crashes related to the smartpqi driver. 5) Engage with hardware vendors such as HPE to confirm firmware and driver compatibility and receive guidance on safe configurations. 6) Test kernel updates in staging environments replicating production hardware to ensure stability before wide deployment. These steps go beyond generic patching advice by emphasizing configuration auditing, proactive monitoring, and vendor coordination tailored to the affected hardware and driver.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-02-19T14:20:24.167Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982ac4522896dcbe39f2
Added to database: 5/21/2025, 9:08:58 AM
Last enriched: 6/29/2025, 6:09:32 PM
Last updated: 8/9/2025, 2:44:53 PM
Views: 12
Related Threats
CVE-2025-2713: CWE-269 Improper Privilege Management in Google gVisor
MediumCVE-2025-8916: CWE-770 Allocation of Resources Without Limits or Throttling in Legion of the Bouncy Castle Inc. Bouncy Castle for Java
MediumCVE-2025-8914: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in WellChoose Organization Portal System
HighCVE-2025-8913: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in WellChoose Organization Portal System
CriticalCVE-2025-8912: CWE-36 Absolute Path Traversal in WellChoose Organization Portal System
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.