Linux Kernel: security vulnerability (CVE-2026-98428)
Published Last modified Sources: Debian LTS, HKCERT, Ubuntu, SUSE, Debian, BSI, EUVD, CVE.org
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: ALSA: usb: 6fire: Avoid embedded URBs The USB 6fire driver uses URBs embedded in different structs for PCM, MIDI and communication, and this is basically a buggy implementation nowadays; since a URB is managed with a refcount, this may lead to a UAF when the URB is released asynchronously. For addressing the problem, this patch converts those embedded URBs to ones that are properly allocated via usb_alloc_urb().
Update Linux Kernel to version 6.1.189, Linux Kernel to version 6.6.158, Linux Kernel to version 6.12.112.
- Affected
- Linux Kernel
lt 2.6.39..6.1.189 - Linux Kernel
lt 6.2..6.6.158 - Linux Kernel
lt 6.7..6.12.112 - Linux Kernel
lt 6.13..6.18.54 - Linux Kernel
lt 6.19..7.2.8
- Linux Kernel
- Fixed in
- Linux Kernel
6.1.189 - Linux Kernel
6.6.158 - Linux Kernel
6.12.112 - Linux Kernel
6.18.54 - Linux Kernel
7.2.8 - Linux Kernel
7.3
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
XIEM Effective CVSS
No value is available for this vulnerability.
0.0
CVSS v3
Severity Not rated on the scale from 0 to 10.
Source: Debian LTS, HKCERT, Ubuntu, SUSE, Debian, BSI, EUVD, CVE.org
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 12.0
Show all metrics
- Severity
- Not rated
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- 31.15 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
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- 0.0
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- 12.0
- Elevated — this CVE ranks above at least 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: ALSA: usb: 6fire: Avoid embedded URBs The USB 6fire driver uses URBs embedded in different structs for PCM, MIDI and communication, and this is basically a buggy implementation nowadays; since a URB is managed with a refcount, this may lead to a UAF when the URB is released asynchronously. For addressing the problem, this patch converts those embedded URBs to ones that are properly allocated via usb_alloc_urb(). The pcm_urb.packets[] is gone, as it's allocated by usb_alloc_urb(), hence it's found in urb.iso_frame_desc[] instead. The conversions are rather straightforward; each embedded struct urb is changed to a pointer, and its callers are updated accordingly. The resource for those structs are released in the common destructor functions (usb6fire_comm_free(), etc), which are called at both the init error path and the disconnect. No functional changes, only compile-tested.
Source: Debian LTS Advisories, HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Ubuntu Security Notices, suse_csaf, Debian Security Advisories, BSI WID Portal, BSI CSAF, ENISA EUVD, cvelistv5, NVD (NIST)
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 | ubuntu | linux | noble |
| Linux | ubuntu | linux | resolute |
| Linux | debian | linux-6.12 | bookworm |
| Linux | ubuntu | linux-aws | noble |
| Linux | ubuntu | linux-aws | resolute |
| Linux | ubuntu | linux-aws-6.8 | jammy |
| Linux | ubuntu | linux-aws-7.0 | noble |
| Linux | ubuntu | linux-aws-fips | noble |
| Linux | ubuntu | linux-azure | noble |
| Linux | ubuntu | linux-azure | resolute |
| Linux | ubuntu | linux-azure-6.8 | jammy |
| Linux | ubuntu | linux-azure-fde | noble |
| Linux | ubuntu | linux-azure-fde | resolute |
| Linux | ubuntu | linux-azure-fde-6.8 | jammy |
| Linux | ubuntu | linux-azure-fde-7.0 | noble |
| Linux | ubuntu | linux-azure-fips | noble |
| Linux | ubuntu | linux-gcp | noble |
| Linux | ubuntu | linux-gcp | resolute |
| Linux | ubuntu | linux-gcp-6.8 | jammy |
| Linux | ubuntu | linux-gcp-7.0 | noble |
| Linux | ubuntu | linux-gcp-fips | noble |
| Linux | ubuntu | linux-gke | noble |
References & sources
- git.kernel.orgstable/c/3ef9093d83ffecb8e5f6c9d5769a52d39df74f7aeuvd
- git.kernel.orgstable/c/8b8559aeaba2e51cfee1779b2383b085991f7d81euvd
- git.kernel.orgstable/c/52a43c2d57e774489ac3fbbac06ff02f19bd9a52euvd
- git.kernel.orgstable/c/999f433c09e4668412bd68ca207ae2b4af863862euvd
- git.kernel.orgstable/c/d181434549b3da668110a25d743848cce9897f4eeuvd
- git.kernel.orgstable/c/9fe49dbc023e82dfaee7b245997d820d01742a9aeuvd
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/98xxx/CVE-2026-98428.json">CVE-2026-98428</a>Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
ReceivedLinux
Description added or changed
New references:- https://git.kernel.org/stable/c/3ef9093d83ffecb8e5f6c9d5769a52d39df74f7a
- https://git.kernel.org/stable/c/52a43c2d57e774489ac3fbbac06ff02f19bd9a52
- https://git.kernel.org/stable/c/8b8559aeaba2e51cfee1779b2383b085991f7d81
- https://git.kernel.org/stable/c/999f433c09e4668412bd68ca207ae2b4af863862
and 2 more references
Show 8 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: ALSA: usb: 6fire: Avoid embedded URBs The USB 6fire driver uses URBs embedded in different structs for PCM, MIDI and communication, and this is basically a buggy implementation nowadays; since a URB is managed with a refcount, this may lead to a UAF when the URB is released asynchronously. For addressing the problem, this patch converts those embedded URBs to ones that are properly allocated via usb_alloc_urb(). The pcm_urb.packets[] is gone, as it's allocated by usb_alloc_urb(), hence it's found in urb.iso_frame_desc[] instead. The conversions are rather straightforward; each embedded struct urb is changed to a pointer, and its callers are updated accordingly. The resource for those structs are released in the common destructor functions (usb6fire_comm_free(), etc), which are called at both the init error path and the disconnect. No functional changes, only compile-tested.Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/98xxx/CVE-2026-98428.json">CVE-2026-98428</a>Reference added —https://git.kernel.org/stable/c/3ef9093d83ffecb8e5f6c9d5769a52d39df74f7aReference added —https://git.kernel.org/stable/c/52a43c2d57e774489ac3fbbac06ff02f19bd9a52Reference added —https://git.kernel.org/stable/c/8b8559aeaba2e51cfee1779b2383b085991f7d81Reference added —https://git.kernel.org/stable/c/999f433c09e4668412bd68ca207ae2b4af863862Reference added —https://git.kernel.org/stable/c/9fe49dbc023e82dfaee7b245997d820d01742a9aReference added —https://git.kernel.org/stable/c/d181434549b3da668110a25d743848cce9897f4eSource 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-98428"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-98428.svg?lang=en" alt="CVE-2026-98428 – NEOSEC Intel" height="20"></a>