CVE-2026-99300
media: go7007: only set audio_enabled if go7007_snd_init() succeeded
What happened?
In the Linux kernel, the following vulnerability has been resolved:
media: go7007: only set audio_enabled if go7007_snd_init() succeeded
go7007_register_encoder() sets go->audio_enabled before calling go7007_snd_init() and discards its return value. go7007_snd_init() assigns go->snd_context only on success, so a failed ALSA setup leaves audio_enabled set with snd_context still NULL. The disconnect path tests audio_enabled and calls go7007_snd_remove(), which dereferences snd_context unconditionally.
go7007_snd_init() returns -ENODEV once its never-decremented static card counter reaches SNDRV_CARDS, so SNDRV_CARDS attach/detach cycles arm the next attach; no memory pressure is needed.
Set go->audio_enabled only once go7007_snd_init() has succeeded.
Oops: general protection fault, probably for non-canonical address ... KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] Workqueue: usb_hub_wq hub_event RIP: 0010:go7007_snd_remove (drivers/media/usb/go7007/snd-go7007.c:273) Call Trace: go7007_usb_disconnect (drivers/media/usb/go7007/go7007-usb.c:1336) usb_unbind_interface (drivers/usb/core/driver.c:461) device_remove (drivers/base/dd.c:618) device_release_driver_internal (drivers/base/dd.c:1349) bus_remove_device (drivers/base/bus.c:664) device_del (drivers/base/core.c:3965) usb_disable_device (drivers/usb/core/message.c:1478) usb_disconnect hub_event (drivers/usb/core/hub.c:5966) process_one_work (kernel/workqueue.c:3396) worker_thread (kernel/workqueue.c:3560) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) Kernel panic - not syncing: Fatal exception
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 866b8695d67e83f47194731d3a7ba55826a7ec70 to < 1db31d3ddc386a8094a34e186243e26ce8fd175d; affected: 866b8695d67e83f47194731d3a7ba55826a7ec70 to < 8e2fc3941b4005eaeef0a6b69b44a8a4941b57ab; affected: 866b8695d67e83f47194731d3a7ba55826a7ec70 to < 5d17cf3d380d56018a5ae8ef03af8df12ed910e9; affected: 866b8695d67e83f47194731d3a7ba55826a7ec70 to < 2eacf058d2dbb0ae3aaf576459da9e5f2b6bbfbd | See vendor advisory |
| LinuxLinux | affected: 2.6.28; unaffected: 0 to < 2.6.28; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99300
- https://git.kernel.org/stable/c/1db31d3ddc386a8094a34e186243e26ce8fd175d
- https://git.kernel.org/stable/c/8e2fc3941b4005eaeef0a6b69b44a8a4941b57ab
- https://git.kernel.org/stable/c/5d17cf3d380d56018a5ae8ef03af8df12ed910e9
- https://git.kernel.org/stable/c/2eacf058d2dbb0ae3aaf576459da9e5f2b6bbfbd