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

serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 220 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.52% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 3 daysRemediation target: Within 90 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 220 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.95-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.177-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.14-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.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.

2 current
CVE-2026-53384 · CSAF 2.0 · revision 7 · interimSUSE Product Security TeamCVE-2026-53384
227 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails dw8250_probe() registers the 8250 port via serial8250_register_8250_port() and then, if the device has a clock, registers a clock notifier. If clk_notifier_register() fails, probe returns the error but leaves the 8250 port registered. The matching serial8250_unregister_port() lives in dw8250_remove(), which is not called when probe fails, so the port slot stays occupied until the device is rebound or the system is rebooted. The devm-allocated driver data is freed while the port still references it (via the saved private_data and serial_in/serial_out callbacks), so any access to that port slot before a rebind is a use-after-free hazard. Unregister the port on the clk_notifier_register() error path.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-53384 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails
200 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's 8250_dw serial driver. When the `clk_notifier_register()` function fails during the probe process, the 8250 port is not properly unregistered. This oversight can lead to a use-after-free vulnerability, where previously freed memory is still referenced. An attacker could potentially exploit this to cause system instability or execute arbitrary code.
Remediation
Affected
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-45506

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

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 220 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: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails dw8250_probe() registers the 8250 port via serial8250_register_8250_port() and then, if the device has a clock, registers a clock notifier. If clk_notifier_register() fails, probe returns the error but leaves the 8250 port registered. The matching serial8250_unregister_port() lives in dw8250_remove(), which is not called when probe fails, so the port slot stays occupied until the device is rebound or the system is rebooted. The devm-allocated driver data is freed while the port still references it (via the saved private_data and serial_in/serial_out callbacks), so any access to that port slot before a rebind is a use-after-free hazard. Unregister the port on the clk_notifier_register() error path.

What

In the Linux kernel, the following vulnerability has been resolved: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails dw8250_probe() registers the 8250 port via serial8250_register_8250_port() and then, if the device has a clock, registers a clock notifier. If clk_notifier_register() fails, probe returns the error but leaves the 8250 port registered. The matching serial8250_unregister_port() lives in dw8250_remove(), which is not called when probe fails, so the port slot stays occupied until the device is rebound or the system is rebooted. The devm-allocated driver data is freed while the port still references it (via the saved private_data and serial_in/serial_out callbacks), so any access to that port slot before a rebind is a use-after-free hazard. Unregister the port on the clk_notifier_register() error path.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails dw8250_probe() registers the 8250 port via serial8250_register_8250_port() and then, if the device has a clock, registers a clock notifier. If clk_notifier_register() fails, probe returns the error but leaves the 8250 port registered. The matching serial8250_unregister_port() lives in dw8250_remove(), which is not called when probe fails, so the port slot stays occupied until the device is rebound or the system is rebooted. The devm-allocated driver data is freed while the port still references it (via the saved private_data and serial_in/serial_out callbacks), so any access to that port slot before a rebind is a use-after-free hazard. Unregister the port on the clk_notifier_register() error path.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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
a network path → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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:N/AC:L/PR:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-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-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

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

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

d?id=CVE-2026-53375 Référence CVE CVE-2026-53376 https://www.cve.org/CVERecord?id=CVE-2026-53376 Référence CVE CVE-2026-53377 https://www.cve.org/CVERecord?id=CVE-2026-53377 Référence CVE CVE-2026-53378 https://www.cve.org/CVERecord?id=CVE-2026-53378 Référence CVE CVE-2026-53379 https://www.cve.org/CVERecord?id=CVE-2026-53379 Référence CVE CVE-2026-53380 https://www.cve.org/CVERecord?id=CVE-2026-53380 Référence CVE CVE-2026-53381 https://www.cve.org/CVERecord?id=CVE-2026-53381 Référence CVE CVE-2026-53382 https://www.cve.org/CVERecord?id=CVE-2026-53382 Référence CVE CVE-2026-53383 https://www.cve.org/CVERecord?id=CVE-2026-53383 Référence CVE CVE-2026-53384 https://www.cve.org/CVERecord?id=CVE-2026-53384 Référence CVE CVE-2026-53385 https://www.cve.org/CVERecord?id=CVE-2026-53385 Référence CVE CVE-2026-53386 https://www.cve.org/CVERecord?id=CVE-2026-53386 Référence CVE CVE-2026-53387 https://www.cve.org/CVERecord?id=CVE-2026-53387 Référence CVE CVE-2026-53388 https://www.cve.org/CVERecord?id=CVE-2026-53388 Référence CVE CVE-2026-53389 https://www.cve.org/CVERecord?id=CVE-2026-53389 Référence CVE CVE-2026-53390 https://www.cve.org/CVERecord?id=CVE-2026-53390 Référence CVE CVE-2026-53391 https://www.cve.org/CVERecord?id=CVE-2026-53391 Référence CVE CVE-2026-53392 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53375 Référence CVE CVE-2026-53376 https://www.cve.org/CVERecord?id=CVE-2026-53376 Référence CVE CVE-2026-53377 https://www.cve.org/CVERecord?id=CVE-2026-53377 Référence CVE CVE-2026-53378 https://www.cve.org/CVERecord?id=CVE-2026-53378 Référence CVE CVE-2026-53379 https://www.cve.org/CVERecord?id=CVE-2026-53379 Référence CVE CVE-2026-53380 https://www.cve.org/CVERecord?id=CVE-2026-53380 Référence CVE CVE-2026-53381 https://www.cve.org/CVERecord?id=CVE-2026-53381 Référence CVE CVE-2026-53382 https://www.cve.org/CVERecord?id=CVE-2026-53382 Référence CVE CVE-2026-53383 https://www.cve.org/CVERecord?id=CVE-2026-53383 Référence CVE CVE-2026-53384 https://www.cve.org/CVERecord?id=CVE-2026-53384 Référence CVE CVE-2026-53385 https://www.cve.org/CVERecord?id=CVE-2026-53385 Référence CVE CVE-2026-53386 https://www.cve.org/CVERecord?id=CVE-2026-53386 Référence CVE CVE-2026-53387 https://www.cve.org/CVERecord?id=CVE-2026-53387 Référence CVE CVE-2026-53388 https://www.cve.org/CVERecord?id=CVE-2026-53388 Référence CVE CVE-2026-53389 https://www.cve.org/CVERecord?id=CVE-2026-53389 Référence CVE CVE-2026-53390 https://www.cve.org/CVERecord?id=CVE-2026-53390 Référence CVE CVE-2026-53391 https://www.cve.org/CVERecord?id=CVE-2026-53391 Référence CVE CVE-2026-53392 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53359 Référence CVE CVE-2026-53361 https://www.cve.org/CVERecord?id=CVE-2026-53361 Référence CVE CVE-2026-53362 https://www.cve.org/CVERecord?id=CVE-2026-53362 Référence CVE CVE-2026-53363 https://www.cve.org/CVERecord?id=CVE-2026-53363 Référence CVE CVE-2026-53366 https://www.cve.org/CVERecord?id=CVE-2026-53366 Référence CVE CVE-2026-53368 https://www.cve.org/CVERecord?id=CVE-2026-53368 Référence CVE CVE-2026-53381 https://www.cve.org/CVERecord?id=CVE-2026-53381 Référence CVE CVE-2026-53382 https://www.cve.org/CVERecord?id=CVE-2026-53382 Référence CVE CVE-2026-53383 https://www.cve.org/CVERecord?id=CVE-2026-53383 Référence CVE CVE-2026-53384 https://www.cve.org/CVERecord?id=CVE-2026-53384 Référence CVE CVE-2026-53385 https://www.cve.org/CVERecord?id=CVE-2026-53385 Référence CVE CVE-2026-53386 https://www.cve.org/CVERecord?id=CVE-2026-53386 Référence CVE CVE-2026-53387 https://www.cve.org/CVERecord?id=CVE-2026-53387 Référence CVE CVE-2026-53388 https://www.cve.org/CVERecord?id=CVE-2026-53388 Référence CVE CVE-2026-53389 https://www.cve.org/CVERecord?id=CVE-2026-53389 Référence CVE CVE-2026-53390 https://www.cve.org/CVERecord?id=CVE-2026-53390 Référence CVE CVE-2026-53391 https://www.cve.org/CVERecord?id=CVE-2026-53391 Référence CVE CVE-2026-53392 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53375 Référence CVE CVE-2026-53376 https://www.cve.org/CVERecord?id=CVE-2026-53376 Référence CVE CVE-2026-53377 https://www.cve.org/CVERecord?id=CVE-2026-53377 Référence CVE CVE-2026-53378 https://www.cve.org/CVERecord?id=CVE-2026-53378 Référence CVE CVE-2026-53379 https://www.cve.org/CVERecord?id=CVE-2026-53379 Référence CVE CVE-2026-53380 https://www.cve.org/CVERecord?id=CVE-2026-53380 Référence CVE CVE-2026-53381 https://www.cve.org/CVERecord?id=CVE-2026-53381 Référence CVE CVE-2026-53382 https://www.cve.org/CVERecord?id=CVE-2026-53382 Référence CVE CVE-2026-53383 https://www.cve.org/CVERecord?id=CVE-2026-53383 Référence CVE CVE-2026-53384 https://www.cve.org/CVERecord?id=CVE-2026-53384 Référence CVE CVE-2026-53385 https://www.cve.org/CVERecord?id=CVE-2026-53385 Référence CVE CVE-2026-53386 https://www.cve.org/CVERecord?id=CVE-2026-53386 Référence CVE CVE-2026-53387 https://www.cve.org/CVERecord?id=CVE-2026-53387 Référence CVE CVE-2026-53388 https://www.cve.org/CVERecord?id=CVE-2026-53388 Référence CVE CVE-2026-53389 https://www.cve.org/CVERecord?id=CVE-2026-53389 Référence CVE CVE-2026-53390 https://www.cve.org/CVERecord?id=CVE-2026-53390 Référence CVE CVE-2026-53391 https://www.cve.org/CVERecord?id=CVE-2026-53391 Référence CVE CVE-2026-53392 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53167 Référence CVE CVE-2026-53325 https://www.cve.org/CVERecord?id=CVE-2026-53325 Référence CVE CVE-2026-53327 https://www.cve.org/CVERecord?id=CVE-2026-53327 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53362 https://www.cve.org/CVERecord?id=CVE-2026-53362 Référence CVE CVE-2026-53366 https://www.cve.org/CVERecord?id=CVE-2026-53366 Référence CVE CVE-2026-53381 https://www.cve.org/CVERecord?id=CVE-2026-53381 Référence CVE CVE-2026-53382 https://www.cve.org/CVERecord?id=CVE-2026-53382 Référence CVE CVE-2026-53383 https://www.cve.org/CVERecord?id=CVE-2026-53383 Référence CVE CVE-2026-53384 https://www.cve.org/CVERecord?id=CVE-2026-53384 Référence CVE CVE-2026-53385 https://www.cve.org/CVERecord?id=CVE-2026-53385 Référence CVE CVE-2026-53388 https://www.cve.org/CVERecord?id=CVE-2026-53388 Référence CVE CVE-2026-53390 https://www.cve.org/CVERecord?id=CVE-2026-53390 Référence CVE CVE-2026-53391 https://www.cve.org/CVERecord?id=CVE-2026-53391 Référence CVE CVE-2026-53397 https://www.cve.org/CVERecord?id=CVE-2026-53397 Référence CVE CVE-2026-53398 https://www.cve.org/CVERecord?id=CVE-2026-53398 Référence CVE CVE-2026-53403 https://www.cve.org/CVERecord?id=CVE-2026-53403 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。serial: 8250_dwにおいて、clk_notifier_register() の失敗時に8250ポートの登録解除を行うdw8250_probe()は、serial8250_register_8250_port()を介して8250ポートを登録し、その後、デバイスにクロックがある場合はクロックノティファイアを登録します。もしclk_notifier_register()が失敗すると、probeはエラーを返しますが、8250ポートの登録を解除しません。対応するserial8250_unregister_port()はdw8250_remove()内にありますが、probeが失敗した場合は呼び出されないため、ポートスロットはデバイスが再バインドされるかシステムが再起動されるまで占有されたままになります。devmで割り当てられたドライバデータは既に解放されていますが、ポートは未だに（保存されたprivate_dataおよびserial_in/serial_outコールバックを介して）そのデータを参照しています。そのため、再バインド前にそのポートスロットにアクセスすると、利用後解放(use-after-free)の危険があります。clk_notifier_register()エラー時のパスでポートの登録解除を行うことで問題を修正しました。

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: < 5.19, 6.1.177 ≤ 6.1.*, 6.6.144 ≤ 6.6.*, 6.12.95 ≤ 6.12.*, 6.18.38 ≤ 6.18.*, 7.0.14 ≤ 7.0.*, 7.1.2 ≤ 7.1.*, 7.2 ≤ *
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2026 · Last source change 17 Aug 2026, 04:50 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-45506
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    57f83e5dd6a33c4696699954784f8fee789b1d0c < ccdf4510a3873b14e5e348cdb038717996f09fda; 57f83e5dd6a33c4696699954784f8fee789b1d0c < 511d2b92f8d20de04acafab676150d26fb5c67f4; 57f83e5dd6a33c4696699954784f8fee789b1d0c < 07ffe414a708ae60551401cec5d727ed156b8caf; 57f83e5dd6a33c4696699954784f8fee789b1d0c < 3d205fe80f2181f0109150ad1fa06ee5bc046935; 57f83e5dd6a33c4696699954784f8fee789b1d0c < d72650a4f334581b23a1892b888a4cb1be142f76; 57f83e5dd6a33c4696699954784f8fee789b1d0c < 778b9dda4b24005a27bcd9c35c110bf8d7f259ca; 57f83e5dd6a33c4696699954784f8fee789b1d0c < 10fc708b4de7f86002d2d735a2dbf3b5b7f65692; 5.19 · Fixed: < 5.19; 6.1.177 ≤ 6.1.*; 6.6.144 ≤ 6.6.*; 6.12.95 ≤ 6.12.*; 6.18.38 ≤ 6.18.*; 7.0.14 ≤ 7.0.*; 7.1.2 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    57f83e5dd6a33c4696699954784f8fee789b1d0c < ccdf4510a3873b14e5e348cdb038717996f09fda; 57f83e5dd6a33c4696699954784f8fee789b1d0c < 511d2b92f8d20de04acafab676150d26fb5c67f4; 57f83e5dd6a33c4696699954784f8fee789b1d0c < 07ffe414a708ae60551401cec5d727ed156b8caf; 57f83e5dd6a33c4696699954784f8fee789b1d0c < 3d205fe80f2181f0109150ad1fa06ee5bc046935; 57f83e5dd6a33c4696699954784f8fee789b1d0c < d72650a4f334581b23a1892b888a4cb1be142f76; 57f83e5dd6a33c4696699954784f8fee789b1d0c < 778b9dda4b24005a27bcd9c35c110bf8d7f259ca; 57f83e5dd6a33c4696699954784f8fee789b1d0c < 10fc708b4de7f86002d2d735a2dbf3b5b7f65692; 5.19 · Fixed: < 5.19; 6.1.177 ≤ 6.1.*; 6.6.144 ≤ 6.6.*; 6.12.95 ≤ 6.12.*; 6.18.38 ≤ 6.18.*; 7.0.14 ≤ 7.0.*; 7.1.2 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
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-45506↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update 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-53384 · cve.blacktree.nl