CVE-2026-68215: media: radio-si476x: Unregister v4l2_device on probe failure
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.22% (FIRST EPSS).
- Fixed version: Linux Linux 436a693af04ffb889aaf87cb69ec1f2b21d3569c, 4ca9c9f12b1bc341a0a3bbbd2090fd182db53771, 64cb15878b35e5574ff4f80a0b613a79e47867ba; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 436a693af04ffb889aaf87cb69ec1f2b21d3569c, 4ca9c9f12b1bc341a0a3bbbd2090fd182db53771, 64cb15878b35e5574ff4f80a0b613a79e47867ba; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.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: radio-si476x: Unregister v4l2_device on probe failure si476x_radio_probe() registers radio->v4l2dev before allocating the V4L2 controls and before registering the video device. If any of those later steps fails, probe returns through the exit label after freeing only the control handler. A failed probe does not call si476x_radio_remove(), so the v4l2_device_unregister() there is not reached. This leaves the parent device reference taken by v4l2_device_register() behind on the error path. Unregister the V4L2 device in the probe error path after freeing the controls.
- Published
- Aug 10, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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
- b879a9c2a755d4ddf9e685258de6435710fd2f03 and later · before 828f8d2181aa09ff3d8b67e1d9c92d0dfc81026faffected · git
- b879a9c2a755d4ddf9e685258de6435710fd2f03 and later · before cac1c4f08cb2d8beaad16f7ddc7911f3711daa9faffected · git
- b879a9c2a755d4ddf9e685258de6435710fd2f03 and later · before 7cf393f176317a126d71e88e4b6e25e83499b465affected · git
- b879a9c2a755d4ddf9e685258de6435710fd2f03 and later · before 4ca9c9f12b1bc341a0a3bbbd2090fd182db53771affected · git
- b879a9c2a755d4ddf9e685258de6435710fd2f03 and later · before 7ef9f1659404544a8dddd68842bafcb4a38197afaffected · git
- b879a9c2a755d4ddf9e685258de6435710fd2f03 and later · before 64cb15878b35e5574ff4f80a0b613a79e47867baaffected · git
- b879a9c2a755d4ddf9e685258de6435710fd2f03 and later · before 730c235d7d2c80a401dac56b0f5066c889aa442daffected · git
- b879a9c2a755d4ddf9e685258de6435710fd2f03 and later · before 436a693af04ffb889aaf87cb69ec1f2b21d3569caffected · 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.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.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-68209Aug 10, 2026 · media: sun4i-csi: Return queued buffers on start_streaming() failure31Monitor
- ← EarlierCVE-2026-68210Aug 10, 2026 · media: stm32: dcmi: unregister notifier on probe failure31Monitor
- Later →CVE-2026-68219Aug 10, 2026 · media: nxp: imx8-isi: Fix potential out-of-bounds issues31Monitor
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 | 436a693af04ffb889aaf87cb69ec1f2b21d3569c | Vendor (CNA) |
| Linux Linux | 4ca9c9f12b1bc341a0a3bbbd2090fd182db53771 | Vendor (CNA) |
| Linux Linux | 64cb15878b35e5574ff4f80a0b613a79e47867ba | Vendor (CNA) |
| Linux Linux | 730c235d7d2c80a401dac56b0f5066c889aa442d | Vendor (CNA) |
| Linux Linux | 7cf393f176317a126d71e88e4b6e25e83499b465 | Vendor (CNA) |
| Linux Linux | 7ef9f1659404544a8dddd68842bafcb4a38197af | Vendor (CNA) |
| Linux Linux | 828f8d2181aa09ff3d8b67e1d9c92d0dfc81026f | Vendor (CNA) |
| Linux Linux | cac1c4f08cb2d8beaad16f7ddc7911f3711daa9f | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
Show all references (7 more)Show less
- git.kernel.org/stable/c/4ca9c9f12b1bc341a0a3bbbd2090fd182db53771
- git.kernel.org/stable/c/64cb15878b35e5574ff4f80a0b613a79e47867ba
- git.kernel.org/stable/c/730c235d7d2c80a401dac56b0f5066c889aa442d
- git.kernel.org/stable/c/7cf393f176317a126d71e88e4b6e25e83499b465
- git.kernel.org/stable/c/7ef9f1659404544a8dddd68842bafcb4a38197af
- git.kernel.org/stable/c/828f8d2181aa09ff3d8b67e1d9c92d0dfc81026f
- git.kernel.org/stable/c/cac1c4f08cb2d8beaad16f7ddc7911f3711daa9f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.