CVE-2022-49118: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: scsi: hisi_sas: Free irq vectors in order for v3 HW If the driver probe fails to request the channel IRQ or fatal IRQ, the driver will free the IRQ vectors before freeing the IRQs in free_irq(), and this will cause a kernel BUG like this: ------------[ cut here ]------------ kernel BUG at drivers/pci/msi.c:369! Internal error: Oops - BUG: 0 [#1] PREEMPT SMP Call trace: free_msi_irqs+0x118/0x13c pci_disable_msi+0xfc/0x120 pci_free_irq_vectors+0x24/0x3c hisi_sas_v3_probe+0x360/0x9d0 [hisi_sas_v3_hw] local_pci_probe+0x44/0xb0 work_for_cpu_fn+0x20/0x34 process_one_work+0x1d0/0x340 worker_thread+0x2e0/0x460 kthread+0x180/0x190 ret_from_fork+0x10/0x20 ---[ end trace b88990335b610c11 ]--- So we use devm_add_action() to control the order in which we free the vectors.
AI Analysis
Technical Summary
CVE-2022-49118 is a vulnerability identified in the Linux kernel specifically affecting the hisi_sas driver, which is responsible for handling certain SAS (Serial Attached SCSI) hardware, particularly the v3 hardware variant. The vulnerability arises from improper handling of IRQ (Interrupt Request) vectors during the driver's probe process. If the driver fails to request the channel IRQ or a fatal IRQ, it incorrectly frees IRQ vectors before freeing the IRQs themselves in the free_irq() function. This incorrect order of freeing resources leads to a kernel BUG, causing an internal kernel error and a system crash (kernel oops). The error trace points to a failure in free_msi_irqs and pci_disable_msi functions, which are involved in managing MSI (Message Signaled Interrupts) IRQ vectors. The root cause is a resource management flaw where the IRQ vectors are freed prematurely, leading to instability in the kernel. The fix implemented involves using devm_add_action() to ensure the proper order of freeing IRQ vectors and IRQs, preventing the kernel BUG and maintaining system stability. This vulnerability is specific to certain versions of the Linux kernel containing the affected hisi_sas driver code and is not known to have any exploits in the wild at the time of publication. The vulnerability does not have an assigned CVSS score yet.
Potential Impact
For European organizations, this vulnerability can lead to system instability and unexpected kernel crashes on Linux systems using the affected hisi_sas driver with v3 SAS hardware. This can result in denial of service conditions, particularly impacting servers and storage systems that rely on SAS devices for critical data operations. Organizations in sectors such as finance, telecommunications, cloud service providers, and data centers that deploy Linux servers with this hardware may experience service disruptions, data unavailability, and potential operational downtime. While this vulnerability does not directly lead to privilege escalation or data leakage, the resulting kernel panic can cause loss of availability and may require system reboots, impacting business continuity. Additionally, repeated crashes could lead to hardware stress or data corruption if not properly managed. Since the vulnerability is related to hardware driver management, it is more likely to affect environments with specific hardware configurations, limiting its scope but increasing the impact on affected systems.
Mitigation Recommendations
European organizations should first identify if their Linux systems use the hisi_sas driver with v3 SAS hardware. This can be done by auditing hardware inventories and kernel module usage. Systems running affected kernel versions should be updated promptly with the patched kernel version that includes the fix using devm_add_action() to manage IRQ vector freeing order. If immediate patching is not possible, organizations should consider isolating affected systems from critical production workloads or implementing monitoring to detect kernel oops and crashes related to this driver. Additionally, organizations should ensure robust backup and recovery procedures are in place to mitigate potential data loss from unexpected reboots. For environments using custom or embedded Linux kernels, developers should backport the fix to their kernel versions. Network segmentation and limiting access to critical Linux servers can reduce the risk of exploitation attempts. Finally, maintaining up-to-date kernel and driver documentation and subscribing to Linux kernel security advisories will help organizations stay informed about further developments.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy
CVE-2022-49118: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: hisi_sas: Free irq vectors in order for v3 HW If the driver probe fails to request the channel IRQ or fatal IRQ, the driver will free the IRQ vectors before freeing the IRQs in free_irq(), and this will cause a kernel BUG like this: ------------[ cut here ]------------ kernel BUG at drivers/pci/msi.c:369! Internal error: Oops - BUG: 0 [#1] PREEMPT SMP Call trace: free_msi_irqs+0x118/0x13c pci_disable_msi+0xfc/0x120 pci_free_irq_vectors+0x24/0x3c hisi_sas_v3_probe+0x360/0x9d0 [hisi_sas_v3_hw] local_pci_probe+0x44/0xb0 work_for_cpu_fn+0x20/0x34 process_one_work+0x1d0/0x340 worker_thread+0x2e0/0x460 kthread+0x180/0x190 ret_from_fork+0x10/0x20 ---[ end trace b88990335b610c11 ]--- So we use devm_add_action() to control the order in which we free the vectors.
AI-Powered Analysis
Technical Analysis
CVE-2022-49118 is a vulnerability identified in the Linux kernel specifically affecting the hisi_sas driver, which is responsible for handling certain SAS (Serial Attached SCSI) hardware, particularly the v3 hardware variant. The vulnerability arises from improper handling of IRQ (Interrupt Request) vectors during the driver's probe process. If the driver fails to request the channel IRQ or a fatal IRQ, it incorrectly frees IRQ vectors before freeing the IRQs themselves in the free_irq() function. This incorrect order of freeing resources leads to a kernel BUG, causing an internal kernel error and a system crash (kernel oops). The error trace points to a failure in free_msi_irqs and pci_disable_msi functions, which are involved in managing MSI (Message Signaled Interrupts) IRQ vectors. The root cause is a resource management flaw where the IRQ vectors are freed prematurely, leading to instability in the kernel. The fix implemented involves using devm_add_action() to ensure the proper order of freeing IRQ vectors and IRQs, preventing the kernel BUG and maintaining system stability. This vulnerability is specific to certain versions of the Linux kernel containing the affected hisi_sas driver code and is not known to have any exploits in the wild at the time of publication. The vulnerability does not have an assigned CVSS score yet.
Potential Impact
For European organizations, this vulnerability can lead to system instability and unexpected kernel crashes on Linux systems using the affected hisi_sas driver with v3 SAS hardware. This can result in denial of service conditions, particularly impacting servers and storage systems that rely on SAS devices for critical data operations. Organizations in sectors such as finance, telecommunications, cloud service providers, and data centers that deploy Linux servers with this hardware may experience service disruptions, data unavailability, and potential operational downtime. While this vulnerability does not directly lead to privilege escalation or data leakage, the resulting kernel panic can cause loss of availability and may require system reboots, impacting business continuity. Additionally, repeated crashes could lead to hardware stress or data corruption if not properly managed. Since the vulnerability is related to hardware driver management, it is more likely to affect environments with specific hardware configurations, limiting its scope but increasing the impact on affected systems.
Mitigation Recommendations
European organizations should first identify if their Linux systems use the hisi_sas driver with v3 SAS hardware. This can be done by auditing hardware inventories and kernel module usage. Systems running affected kernel versions should be updated promptly with the patched kernel version that includes the fix using devm_add_action() to manage IRQ vector freeing order. If immediate patching is not possible, organizations should consider isolating affected systems from critical production workloads or implementing monitoring to detect kernel oops and crashes related to this driver. Additionally, organizations should ensure robust backup and recovery procedures are in place to mitigate potential data loss from unexpected reboots. For environments using custom or embedded Linux kernels, developers should backport the fix to their kernel versions. Network segmentation and limiting access to critical Linux servers can reduce the risk of exploitation attempts. Finally, maintaining up-to-date kernel and driver documentation and subscribing to Linux kernel security advisories will help organizations stay informed about further developments.
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
- 2025-02-26T01:49:39.263Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982cc4522896dcbe4f5f
Added to database: 5/21/2025, 9:09:00 AM
Last enriched: 6/30/2025, 2:57:17 AM
Last updated: 8/11/2025, 6:23:43 PM
Views: 16
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumActions
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.