Back to CVE records
High 7.8Published Apr 24, 2026

CVE-2026-31578media: as102: fix to not free memory after the device is registered in as102_usb_probe()

Updated under an hour ago ()

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

In the Linux kernel, the following vulnerability has been resolved: media: as102: fix to not free memory after the device is registered in as102_usb_probe() In as102_usb driver, the following race condition occurs: ``` CPU0 CPU1 as102_usb_probe() kzalloc(); // alloc as102_dev_t .... usb_register_dev(); fd = sys_open("/path/to/dev"); // open as102 fd .... usb_deregister_dev(); .... kfree(); // free as102_dev_t .... sys_close(fd); as102_release() // UAF!! as102_usb_release() kfree(); // DFB!! ``` When a USB character device registered with usb_register_dev() is later unregistered (via usb_deregister_dev() or disconnect), the device node is removed so new open() calls fail. However, file descriptors that are already open do not go away immediately: they remain valid until the last reference is dropped and the driver's .release() is invoked. In as102, as102_usb_probe() calls usb_register_dev() and then, on an error path, does usb_deregister_dev() and frees as102_dev_t right away. If userspace raced a successful open() before the deregistration, that open FD will later hit as102_release() --> as102_usb_release() and access or free as102_dev_t again, occur a race to use-after-free and double-free vuln. The fix is to never kfree(as102_dev_t) directly once usb_register_dev() has succeeded. After deregistration, defer freeing memory to .release(). In other words, let release() perform the last kfree when the final open FD is closed.

CVSS
7.8 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Modified
Record last updated
Jun 14, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c before 0d36653a3a821e5a974798adb347b3ea09332914; from cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c before 25d500cf391e384356a612b85cf60b353ad3cd0c; from cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c before 07ceb444c8f627cf863864d4274b5a77769725ed; from cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c before cb8092038e95dc1113a68e63762de40fff61ba71; from cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c before 582fbecb3756330006fe1950762412a68c2cacd2; from cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c before 09e9206008b887aa553733bd915d73131071a086; from cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c before 2eeae47a438694408189138048a786be99954032; from cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c before 7e5aedf6059cba2a669d86caeaf5a51f33ec85a1; and 1 more ranges
CNA record
linux linux_kernel
linux:linux_kernel
before 6.6.136; from 6.7 before 6.12.83; from 6.13 before 6.18.24; from 6.19 before 6.19.14; from 7.0 before 7.0.1
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.