PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-80928 Linux CVE debrief

A use-after-free vulnerability was found in the Linux kernel's smack_file_send_sigiotask() function. The bug occurs when accessing the credentials of another task using both tsk->cred and __task_cred(tsk). This can lead to a KASAN-reported UAF of struct cred. The issue has been resolved by always accessing the objective credentials. The vulnerability allows for potential elevation of privileges or denial of service. Linux kernel developers, maintainers, and users should assess their exposure and apply the provided patch or update to the latest kernel version.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-11
Original CVE updated
2026-10-19
Advisory published
2026-09-11
Advisory updated
2026-10-19

Who should care

Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems should assess their exposure and apply the provided patch or update to the latest kernel version.

Why it matters

The CVE-2026-80928 vulnerability in the Linux kernel can lead to a use-after-free error, potentially allowing for privilege escalation or denial of service. Linux kernel developers, maintainers, and users should assess their exposure and apply the provided patch or update to the latest kernel version.

  • Potential elevation of privileges
  • Denial of service through system crash
  • Information disclosure through unauthorized access to sensitive data

Technical summary

The vulnerability occurs in the smack_file_send_sigiotask() function of the Linux kernel. The function was accessing both tsk->cred and __task_cred(tsk), which can lead to a use-after-free error. The fix ensures that only the objective credentials are accessed, preventing the use-after-free error and potential elevation of privileges or denial of service. The vulnerability has been resolved in the Linux kernel, and users are advised to update to the latest kernel version. Linux kernel developers and maintainers should assess their exposure and apply the provided patch or update to the latest kernel version.

Defensive priority

High

Recommended defensive actions

  • Review and apply the provided patch to ensure the vulnerability is fixed.
  • Update Linux kernel to the latest version.
  • Monitor system logs for potential exploitation attempts.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details about the vulnerability. The Linux kernel maintainers have confirmed the issue and provided a fix. The vulnerability has been resolved in the Linux kernel, and users are advised to update to the latest kernel version. The fix ensures that only the objective credentials are accessed, preventing the use-after-free error.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-80928 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-80928

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-80928 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-80928

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/7c7fe043f3099d0d35002b248967f75e55345b93

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a512366d84e134a9eefc2cc40eeb6e80e2ec162c

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b5bcf3adfa27279da4401ab8f1e1a706601a92be

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b791401bf389a1546a830d2b381ca60fe94c7870

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/ed64aa505875a3b4defd504ee8e59e1949246a62

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/f9c7b1f2b9d8f4176d2632743f51400855978ace

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/fedc88e38ce979a720cd2de042578cb5df3dc8de

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.