Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-49118scsi: hisi_sas: Free irq vectors in order for v3 HW

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 21 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-49118, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected e16963f378faf82d307cad2796953f198497c614 – < 224903cc60d045576393c3b16907742f23e6c740
    • affected e16963f378faf82d307cad2796953f198497c614 – < f05a0d8de2ea49af36821a20b0b501e20ced937e
    • affected e16963f378faf82d307cad2796953f198497c614 – < 8b6eab9d683bae7f88dc894b8c851f866032301c
    • affected e16963f378faf82d307cad2796953f198497c614 – < b4cc04fa8f1fc3816c8494d77abab3f72b9d2292
    • affected e16963f378faf82d307cad2796953f198497c614 – < 554fb72ee34f4732c7f694f56c3c6e67790352a0
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.10.111 – ≤ 5.10.*
    • unaffected 5.15.34 – ≤ 5.15.*
    • unaffected 5.16.20 – ≤ 5.16.*
    • unaffected 5.17.3 – ≤ 5.17.*
    • unaffected 5.18 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49118 badge
[![CVE-2022-49118](https://cveledger.app/badge/CVE-2022-49118.svg)](https://cveledger.app/cve/CVE-2022-49118)

Record last updated .