# CVE-2026-92479: scsi: ufs: Avoid NULL CQE dereference when reporting invalid tags

> A NULL pointer dereference in the Linux kernel UFS driver can cause a system crash when processing invalid completion tags.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-92479, GHSA-qmq3-vr5x-q9gg, UBUNTU-CVE-2026-92479

## What is CVE-2026-92479?

CVE-2026-92479 is a vulnerability in Linux, published on 17 Sep 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: ufs: Avoid NULL CQE dereference when reporting invalid tags

The single-doorbell completion path can call ufshcd_compl_one_cqe() with a
NULL CQE. If no command is associated with the completion tag, the warning
message dereferences the CQE while reporting the error.  Avoid that
dereference and include the invalid tag in the warning.

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


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

Apply the vendor's patch.

## Is CVE-2026-92479 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92479 is a vulnerability in Linux, published on 17 Sep 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-92479 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-92479/ (Markdown: https://insights.sbomify.com/CVE-2026-92479/index.md)
```

## Sources

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

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