CVE-2026-89877: media: saa7164: fix cleanup on resource allocation failure
Noroxi assessment
Priority: Monitor (action score 33/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.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 28e84c6e2e6753ed238ea097b2842a32a6a6879b, 4d2048466af9e2c960c5be6dcd317e3b657d268b, 69259c627009bf7621010ae9e997dad2dad3339c.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 28e84c6e2e6753ed238ea097b2842a32a6a6879b, 4d2048466af9e2c960c5be6dcd317e3b657d268b, 69259c627009bf7621010ae9e997dad2dad3339c 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: saa7164: fix cleanup on resource allocation failure saa7164_dev_setup() adds the device to the global saa7164_devlist before requesting the PCI BAR memory regions. If get_resources() fails, saa7164_dev_setup() decrements the device count and returns an error, but leaves the device on saa7164_devlist. The probe error path then frees the device, leaving a dangling entry on the global list. Reuse the existing MMIO mapping error path to remove the device from saa7164_devlist and decrement the device count before returning. Also release BAR0 if it was successfully requested but the BAR2 request fails.
- Published
- Sep 16, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- 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
- 2.6.32affected
- 443c1228d50518f3c550e1fef490a2c9d9246ce7 and later · before ac9d7ca8199c64c320ba8177e3c0f7b0deb7ff06affected · git
- 443c1228d50518f3c550e1fef490a2c9d9246ce7 and later · before 99bf01e2563f8bdfe5f25e489596cff455a35d6baffected · git
- 443c1228d50518f3c550e1fef490a2c9d9246ce7 and later · before daa5b32cdf7db81a07ee2a91ce092a363e7754aaaffected · git
- 443c1228d50518f3c550e1fef490a2c9d9246ce7 and later · before 77f216f8de6221efb6f6c471bc9e598f1879825baffected · git
- 443c1228d50518f3c550e1fef490a2c9d9246ce7 and later · before 69259c627009bf7621010ae9e997dad2dad3339caffected · git
- 443c1228d50518f3c550e1fef490a2c9d9246ce7 and later · before 4d2048466af9e2c960c5be6dcd317e3b657d268baffected · git
- 443c1228d50518f3c550e1fef490a2c9d9246ce7 and later · before fc65623524b5bf23baddc6ae688d954fba0d5de2affected · git
- 443c1228d50518f3c550e1fef490a2c9d9246ce7 and later · before 28e84c6e2e6753ed238ea097b2842a32a6a6879baffected · git
- before 2.6.32not 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-89875Sep 16, 2026 · media: ti: vpe: quiesce overflow recovery before freeing streams31Monitor
- ← EarlierCVE-2026-89876Sep 16, 2026 · media: tda18250: fix possible integer overflow0Monitor
- Later →CVE-2026-89878Sep 16, 2026 · media: s2255: check firmware size before reading trailing marker0Monitor
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 | 28e84c6e2e6753ed238ea097b2842a32a6a6879b | Vendor (CNA) |
| Linux Linux | 4d2048466af9e2c960c5be6dcd317e3b657d268b | Vendor (CNA) |
| Linux Linux | 69259c627009bf7621010ae9e997dad2dad3339c | Vendor (CNA) |
| Linux Linux | 77f216f8de6221efb6f6c471bc9e598f1879825b | Vendor (CNA) |
| Linux Linux | 99bf01e2563f8bdfe5f25e489596cff455a35d6b | Vendor (CNA) |
| Linux Linux | ac9d7ca8199c64c320ba8177e3c0f7b0deb7ff06 | Vendor (CNA) |
| Linux Linux | daa5b32cdf7db81a07ee2a91ce092a363e7754aa | Vendor (CNA) |
| Linux Linux | fc65623524b5bf23baddc6ae688d954fba0d5de2 | Vendor (CNA) |
| 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.
- No account or password is required.
- 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
- None
- 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:N/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/4d2048466af9e2c960c5be6dcd317e3b657d268b
- git.kernel.org/stable/c/69259c627009bf7621010ae9e997dad2dad3339c
- git.kernel.org/stable/c/77f216f8de6221efb6f6c471bc9e598f1879825b
- git.kernel.org/stable/c/99bf01e2563f8bdfe5f25e489596cff455a35d6b
- git.kernel.org/stable/c/ac9d7ca8199c64c320ba8177e3c0f7b0deb7ff06
- git.kernel.org/stable/c/daa5b32cdf7db81a07ee2a91ce092a363e7754aa
- git.kernel.org/stable/c/fc65623524b5bf23baddc6ae688d954fba0d5de2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.