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-2026-72082

scsi: elx: efct: Fix refcount leak in efct_hw_io_abort()

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: elx: efct: Fix refcount leak in efct_hw_io_abort() When efct_hw_reqtag_alloc() fails in efct_hw_io_abort(), the error path returns -ENOSPC without releasing the reference obtained via kref_get_unless_zero() earlier in the function. All other error paths correctly drop the reference. This causes a permanent reference leak on the io_to_abort object. Additionally, the abort_in_progress flag is left set to true on this path, which means future abort attempts for the same I/O will immediately return -EINPROGRESS even though the abort was never submitted, effectively blocking recovery. Fix this by adding the missing kref_put() call and reset abort_in_progress to false, matching the cleanup done in the efct_hw_wq_write() failure path below.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (11 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 63de51327a64c74e85611a0161eaae71256a3b6d – < cf97ea7b164a1881c7219f5222219c9d0fac4204
    • affected 63de51327a64c74e85611a0161eaae71256a3b6d – < 1c6e186c722cfa9a58ebe841f91ab2ddf8570cc7
    • affected 63de51327a64c74e85611a0161eaae71256a3b6d – < 62cf39a9770a6f29df59fd0edb0a05234a8b07f2
    • affected 63de51327a64c74e85611a0161eaae71256a3b6d – < faa59add4808fbf92e7d15bfd8770d2682c2b953
    • affected 63de51327a64c74e85611a0161eaae71256a3b6d – < 9b871369cbb4532f6715e044d6b9c4ceb036e5b6
    • affected 63de51327a64c74e85611a0161eaae71256a3b6d – < 747eaead2db298abfda2aa505f6d03775b40fe5f
    • affected 63de51327a64c74e85611a0161eaae71256a3b6d – < 2c007acf7b31c39c08ce4959451ad00b19be4c1f
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .