Menu

Star on GitHub · 3.2k

CVE-2026-80661

7.8 · HIGH

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…

Published Aug 28, 2026EPSS 0.17%

Overview

CVE-2026-80661 is a high-severity vulnerability. It was published on August 28, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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 rea

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-80661?

CVE-2026-80661 is a high-severity vulnerability. It was published on August 28, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-80661?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-80661?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-80661?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-80661 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all