Linux Kernel: Use-After-Free (CVE-2026-74478)
Published Last modified Sources: Ubuntu, Debian LTS, Debian, CVE.org, BSI
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: um: vector: fix use-after-free in vector_mmsg_rx() When vector_mmsg_rx() discards a packet whose overlay header fails verify_header(), it frees the skb and continues the loop: if (header_check < 0) { dev_kfree_skb_irq(skb); vp->estats.rx_encaps_errors++; continue; } The normal and short-packet paths fall through to the bottom of the loop body, which clears the consumed slot and advances the cursors: (*skbuff_vector) = NULL; mmsg_vector++; skbuff_vector++; The verify_header() < 0 path skips that via continue, so the freed skb is left in skbuff_vector[] and the cursors do not advance. The next iteration reads the same slot, gets the freed skb, and frees it again, producing a refcount underflow / use-after-free in the RX path.
Update Linux Kernel to version 5.10.265, Linux Kernel to version 5.15.216, Linux Kernel to version 6.1.183.
- Affected
- Linux Kernel
lt 4.17..5.10.265 - Linux Kernel
lt 5.11..5.15.216 - Linux Kernel
lt 5.16..6.1.183 - Linux Kernel
lt 6.2..6.6.151 - Linux Kernel
lt 6.7..6.12.103 - Linux Kernel
lt 6.13..6.18.44 - Linux Kernel
lt 6.19..7.1.8
- Linux Kernel
- Fixed in
- Linux Kernel
5.10.265 - Linux Kernel
5.15.216 - Linux Kernel
6.1.183 - Linux Kernel
6.6.151 - Linux Kernel
6.12.103 - Linux Kernel
6.18.44 - Linux Kernel
7.1.8 - Linux Kernel
7.2
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
9.8
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: Ubuntu, Debian LTS, Debian, CVE.org, BSI
0.9 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 58.5
Show all metrics
- Severity
- Critical
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- 99.77 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- 9.8 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- 9.8
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.9 %
- 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- 58.5
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
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- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
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: um: vector: fix use-after-free in vector_mmsg_rx() When vector_mmsg_rx() discards a packet whose overlay header fails verify_header(), it frees the skb and continues the loop: if (header_check < 0) { dev_kfree_skb_irq(skb); vp->estats.rx_encaps_errors++; continue; } The normal and short-packet paths fall through to the bottom of the loop body, which clears the consumed slot and advances the cursors: (*skbuff_vector) = NULL; mmsg_vector++; skbuff_vector++; The verify_header() < 0 path skips that via continue, so the freed skb is left in skbuff_vector[] and the cursors do not advance. The next iteration reads the same slot, gets the freed skb, and frees it again, producing a refcount underflow / use-after-free in the RX path. Discard the slot the same way the other paths do before continuing. Only transports whose verify_header() can return negative are affected: GRE and L2TPv3 do so on a cookie/session-id mismatch (raw/tap do not), so any peer on such a transport can trigger it without authentication.
Source: Ubuntu Security Notices, Debian LTS Advisories, Debian Security Advisories, cvelistv5, NVD (NIST), 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 |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | bookworm |
| Linux | debian | linux | trixie |
| Linux | debian | linux-6.12 | bookworm |
| Linux | ubuntu | linux-gcp-5.15 | focal |
References & sources
- git.kernel.orgstable/c/4b9601595e8b6b5d18878cac0aeabc687d241111
- git.kernel.orgstable/c/67d58ab4f2ccf7145f3da07e025735a09c79de1b
- git.kernel.orgstable/c/180ff4c81faf01ec4e06082c9daa7c40518ead89
- git.kernel.orgstable/c/804b681002ead233abf49a3efd681f5468a835f9
- git.kernel.orgstable/c/af421e9aed3920c7ac88c24daa48606c7112feca
- git.kernel.orgstable/c/967c779c9853d2a1cc9cd8e61d300250c348f3d9
- git.kernel.orgstable/c/a7bc015bb798c525e7a82dd14225c6aeb994274b
- git.kernel.orgstable/c/7dc9781e320d664c9bdd50003c9acfddf363d1e1
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
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://git.kernel.org/stable/c/7dc9781e320d664c9bdd50003c9acfddf363d1e1Reference added —https://git.kernel.org/stable/c/967c779c9853d2a1cc9cd8e61d300250c348f3d9Reference added —https://git.kernel.org/stable/c/a7bc015bb798c525e7a82dd14225c6aeb994274bAffected versions (publisher) changed Linux, LinuxLinux, LinuxSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedLinux
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected versions (publisher) changed Linux, LinuxLinux, LinuxSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
ReceivedLinux
Description added or changed
New references:- https://git.kernel.org/stable/c/180ff4c81faf01ec4e06082c9daa7c40518ead89
- https://git.kernel.org/stable/c/4b9601595e8b6b5d18878cac0aeabc687d241111
- https://git.kernel.org/stable/c/67d58ab4f2ccf7145f3da07e025735a09c79de1b
- https://git.kernel.org/stable/c/804b681002ead233abf49a3efd681f5468a835f9
and 1 more reference
Show 7 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Linux, LinuxDescription added —In the Linux kernel, the following vulnerability has been resolved: um: vector: fix use-after-free in vector_mmsg_rx() When vector_mmsg_rx() discards a packet whose overlay header fails verify_header(), it frees the skb and continues the loop: if (header_check < 0) { dev_kfree_skb_irq(skb); vp->estats.rx_encaps_errors++; continue; } The normal and short-packet paths fall through to the bottom of the loop body, which clears the consumed slot and advances the cursors: (*skbuff_vector) = NULL; mmsg_vector++; skbuff_vector++; The verify_header() < 0 path skips that via continue, so the freed skb is left in skbuff_vector[] and the cursors do not advance. The next iteration reads the same slot, gets the freed skb, and frees it again, producing a refcount underflow / use-after-free in the RX path. Discard the slot the same way the other paths do before continuing. Only transports whose verify_header() can return negative are affected: GRE and L2TPv3 do so on a cookie/session-id mismatch (raw/tap do not), so any peer on such a transport can trigger it without authentication.Reference added —https://git.kernel.org/stable/c/180ff4c81faf01ec4e06082c9daa7c40518ead89Reference added —https://git.kernel.org/stable/c/4b9601595e8b6b5d18878cac0aeabc687d241111Reference added —https://git.kernel.org/stable/c/67d58ab4f2ccf7145f3da07e025735a09c79de1bReference added —https://git.kernel.org/stable/c/804b681002ead233abf49a3efd681f5468a835f9Reference added —https://git.kernel.org/stable/c/af421e9aed3920c7ac88c24daa48606c7112fecaSource 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-74478"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-74478.svg?lang=en" alt="CVE-2026-74478 – NEOSEC Intel" height="20"></a>