What is CVE-2026-80661?

CVE-2026-80661 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 6.15 onward and patched in 6.18.40, 7.1.5 and 7.2. CVE-2026-80661 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-80661?

CVE-2026-80661 has a CVSS score of 7.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-80661?

Yes, CVE-2026-80661 has been patched. Fixed versions include 6.18.40, 7.1.5 and 7.2. If you are running Linux kernel 6.15 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-80661 actively exploited?

CVE-2026-80661 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-80661

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 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/[email protected]/

Package Linux Kernel

Published 2026-08-28

Last modified 2026-08-29

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.15 and later are affected. Fixed in 6.18.40, 7.1.5, 7.2 and their respective stable series.

Affected from

≥ 6.15

Fixed in

✓ 6.18.40 6.18.x ✓ 7.1.5 7.1.x ✓ 7.2

References

3 total

Details

CVE ID CVE-2026-80661

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-08-28

Modified 2026-08-29

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-80661?

CVE-2026-80661 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.15 onward and has been patched in 6.18.40, 7.1.5 and 7.2. CVE-2026-80661 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-80661?

CVE-2026-80661 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-80661?

Yes. CVE-2026-80661 has been patched. Fixed versions include 6.18.40, 7.1.5 and 7.2. If you are running Linux kernel 6.15 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-80661 actively exploited?

No. CVE-2026-80661 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.