CVE-2026-98741

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-103826 (ENISA EUVD) · GHSA-3vm7-3m85-mm4q (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ALSA: ua101: reject mismatched capture/playback packet sizes

detect_usb_format() cross-checks bSubframeSize, bBitResolution and tSamFreq between the capture and playback interfaces, but never relates the two endpoints' wMaxPacketSize and bNrChannels. Each playback URB gets a buffer of ua->playback.max_packet_bytes, while the number of bytes written into it is derived from the capture stream: capture_urb_complete() computes frames from the received capture packet and capture.frame_bytes, and start_usb_playback() and playback_work() multiply that by playback.frame_bytes.

A device declaring a large capture wMaxPacketSize with few capture channels and a small playback wMaxPacketSize with many playback channels therefore memset()s and memcpy()s past the end of the playback buffer, in open() of the PCM node the driver registers during probe. usb_submit_urb() rejects the over-long iso_frame_desc[0].length with -EMSGSIZE, but only after the write.

Reject such descriptors at probe time. Genuine UA-101/UA-1000 hardware declares proportional packet sizes and is unaffected.

BUG: KASAN: slab-out-of-bounds in start_usb_playback (sound/usb/misc/ua101.c:586) Write of size 2048 at addr ffff8881098f3c00 by task exploit/5021 Call Trace: __asan_memset (mm/kasan/shadow.c:84) start_usb_playback (sound/usb/misc/ua101.c:586) playback_pcm_open (sound/usb/misc/ua101.c:679) snd_pcm_open_substream (sound/core/pcm_native.c:2829) snd_pcm_open (sound/core/pcm_native.c:2865 sound/core/pcm_native.c:2932) snd_pcm_playback_open (sound/core/pcm_native.c:2891) snd_open (sound/core/sound.c:166) chrdev_open (fs/char_dev.c:411) do_dentry_open (fs/open.c:996) vfs_open (fs/open.c:1101) path_openat (fs/namei.c:4837 fs/namei.c:5000) do_file_open (fs/namei.c:5029) do_sys_openat2 (fs/open.c:1417) __x64_sys_openat (fs/open.c:1423 fs/open.c:1439 fs/open.c:1434) do_syscall_64 (arch/x86/entry/syscall_64.c:61 arch/x86/entry/syscall_64.c:84) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)

The buggy address belongs to the object at ffff8881098f3c00 which belongs to the cache kmalloc-192 of size 192 The buggy address is located 0 bytes inside of allocated 168-byte region [ffff8881098f3c00, ffff8881098f3ca8)

CVSS
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 18, 2026

Last Modified

October 30, 2026

References (8)

Vendor Advisories for CVE-2026-98741(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.6.160 (fixes >=2.6.34)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc7-1~exp1 (371 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1, 6.12.111-1~deb12u1
  • every version up to 6.12.113-1~deb12u1: fixed in 6.12.113-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (36 versions)
  • every version up to 6.12.113-1: fixed in 6.12.113-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (185 versions)
  • every version up to 7.2.10-1: fixed in 7.2.10-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-11-08 16:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-30 13:42 UTCVendor advisory
  16. 2026-10-30 13:41 UTCGHSA enrichmentGHSA-3vm7-3m85-mm4q
  17. 2026-10-30 13:27 UTCNVD update
  18. 2026-10-30 12:46 UTCEchelonGraph re-scored
  19. 2026-10-30 12:46 UTCVendor advisory
  20. 2026-10-30 12:46 UTCGHSA enrichmentGHSA-3vm7-3m85-mm4q
  21. 2026-10-30 12:41 UTCMITRE cvelistV5
  22. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-29 08:55 UTCOSV refresh
  24. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 22 more
  1. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-25 13:46 UTCEchelonGraph re-scored
  3. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-21 14:33 UTCVendor advisory
  8. 2026-10-21 14:33 UTCGHSA enrichmentGHSA-3vm7-3m85-mm4q
  9. 2026-10-21 14:28 UTCNVD update
  10. 2026-10-21 13:12 UTCEchelonGraph re-scored
  11. 2026-10-21 13:12 UTCVendor advisory
  12. 2026-10-21 13:12 UTCGHSA enrichmentGHSA-3vm7-3m85-mm4q
  13. 2026-10-21 13:09 UTCMITRE cvelistV5
  14. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-19 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-19 10:52 UTCGHSA enrichmentGHSA-3vm7-3m85-mm4q
  17. 2026-10-19 10:26 UTCNVD update
  18. 2026-10-19 10:07 UTCGHSA enrichmentGHSA-3vm7-3m85-mm4q
  19. 2026-10-19 09:39 UTCMITRE cvelistV5
  20. 2026-10-18 16:25 UTCNVD update
  21. 2026-10-18 15:56 UTCEchelonGraph re-scored
  22. 2026-10-18 15:53 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-98741?
CVE-2026-98741 is a vulnerability whose severity is not yet rated; its CVE record was published on October 18, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: ua101: reject mismatched capture/playback packet sizes detect_usb_format() cross-checks bSubframeSize, bBitResolution and tSamFreq between the capture and playback interfaces, but never relates the two endpoints'…
When was the CVE record for CVE-2026-98741 published?
The CVE record for CVE-2026-98741 was published on October 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-98741 actively exploited?
CVE-2026-98741 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-98741?
A fix for CVE-2026-98741 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98741 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-98741

Explore →

Is Your Infrastructure Affected by CVE-2026-98741?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs