BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-31578High confidence

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

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 14 Jun 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.14-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.14-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-31578 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-31578
17 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-25471

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-416
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1279Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260429Security Bulletin 29 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Apr 2026, published on 29 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31550 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=CVE-2026-31586 Référence CVE CVE-2026-31588 https://www.cve.org/CVERecord?id=CVE-2026-31588 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31594 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1093Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31549 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=CVE-2026-31550 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=CVE-2026-31586 Référence CVE CVE-2026-31588 https://www.cve.org/CVERecord?id=CVE-2026-31588 Référence CVE CVE-2026-31589 https://www.cve.org/CVERecord?id=CVE-2026-31589 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31556 Référence CVE CVE-2026-31557 https://www.cve.org/CVERecord?id=CVE-2026-31557 Référence CVE CVE-2026-31563 https://www.cve.org/CVERecord?id=CVE-2026-31563 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31575 https://www.cve.org/CVERecord?id=CVE-2026-31575 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31582 https://www.cve.org/CVERecord?id=CVE-2026-31582 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31584 https://www.cve.org/CVERecord?id=CVE-2026-31584 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=CVE-2026-31586 Référence CVE CVE-2026-31587 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-31548 Référence CVE CVE-2026-31549 https://www.cve.org/CVERecord?id=CVE-2026-31549 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31557 https://www.cve.org/CVERecord?id=CVE-2026-31557 Référence CVE CVE-2026-31561 https://www.cve.org/CVERecord?id=CVE-2026-31561 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31582 https://www.cve.org/CVERecord?id=CVE-2026-31582 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31587 https://www.cve.org/CVERecord?id=CVE-2026-31587 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31591 https://www.cve.org/CVERecord?id=CVE-2026-31591 Référence CVE CVE-2026-31592 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0985Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31549 Référence CVE CVE-2026-31550 https://www.cve.org/CVERecord?id=CVE-2026-31550 Référence CVE CVE-2026-31551 https://www.cve.org/CVERecord?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=CVE-2026-31586 Référence CVE CVE-2026-31588 https://www.cve.org/CVERecord?id=CVE-2026-31588 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31594 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31557 Référence CVE CVE-2026-31563 https://www.cve.org/CVERecord?id=CVE-2026-31563 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31574 https://www.cve.org/CVERecord?id=CVE-2026-31574 Référence CVE CVE-2026-31575 https://www.cve.org/CVERecord?id=CVE-2026-31575 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31579 https://www.cve.org/CVERecord?id=CVE-2026-31579 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31582 https://www.cve.org/CVERecord?id=CVE-2026-31582 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31584 https://www.cve.org/CVERecord?id=CVE-2026-31584 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0927Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-31551 Référence CVE CVE-2026-31552 https://www.cve.org/CVERecord?id=CVE-2026-31552 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31561 https://www.cve.org/CVERecord?id=CVE-2026-31561 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31568 https://www.cve.org/CVERecord?id=CVE-2026-31568 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=CVE-2026-31586 Référence CVE CVE-2026-31587 https://www.cve.org/CVERecord?id=CVE-2026-31587 Référence CVE CVE-2026-31596 https://www.cve.org/CVERecord?id=CVE-2026-31596 Référence CVE CVE-2026-31599 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31557 Référence CVE CVE-2026-31563 https://www.cve.org/CVERecord?id=CVE-2026-31563 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31574 https://www.cve.org/CVERecord?id=CVE-2026-31574 Référence CVE CVE-2026-31575 https://www.cve.org/CVERecord?id=CVE-2026-31575 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31579 https://www.cve.org/CVERecord?id=CVE-2026-31579 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31582 https://www.cve.org/CVERecord?id=CVE-2026-31582 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31584 https://www.cve.org/CVERecord?id=CVE-2026-31584 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0862Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-31407 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31449 https://www.cve.org/CVERecord?id=CVE-2026-31449 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31489 https://www.cve.org/CVERecord?id=CVE-2026-31489 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=CVE-2026-31586 Référence CVE CVE-2026-31587 https://www.cve.org/CVERecord?id=CVE-2026-31587 Référence CVE CVE-2026-31588 https://www.cve.org/CVERecord?id=CVE-2026-31588 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0861Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31448 Référence CVE CVE-2026-31478 https://www.cve.org/CVERecord?id=CVE-2026-31478 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31574 https://www.cve.org/CVERecord?id=CVE-2026-31574 Référence CVE CVE-2026-31575 https://www.cve.org/CVERecord?id=CVE-2026-31575 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31579 https://www.cve.org/CVERecord?id=CVE-2026-31579 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31582 https://www.cve.org/CVERecord?id=CVE-2026-31582 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31584 https://www.cve.org/CVERecord?id=CVE-2026-31584 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0831Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31448 Référence CVE CVE-2026-31478 https://www.cve.org/CVERecord?id=CVE-2026-31478 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31574 https://www.cve.org/CVERecord?id=CVE-2026-31574 Référence CVE CVE-2026-31575 https://www.cve.org/CVERecord?id=CVE-2026-31575 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31579 https://www.cve.org/CVERecord?id=CVE-2026-31579 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31582 https://www.cve.org/CVERecord?id=CVE-2026-31582 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31584 https://www.cve.org/CVERecord?id=CVE-2026-31584 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0548Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2026-31559 Référence CVE CVE-2026-31561 https://www.cve.org/CVERecord?id=CVE-2026-31561 Référence CVE CVE-2026-31563 https://www.cve.org/CVERecord?id=CVE-2026-31563 Référence CVE CVE-2026-31565 https://www.cve.org/CVERecord?id=CVE-2026-31565 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31570 https://www.cve.org/CVERecord?id=CVE-2026-31570 Référence CVE CVE-2026-31575 https://www.cve.org/CVERecord?id=CVE-2026-31575 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=CVE-2026-31580 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31582 https://www.cve.org/CVERecord?id=CVE-2026-31582 Référence CVE CVE-2026-31583 https://www.cve.org/CVERecord?id=CVE-2026-31583 Référence CVE CVE-2026-31584 https://www.cve.org/CVERecord?id=CVE-2026-31584 Référence CVE CVE-2026-31585 https://www.cve.org/CVERecord?id=CVE-2026-31585 Référence CVE CVE-2026-31586 https://www.cve.org/CVERecord?id=CVE-2026-31586 Référence CVE CVE-2026-31587 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0526Multiples vulnérabilités dans les produits Microsoft

es d'information Paris, le 04 mai 2026 N° CERTFR-2026-AVI-0526 Affaire suivie par: CERT-FR Avis du CERT-FR Objet: Multiples vulnérabilités dans les produits Microsoft Gestion du document Référence CERTFR-2026-AVI-0526 Titre Multiples vulnérabilités dans les produits Microsoft Date de la première version 04 mai 2026 Date de la dernière version 04 mai 2026 Source(s) Bulletin de sécurité Microsoft CVE-2026-31430 du 22 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31431 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31532 du 24 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31577 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31578 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31583 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31585 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31586 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31587 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31588 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31590 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31594 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31595 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31596 du 26 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31597 du 26 avril 2026 Bu

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-013669LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。media: as102: as102_usb_probe()内でデバイス登録後にメモリを解放しないように修正されました。as102_usbドライバでは以下の競合状態が発生します。CPU0ではas102_usb_probe()内でkzalloc()によりas102_dev_tを割り当て、usb_register_dev()を呼び出します。一方、CPU1ではsys_open("/path/to/dev")でas102のファイルディスクリプタを開き、その後usb_deregister_dev()とkfree()でas102_dev_tを解放します。sys_close(fd)呼び出し時にはas102_release() → as102_usb_release() → kfree()が発生し、use-after-freeおよびdouble-freeの脆弱性が生じます。usb_register_dev()で登録されたUSBキャラクタデバイスがusb_deregister_dev()や切断によって登録解除されると、デバイスノードは削除されて新しいopen()は失敗しますが、既に開いているファイルディスクリプタは最後の参照が外れるまで有効です。また、ドライバの.release()が呼ばれるまで保持されます。as102_usb_probe()はエラーパスでusb_deregister_dev()後に即座にas102_dev_tを解放してしまうため、ユーザ空間での競合により解放済みメモリへのアクセスが発生し、脆弱性が生まれます。この問題の修正はusb_register_dev()成功後に直接kfree(as102_dev_t)をしないことであり、登録解除後のメモリ解放は.release()に遅延させます。つまり、最後のopenファイルディスクリプタが閉じられた時点で.release()が最終的にkfreeを行うようにしています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 3.14, 5.10.258 ≤ 5.10.*, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.136 ≤ 6.6.*, 6.12.83 ≤ 6.12.*, 6.18.24 ≤ 6.18.*, 6.19.14 ≤ 6.19.*, 7.0.1 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 24 Apr 2026 · Last source change 14 Jun 2026, 17:42 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-25471
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-25471↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-31578 · cve.blacktree.nl