# CVE-2026-72081: scsi: elx: efct: Fix I/O leak on unsupported additional CDB

> A memory leak in the Linux kernel's efct SCSI driver allows attackers to cause a denial of service by sending unsupported FCP commands.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72081, DEBIAN-CVE-2026-72081, GHSA-993f-79rg-53g7, UBUNTU-CVE-2026-72081

## What is CVE-2026-72081?

CVE-2026-72081 is a denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

scsi: elx: efct: Fix I/O leak on unsupported additional CDB

efct_dispatch_fcp_cmd() allocates an efct_io before dispatching an
unsolicited FCP command. If the command has an unsupported additional
CDB, the function returns -EIO before handing the IO to the SCSI layer.

Free the allocated IO before returning from this error path.

## Which versions are affected by CVE-2026-72081?


## How do I fix CVE-2026-72081?

Apply the vendor's patch.

## Is CVE-2026-72081 being exploited?

There is no known exploitation of CVE-2026-72081 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72081 and fix it if it is affected.

What it is: CVE-2026-72081 is a denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72081 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72081/ (Markdown: https://insights.sbomify.com/CVE-2026-72081/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72081
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72081
- OSV: https://osv.dev/vulnerability/CVE-2026-72081

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72081/
Summaries are generated and may contain mistakes; the official description above is the record.