Linux Kernel: Use-After-Free (CVE-2026-80833)
Published Last modified Sources: Ubuntu, Debian LTS, HKCERT, Debian, CVE.org, EUVD, Msrc Update Guide, BSI
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: crypto: sun8i-ss - Remove crypto_rng interface Since the crypto_rng interface for hardware PRNGs is unused and is redundant with hwrng and the actual Linux RNG, it's being phased out. Most drivers for it were already removed.
Update Linux Kernel to version 5.10.271, Linux Kernel to version 5.15.222, Linux Kernel to version 6.1.189.
- Affected
- Linux Kernel
lt 5.10..5.10.271 - Linux Kernel
lt 5.11..5.15.222 - Linux Kernel
lt 5.16..6.1.189 - Linux Kernel
lt 6.2..6.6.158 - Linux Kernel
lt 6.7..6.12.109 - Linux Kernel
lt 6.13..6.18.50 - Linux Kernel
lt 6.19..7.2.3
- Linux Kernel
- Fixed in
- Linux Kernel
5.10.271 - Linux Kernel
5.15.222 - Linux Kernel
6.1.189 - Linux Kernel
6.6.158 - Linux Kernel
6.12.109 - Linux Kernel
6.18.50 - Linux Kernel
7.2.3 - Linux Kernel
7.3
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
4.7
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
4.7
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: Ubuntu, Debian LTS, HKCERT, Debian, CVE.org, EUVD, Msrc Update Guide, BSI
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 7.3
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 47.99 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 4.7 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 4.7
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.2 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 7.3
- Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
In the Linux kernel, the following vulnerability has been resolved: crypto: sun8i-ss - Remove crypto_rng interface Since the crypto_rng interface for hardware PRNGs is unused and is redundant with hwrng and the actual Linux RNG, it's being phased out. Most drivers for it were already removed. Go ahead and remove the sun8i-ss support which is one of the only remaining ones. As usual for crypto_rng, this driver was also buggy: its ->generate() function had a use-after-free vulnerability due to using wait_for_completion_interruptible_timeout() without handling shutting down the DMA operation if a signal is sent. Also, it had a buffer overread bug in the line 'memcpy(ctx->seed, d + dlen, ctx->slen);'. There's no point in fixing these bugs separately only to remove the code anyway, so this commit is marked with Fixes and Cc stable.
Source: Ubuntu Security Notices, Debian LTS Advisories, HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Debian Security Advisories, cvelistv5, NVD (NIST), CVE.org (MITRE), ENISA EUVD, Microsoft Security Update Guide, BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
| Red Hat | OpenShift |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | bookworm |
| Linux | debian | linux | trixie |
| Linux | ubuntu | linux | jammy |
| Linux | ubuntu | linux | noble |
| Linux | ubuntu | linux | resolute |
| Linux | debian | linux-6.12 | bookworm |
| Linux | ubuntu | linux-aws | jammy |
| Linux | ubuntu | linux-aws | noble |
| Linux | ubuntu | linux-aws | resolute |
| Linux | ubuntu | linux-aws-5.15 | focal |
| Linux | ubuntu | linux-aws-6.8 | jammy |
| Linux | ubuntu | linux-aws-7.0 | noble |
| Linux | ubuntu | linux-aws-fips | jammy |
| Linux | ubuntu | linux-aws-fips | noble |
| Linux | ubuntu | linux-azure | jammy |
| Linux | ubuntu | linux-azure | noble |
| Linux | ubuntu | linux-azure | resolute |
| Linux | ubuntu | linux-azure-5.15 | focal |
| Linux | ubuntu | linux-azure-6.8 | jammy |
| Linux | ubuntu | linux-azure-fde | jammy |
| Linux | ubuntu | linux-azure-fde | noble |
| Linux | ubuntu | linux-azure-fde | resolute |
| Linux | ubuntu | linux-azure-fde-5.15 | focal |
| Linux | ubuntu | linux-azure-fde-6.8 | jammy |
References & sources
- git.kernel.orgstable/c/8ab58786b4c63b8f1b6c522f33bb67a3c8c2791feuvd
- git.kernel.orgstable/c/a78446ee6fae86ac8733f120e3ffce2e5d9384f5euvd
- git.kernel.orgstable/c/d29ccf9eeb67d775221e49a079caa1af83427afaeuvd
- git.kernel.orgstable/c/7c257a295e05ceb8f78aa3efecc4e9ce19c3313feuvd
- git.kernel.orgstable/c/9127d2a88c1795ddc4ba7687fea01cab1908fae1euvd
- git.kernel.orgstable/c/64f3406ad082c00fb7a80240a24943ccb6d9a538euvd
- git.kernel.orgstable/c/6117968fe2cdcde28ac3aa6ec814485320af4049euvd
- git.kernel.orgstable/c/a41e4ba94ad4571aa2e566baa395e6e871e0fd4feuvd
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedLinux
1 individual change: Affected versions (publisher)
Show the original change
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80833.json">CVE-2026-80833</a>Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedLinux
New references:Show 5 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80833.json">CVE-2026-80833</a>Reference added —https://git.kernel.org/stable/c/6117968fe2cdcde28ac3aa6ec814485320af4049Reference added —https://git.kernel.org/stable/c/64f3406ad082c00fb7a80240a24943ccb6d9a538Reference added —https://git.kernel.org/stable/c/9127d2a88c1795ddc4ba7687fea01cab1908fae1Reference added —https://git.kernel.org/stable/c/a41e4ba94ad4571aa2e566baa395e6e871e0fd4fSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedLinux
Show 3 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80833.json">CVE-2026-80833</a>Reference added —https://git.kernel.org/stable/c/7c257a295e05ceb8f78aa3efecc4e9ce19c3313fReference added —https://git.kernel.org/stable/c/d29ccf9eeb67d775221e49a079caa1af83427afaSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
ReceivedLinux
Description added or changed
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —In the Linux kernel, the following vulnerability has been resolved: crypto: sun8i-ss - Remove crypto_rng interface Since the crypto_rng interface for hardware PRNGs is unused and is redundant with hwrng and the actual Linux RNG, it's being phased out. Most drivers for it were already removed. Go ahead and remove the sun8i-ss support which is one of the only remaining ones. As usual for crypto_rng, this driver was also buggy: its ->generate() function had a use-after-free vulnerability due to using wait_for_completion_interruptible_timeout() without handling shutting down the DMA operation if a signal is sent. Also, it had a buffer overread bug in the line 'memcpy(ctx->seed, d + dlen, ctx->slen);'. There's no point in fixing these bugs separately only to remove the code anyway, so this commit is marked with Fixes and Cc stable.Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80833.json">CVE-2026-80833</a>Reference added —https://git.kernel.org/stable/c/8ab58786b4c63b8f1b6c522f33bb67a3c8c2791fReference added —https://git.kernel.org/stable/c/a78446ee6fae86ac8733f120e3ffce2e5d9384f5Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-80833"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-80833.svg?lang=en" alt="CVE-2026-80833 – NEOSEC Intel" height="20"></a>