# CVE-2026-80661: ufs: core: tracing: Do not dereference pointers in TP_printk()

> A use-after-free vulnerability in the Linux kernel UFS tracing code allows a local attacker to crash the system by reading trace logs after the device is removed.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** BELL-CVE-2026-80661, DEBIAN-CVE-2026-80661, GHSA-q8qh-9988-234v, UBUNTU-CVE-2026-80661

## What is CVE-2026-80661?

CVE-2026-80661 is a high-severity vulnerability in Linux, published on 28 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:

ufs: core: tracing: Do not dereference pointers in TP_printk()

The trace events in drivers/ufs/core/ufs_trace.h were converted to take a
pointer to the hba structure as an argument for the tracepoint and then in
TP_printk() the printing of the dev_name from the ring buffer was
converted to using the dev dereferenced pointer from the hba saved
pointer.

This is not allowed as the TP_printk() is executed at the time the trace
event is read from /sys/kernel/tracing/trace file. That can happen
literally, seconds, minutes, hours, weeks, days, or even months later!
There is no guarantee that the hba pointer will still exist by the time it
is dereferenced when the "trace" file is read.

Instead, save the device name from the hba pointer at the time the
tracepoint is called and place it into the ring buffer event. Then the
TP_printk() can read the name directly from the ring buffer and remove the
possibility that it will read a freed pointer and crash the kernel.

This was detected when testing the trace event code that looks for
TP_printk() parameters doing illegal derferences[1]

[1] https://lore.kernel.org/all/20260630184836.74d477b6@gandalf.local.home/

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


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

Apply the vendor's patch.

## Is CVE-2026-80661 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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