CVE-2026-80928

HIGHCVSS 7.8/10EPSS 0.13%

Last modified

CVE-2026-80928 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: smack: fix cred UAF in smack_file_send_sigiotask() When inspecting the credentials of another task, objective credentials (->real_cred, accessed with __task_cred()) must always be used. Accessing ->cred on a non-current task is forbidden unless that task is being created or destroyed; a task is allowed to change its own ->cred pointer with no synchronization, and changing ->cred should only affect the current syscall. smack_file_send_sigiotask() was accessing both sets of credentials: First tsk->cred, then __task_cred(tsk). Fix it, always access the objective credentials here. I have tested that this bug can lead to a KASAN-reported UAF of struct cred in smack_file_send_sigiotask(), and that this fix prevents the race.. EPSS estimates a 0.13% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: smack: fix cred UAF in smack_file_send_sigiotask() When inspecting the credentials of another task, objective credentials (->real_cred, accessed with __task_cred()) must always be used. Accessing ->cred on a non-current task is forbidden unless that task is being created or destroyed; a task is allowed to change its own ->cred pointer with no synchronization, and changing ->cred should only affect the current syscall. smack_file_send_sigiotask() was accessing both sets of credentials: First tsk->cred, then __task_cred(tsk). Fix it, always access the objective credentials here. I have tested that this bug can lead to a KASAN-reported UAF of struct cred in smack_file_send_sigiotask(), and that this fix prevents the race.

Metrics

EPSS Probability
0.13%

2.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 3b11a1decef07c19443d24ae926982bc8ec9f4c0, < a512366d84e134a9eefc2cc40eeb6e80e2ec162c; >= 3b11a1decef07c19443d24ae926982bc8ec9f4c0, < 7c7fe043f3099d0d35002b248967f75e55345b93; >= 3b11a1decef07c19443d24ae926982bc8ec9f4c0, < f9c7b1f2b9d8f4176d2632743f51400855978ace; >= 3b11a1decef07c19443d24ae926982bc8ec9f4c0, < b5bcf3adfa27279da4401ab8f1e1a706601a92be; >= 3b11a1decef07c19443d24ae926982bc8ec9f4c0, < ed64aa505875a3b4defd504ee8e59e1949246a62; >= 3b11a1decef07c19443d24ae926982bc8ec9f4c0, < b791401bf389a1546a830d2b381ca60fe94c7870; >= 3b11a1decef07c19443d24ae926982bc8ec9f4c0, < fedc88e38ce979a720cd2de042578cb5df3dc8de
LinuxLinux2.6.29

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80928?
In the Linux kernel, the following vulnerability has been resolved: smack: fix cred UAF in smack_file_send_sigiotask() When inspecting the credentials of another task, objective credentials (->real_cred, accessed with __task_cred()) must always be used. Accessing ->cred on a non-current task is forbidden unless that task is being created or destroyed; a task is allowed to change its own ->cred pointer with no synchronization, and changing ->cred should only affect the current syscall. smack_file_send_sigiotask() was accessing both sets of credentials: First tsk->cred, then __task_cred(tsk). Fix it, always access the objective credentials here. I have tested that this bug can lead to a KASAN-reported UAF of struct cred in smack_file_send_sigiotask(), and that this fix prevents the race.
How severe is CVE-2026-80928?
CVE-2026-80928 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.13% probability of exploitation in the next 30 days.
How do I fix CVE-2026-80928?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-80928?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST