CVE-2026-89890: media: go7007: defer the ALSA v4l2 put until card release
Noroxi assessment
Priority: Monitor (action score 31/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.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0745a59945d927652d892437f9647ed6e87c0677, 1bd456afeb8a515137e567967069fce6f8fcd23e, 1c57d1a3396b2d767d58f10dff09bb397586c714; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0745a59945d927652d892437f9647ed6e87c0677, 1bd456afeb8a515137e567967069fce6f8fcd23e, 1c57d1a3396b2d767d58f10dff09bb397586c714; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 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: media: go7007: defer the ALSA v4l2 put until card release go7007_snd_init() already takes a v4l2_device reference for the ALSA side, but go7007_snd_remove() drops it immediately after calling snd_card_free_when_closed(). That is too early when a userspace process still has the capture PCM open. The ALSA card and its PCM callbacks remain alive until the last file is closed, so the release path can still reach struct go7007 through pcm->private_data and call go7007_snd_hw_free() after the V4L2 release path has freed the object. Move the matching v4l2_device_put() to the ALSA card private_free callback so the existing ALSA reference covers the whole deferred card lifetime.
- Published
- Sep 16, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 3.10affected
- d5d3a7cc127d096c22ad63c4ff72970e1beb22ef and later · before 1c57d1a3396b2d767d58f10dff09bb397586c714affected · git
- d5d3a7cc127d096c22ad63c4ff72970e1beb22ef and later · before 9c4f9628b8558c87903492a777834cc5be14ded3affected · git
- d5d3a7cc127d096c22ad63c4ff72970e1beb22ef and later · before b7a0de398ad510426db9c8e96c516ef7abf48b0eaffected · git
- d5d3a7cc127d096c22ad63c4ff72970e1beb22ef and later · before 1c9fdd9465211432d5c0ff70caaec0be245823d5affected · git
- d5d3a7cc127d096c22ad63c4ff72970e1beb22ef and later · before 29fe4d38fb59ec28ca656cb2dabc2b0f78e78980affected · git
- d5d3a7cc127d096c22ad63c4ff72970e1beb22ef and later · before 0745a59945d927652d892437f9647ed6e87c0677affected · git
- d5d3a7cc127d096c22ad63c4ff72970e1beb22ef and later · before e6f1a1ac9b8ccabfec548aef0d0d93eaf4dba4f4affected · git
- d5d3a7cc127d096c22ad63c4ff72970e1beb22ef and later · before 1bd456afeb8a515137e567967069fce6f8fcd23eaffected · git
- before 3.10not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89888Sep 16, 2026 · media: i2c: ov02a10: fix endpoint parsing use-after-free31Monitor
- ← EarlierCVE-2026-89889Sep 16, 2026 · media: i2c: imx415: Release runtime PM reference on VBLANK error0Monitor
- Later →CVE-2026-89891Sep 16, 2026 · media: em28xx: fix use-after-free of dev_next->devlist on disconnect0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0745a59945d927652d892437f9647ed6e87c0677 | Vendor (CNA) |
| Linux Linux | 1bd456afeb8a515137e567967069fce6f8fcd23e | Vendor (CNA) |
| Linux Linux | 1c57d1a3396b2d767d58f10dff09bb397586c714 | Vendor (CNA) |
| Linux Linux | 1c9fdd9465211432d5c0ff70caaec0be245823d5 | Vendor (CNA) |
| Linux Linux | 29fe4d38fb59ec28ca656cb2dabc2b0f78e78980 | Vendor (CNA) |
| Linux Linux | 9c4f9628b8558c87903492a777834cc5be14ded3 | Vendor (CNA) |
| Linux Linux | b7a0de398ad510426db9c8e96c516ef7abf48b0e | Vendor (CNA) |
| Linux Linux | e6f1a1ac9b8ccabfec548aef0d0d93eaf4dba4f4 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package 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.
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.
Credits
All researchersFinders, 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.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1bd456afeb8a515137e567967069fce6f8fcd23e
- git.kernel.org/stable/c/1c57d1a3396b2d767d58f10dff09bb397586c714
- git.kernel.org/stable/c/1c9fdd9465211432d5c0ff70caaec0be245823d5
- git.kernel.org/stable/c/29fe4d38fb59ec28ca656cb2dabc2b0f78e78980
- git.kernel.org/stable/c/9c4f9628b8558c87903492a777834cc5be14ded3
- git.kernel.org/stable/c/b7a0de398ad510426db9c8e96c516ef7abf48b0e
- git.kernel.org/stable/c/e6f1a1ac9b8ccabfec548aef0d0d93eaf4dba4f4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.