Skip to content
Noroxi
CVE-2026-80964· NVD / CVE Program· CNA Linux

ALSA: virmidi: Check card index validity at probe

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 368c521503e38e9bcfcf04c053eb1f85d22391b2, 3ee9cea821730805f232f1e4db0f95e7420477fc, 40ee4224e2fe24c05b92e4d37476adb6e83f10e9.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 368c521503e38e9bcfcf04c053eb1f85d22391b2, 3ee9cea821730805f232f1e4db0f95e7420477fc, 40ee4224e2fe24c05b92e4d37476adb6e83f10e9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: ALSA: virmidi: Check card index validity at probe virmidi driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver itself creates at the module probe time, but if the device is bound manually via sysfs interface, this could be -1 as "none", and this leads to OOB access for index[] and other parameters. Add a sanity check for the card index and warn/correct it if it's a value out of the range.

—No exploit Fix available
Published
Sep 11, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 6th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80964

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.16affected
    • 3564fbb880f9a62ddbb81b7440c32e0e6619c52d and later · before 3ee9cea821730805f232f1e4db0f95e7420477fcaffected · git
    • 3564fbb880f9a62ddbb81b7440c32e0e6619c52d and later · before ffefee7daf2362f534097422bb7f8894e798adfdaffected · git
    • 3564fbb880f9a62ddbb81b7440c32e0e6619c52d and later · before 368c521503e38e9bcfcf04c053eb1f85d22391b2affected · git
    • 3564fbb880f9a62ddbb81b7440c32e0e6619c52d and later · before 43f161c53279adac0517cf1c443e531e738b54ceaffected · git
    • 3564fbb880f9a62ddbb81b7440c32e0e6619c52d and later · before 40ee4224e2fe24c05b92e4d37476adb6e83f10e9affected · git
    • 3564fbb880f9a62ddbb81b7440c32e0e6619c52d and later · before f48c5f3b03afdb795e5f448a1d53d912d5b09f2eaffected · git
    • 3564fbb880f9a62ddbb81b7440c32e0e6619c52d and later · before b65d5182ecd6b7a24a83d980a0d06e809ef876c5affected · git
    • before 2.6.16not affected · semver
    • 5.15.221 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80962Sep 11, 2026 · dm-pcache: validate geometry fields from on-disk cache_info
    31Monitor
  • ← EarlierCVE-2026-80963Sep 11, 2026 · dm-stats: fix a crash if allocation of per-cpu data fails
    0Monitor
  • Later →CVE-2026-80965Sep 11, 2026 · ALSA: serial-u16550: Check card index validity at probe
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux368c521503e38e9bcfcf04c053eb1f85d22391b2Vendor (CNA)
Linux Linux3ee9cea821730805f232f1e4db0f95e7420477fcVendor (CNA)
Linux Linux40ee4224e2fe24c05b92e4d37476adb6e83f10e9Vendor (CNA)
Linux Linux43f161c53279adac0517cf1c443e531e738b54ceVendor (CNA)
Linux Linuxb65d5182ecd6b7a24a83d980a0d06e809ef876c5Vendor (CNA)
Linux Linuxf48c5f3b03afdb795e5f448a1d53d912d5b09f2eVendor (CNA)
Linux Linuxffefee7daf2362f534097422bb7f8894e798adfdVendor (CNA)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records