Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

HighCVSS 7.8 · v3.1—No exploit Fix available

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.12% (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 07ceb444c8f627cf863864d4274b5a77769725ed, 09e9206008b887aa553733bd915d73131071a086, 0d36653a3a821e5a974798adb347b3ea09332914; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 07ceb444c8f627cf863864d4274b5a77769725ed, 09e9206008b887aa553733bd915d73131071a086, 0d36653a3a821e5a974798adb347b3ea09332914; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes 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: 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.

Published
Apr 24, 2026
Updated
Nov 11, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

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%

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.

Follow CVE-2026-31578

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux kernel

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.14affected
    • cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c and later · before 0d36653a3a821e5a974798adb347b3ea09332914affected · git
    • cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c and later · before 25d500cf391e384356a612b85cf60b353ad3cd0caffected · git
    • cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c and later · before 07ceb444c8f627cf863864d4274b5a77769725edaffected · git
    • cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c and later · before cb8092038e95dc1113a68e63762de40fff61ba71affected · git
    • cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c and later · before 582fbecb3756330006fe1950762412a68c2cacd2affected · git
    • cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c and later · before 09e9206008b887aa553733bd915d73131071a086affected · git
    • cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c and later · before 2eeae47a438694408189138048a786be99954032affected · git
    • cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c and later · before 7e5aedf6059cba2a669d86caeaf5a51f33ec85a1affected · git
    • cd19f7d3e39b3160595d56bb3e3a2bf4f7f4669c and later · before 8bd29dbe03fc5b0f039ab2395ff37b64236d2f0caffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.176-16.1.176-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.14-16.19.14-1
openSUSE:Tumbleweedkernel-sourcebefore 7.0.3-1.17.0.3-1.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31576Apr 24, 2026 · media: hackrf: fix to not free memory after the device is registered in hackrf_probe()
    31Monitor
  • ← EarlierCVE-2026-31577Apr 24, 2026 · nilfs2: fix NULL i_assoc_inode dereference in nilfs_mdt_save_to_shadow_map
    22Monitor
  • Later →CVE-2026-31579Apr 24, 2026 · wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux07ceb444c8f627cf863864d4274b5a77769725edVendor (CNA)
Linux Linux09e9206008b887aa553733bd915d73131071a086Vendor (CNA)
Linux Linux0d36653a3a821e5a974798adb347b3ea09332914Vendor (CNA)
Linux Linux25d500cf391e384356a612b85cf60b353ad3cd0cVendor (CNA)
Linux Linux2eeae47a438694408189138048a786be99954032Vendor (CNA)
Linux Linux582fbecb3756330006fe1950762412a68c2cacd2Vendor (CNA)
Linux Linux7e5aedf6059cba2a669d86caeaf5a51f33ec85a1Vendor (CNA)
Linux Linux8bd29dbe03fc5b0f039ab2395ff37b64236d2f0cVendor (CNA)
Linux Linuxcb8092038e95dc1113a68e63762de40fff61ba71Vendor (CNA)
azl3 kernel 6.6.134.1-2 on Azure Linux 3.06.6.137.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.0.3-1.1 · openSUSE:TumbleweedPackage 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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.

References

All records