Full vulnerability report · 2026

CVE-2026-43269High confidence

drm/atmel-hlcdc: fix memory leak from the atomic_destroy_state callback

Linux · Linux

5.5MediumCVSS 3.1

Recommended action

Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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

Operational reassessment

Published severity in operational context

Open reassessment dashboard →

Published severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

No CISA KEV confirmation is currently recorded.
Exploitation requires an existing local or physical foothold with privileges.
EPSS is 0.16% 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

Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.

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.

Canonical Ubuntu Security: 20 affected package states with no published fix

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 release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.85-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.1.170-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.6-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.6-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, 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 feed`	Canonical 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-43269 · CSAF 2.0 · revision 10 · interimSUSE Product Security TeamCVE-2026-43269

130 known affected

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

kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1

Summary: In the Linux kernel, the following vulnerability has been resolved: drm/atmel-hlcdc: fix memory leak from the atomic_destroy_state callback After several commits, the slab memory increases. Some drm_crtc_commit objects are not freed. The atomic_destroy_state callback only put the framebuffer. Use the __drm_atomic_helper_plane_destroy_state() function to put all the objects that are no longer needed. It has been seen after hours of usage of a graphics application or using kmemleak: unreferenced object 0xc63a6580 (size 64): comm "egt_basic", pid 171, jiffies 4294940784 hex dump (first 32 bytes): 40 50 34 c5 01 00 00 00 ff ff ff ff 8c 65 3a c6 @P4..........e:. 8c 65 3a c6 ff ff ff ff 98 65 3a c6 98 65 3a c6 .e:......e:..e:. backtrace (crc c25aa925): kmemleak_alloc+0x34/0x3c __kmalloc_cache_noprof+0x150/0x1a4 drm_atomic_helper_setup_commit+0x1e8/0x7bc drm_atomic_helper_commit+0x3c/0x15c drm_atomic_commit+0xc0/0xf4 drm_atomic_helper_set_config+0x84/0xb8 drm_mode_setcrtc+0x32c/0x810 drm_ioctl+0x20c/0x488 sys_ioctl+0x14c/0xc20 ret_fast_syscall+0x0/0x54
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

In the Linux kernel, the following vulnerability has been resolved: drm/atmel-hlcdc: fix memory leak from the atomic_destroy_state callback After several commits, the slab memory increases. Some drm_crtc_commit objects are not freed. The atomic_destroy_state callback only put the framebuffer. Use the __drm_atomic_helper_plane_destroy_state() function to put all the objects that are no longer needed. It has been seen after hours of usage of a graphics application or using kmemleak: unreferenced object 0xc63a6580 (size 64): comm "egt_basic", pid 171, jiffies 4294940784 hex dump (first 32 bytes): 40 50 34 c5 01 00 00 00 ff ff ff ff 8c 65 3a c6 @P4..........e:. 8c 65 3a c6 ff ff ff ff 98 65 3a c6 98 65 3a c6 .e:......e:..e:. backtrace (crc c25aa925): kmemleak_alloc+0x34/0x3c __kmalloc_cache_noprof+0x150/0x1a4 drm_atomic_helper_setup_commit+0x1e8/0x7bc drm_atomic_helper_commit+0x3c/0x15c drm_atomic_commit+0xc0/0xf4 drm_atomic_helper_set_config+0x84/0xb8 drm_mode_setcrtc+0x32c/0x810 drm_ioctl+0x20c/0x488 sys_ioctl+0x14c/0xc20 ret_fast_syscall+0x0/0x54

What

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

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 → Missing Release of Memory after Effective Lifetime → 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-401 ↗
CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-401

Official authority intelligence

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

ENISA EUVD · EUVD-2026-27668Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.

Official advisory ↗

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

d?id=CVE-2026-43246 Référence CVE CVE-2026-43251 https://www.cve.org/CVERecord?id=CVE-2026-43251 Référence CVE CVE-2026-43255 https://www.cve.org/CVERecord?id=CVE-2026-43255 Référence CVE CVE-2026-43257 https://www.cve.org/CVERecord?id=CVE-2026-43257 Référence CVE CVE-2026-43261 https://www.cve.org/CVERecord?id=CVE-2026-43261 Référence CVE CVE-2026-43262 https://www.cve.org/CVERecord?id=CVE-2026-43262 Référence CVE CVE-2026-43264 https://www.cve.org/CVERecord?id=CVE-2026-43264 Référence CVE CVE-2026-43266 https://www.cve.org/CVERecord?id=CVE-2026-43266 Référence CVE CVE-2026-43268 https://www.cve.org/CVERecord?id=CVE-2026-43268 Référence CVE CVE-2026-43269 https://www.cve.org/CVERecord?id=CVE-2026-43269 Référence CVE CVE-2026-43270 https://www.cve.org/CVERecord?id=CVE-2026-43270 Référence CVE CVE-2026-43273 https://www.cve.org/CVERecord?id=CVE-2026-43273 Référence CVE CVE-2026-43275 https://www.cve.org/CVERecord?id=CVE-2026-43275 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43281 https://www.cve.org/CVERecord?id=CVE-2026-43281 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

d?id=CVE-2026-43251 Référence CVE CVE-2026-43253 https://www.cve.org/CVERecord?id=CVE-2026-43253 Référence CVE CVE-2026-43255 https://www.cve.org/CVERecord?id=CVE-2026-43255 Référence CVE CVE-2026-43256 https://www.cve.org/CVERecord?id=CVE-2026-43256 Référence CVE CVE-2026-43257 https://www.cve.org/CVERecord?id=CVE-2026-43257 Référence CVE CVE-2026-43261 https://www.cve.org/CVERecord?id=CVE-2026-43261 Référence CVE CVE-2026-43262 https://www.cve.org/CVERecord?id=CVE-2026-43262 Référence CVE CVE-2026-43264 https://www.cve.org/CVERecord?id=CVE-2026-43264 Référence CVE CVE-2026-43266 https://www.cve.org/CVERecord?id=CVE-2026-43266 Référence CVE CVE-2026-43269 https://www.cve.org/CVERecord?id=CVE-2026-43269 Référence CVE CVE-2026-43270 https://www.cve.org/CVERecord?id=CVE-2026-43270 Référence CVE CVE-2026-43273 https://www.cve.org/CVERecord?id=CVE-2026-43273 Référence CVE CVE-2026-43275 https://www.cve.org/CVERecord?id=CVE-2026-43275 Référence CVE CVE-2026-43276 https://www.cve.org/CVERecord?id=CVE-2026-43276 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43278 https://www.cve.org/CVERecord?id=CVE-2026-43278 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43281 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

d?id=CVE-2026-43256 Référence CVE CVE-2026-43257 https://www.cve.org/CVERecord?id=CVE-2026-43257 Référence CVE CVE-2026-43258 https://www.cve.org/CVERecord?id=CVE-2026-43258 Référence CVE CVE-2026-43261 https://www.cve.org/CVERecord?id=CVE-2026-43261 Référence CVE CVE-2026-43262 https://www.cve.org/CVERecord?id=CVE-2026-43262 Référence CVE CVE-2026-43264 https://www.cve.org/CVERecord?id=CVE-2026-43264 Référence CVE CVE-2026-43265 https://www.cve.org/CVERecord?id=CVE-2026-43265 Référence CVE CVE-2026-43266 https://www.cve.org/CVERecord?id=CVE-2026-43266 Référence CVE CVE-2026-43268 https://www.cve.org/CVERecord?id=CVE-2026-43268 Référence CVE CVE-2026-43269 https://www.cve.org/CVERecord?id=CVE-2026-43269 Référence CVE CVE-2026-43270 https://www.cve.org/CVERecord?id=CVE-2026-43270 Référence CVE CVE-2026-43271 https://www.cve.org/CVERecord?id=CVE-2026-43271 Référence CVE CVE-2026-43273 https://www.cve.org/CVERecord?id=CVE-2026-43273 Référence CVE CVE-2026-43275 https://www.cve.org/CVERecord?id=CVE-2026-43275 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43278 https://www.cve.org/CVERecord?id=CVE-2026-43278 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43281 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-43246 Référence CVE CVE-2026-43248 https://www.cve.org/CVERecord?id=CVE-2026-43248 Référence CVE CVE-2026-43251 https://www.cve.org/CVERecord?id=CVE-2026-43251 Référence CVE CVE-2026-43253 https://www.cve.org/CVERecord?id=CVE-2026-43253 Référence CVE CVE-2026-43255 https://www.cve.org/CVERecord?id=CVE-2026-43255 Référence CVE CVE-2026-43256 https://www.cve.org/CVERecord?id=CVE-2026-43256 Référence CVE CVE-2026-43257 https://www.cve.org/CVERecord?id=CVE-2026-43257 Référence CVE CVE-2026-43260 https://www.cve.org/CVERecord?id=CVE-2026-43260 Référence CVE CVE-2026-43264 https://www.cve.org/CVERecord?id=CVE-2026-43264 Référence CVE CVE-2026-43269 https://www.cve.org/CVERecord?id=CVE-2026-43269 Référence CVE CVE-2026-43270 https://www.cve.org/CVERecord?id=CVE-2026-43270 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43278 https://www.cve.org/CVERecord?id=CVE-2026-43278 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=CVE-2026-43287 Référence CVE CVE-2026-43291 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-43252 Référence CVE CVE-2026-43255 https://www.cve.org/CVERecord?id=CVE-2026-43255 Référence CVE CVE-2026-43257 https://www.cve.org/CVERecord?id=CVE-2026-43257 Référence CVE CVE-2026-43261 https://www.cve.org/CVERecord?id=CVE-2026-43261 Référence CVE CVE-2026-43262 https://www.cve.org/CVERecord?id=CVE-2026-43262 Référence CVE CVE-2026-43264 https://www.cve.org/CVERecord?id=CVE-2026-43264 Référence CVE CVE-2026-43265 https://www.cve.org/CVERecord?id=CVE-2026-43265 Référence CVE CVE-2026-43266 https://www.cve.org/CVERecord?id=CVE-2026-43266 Référence CVE CVE-2026-43268 https://www.cve.org/CVERecord?id=CVE-2026-43268 Référence CVE CVE-2026-43269 https://www.cve.org/CVERecord?id=CVE-2026-43269 Référence CVE CVE-2026-43270 https://www.cve.org/CVERecord?id=CVE-2026-43270 Référence CVE CVE-2026-43273 https://www.cve.org/CVERecord?id=CVE-2026-43273 Référence CVE CVE-2026-43275 https://www.cve.org/CVERecord?id=CVE-2026-43275 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43281 https://www.cve.org/CVERecord?id=CVE-2026-43281 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43284 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-43255 Référence CVE CVE-2026-43256 https://www.cve.org/CVERecord?id=CVE-2026-43256 Référence CVE CVE-2026-43257 https://www.cve.org/CVERecord?id=CVE-2026-43257 Référence CVE CVE-2026-43258 https://www.cve.org/CVERecord?id=CVE-2026-43258 Référence CVE CVE-2026-43261 https://www.cve.org/CVERecord?id=CVE-2026-43261 Référence CVE CVE-2026-43262 https://www.cve.org/CVERecord?id=CVE-2026-43262 Référence CVE CVE-2026-43264 https://www.cve.org/CVERecord?id=CVE-2026-43264 Référence CVE CVE-2026-43266 https://www.cve.org/CVERecord?id=CVE-2026-43266 Référence CVE CVE-2026-43268 https://www.cve.org/CVERecord?id=CVE-2026-43268 Référence CVE CVE-2026-43269 https://www.cve.org/CVERecord?id=CVE-2026-43269 Référence CVE CVE-2026-43270 https://www.cve.org/CVERecord?id=CVE-2026-43270 Référence CVE CVE-2026-43271 https://www.cve.org/CVERecord?id=CVE-2026-43271 Référence CVE CVE-2026-43273 https://www.cve.org/CVERecord?id=CVE-2026-43273 Référence CVE CVE-2026-43275 https://www.cve.org/CVERecord?id=CVE-2026-43275 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43278 https://www.cve.org/CVERecord?id=CVE-2026-43278 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

d?id=CVE-2026-43242 Référence CVE CVE-2026-43246 https://www.cve.org/CVERecord?id=CVE-2026-43246 Référence CVE CVE-2026-43251 https://www.cve.org/CVERecord?id=CVE-2026-43251 Référence CVE CVE-2026-43255 https://www.cve.org/CVERecord?id=CVE-2026-43255 Référence CVE CVE-2026-43257 https://www.cve.org/CVERecord?id=CVE-2026-43257 Référence CVE CVE-2026-43261 https://www.cve.org/CVERecord?id=CVE-2026-43261 Référence CVE CVE-2026-43264 https://www.cve.org/CVERecord?id=CVE-2026-43264 Référence CVE CVE-2026-43266 https://www.cve.org/CVERecord?id=CVE-2026-43266 Référence CVE CVE-2026-43268 https://www.cve.org/CVERecord?id=CVE-2026-43268 Référence CVE CVE-2026-43269 https://www.cve.org/CVERecord?id=CVE-2026-43269 Référence CVE CVE-2026-43270 https://www.cve.org/CVERecord?id=CVE-2026-43270 Référence CVE CVE-2026-43273 https://www.cve.org/CVERecord?id=CVE-2026-43273 Référence CVE CVE-2026-43277 https://www.cve.org/CVERecord?id=CVE-2026-43277 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=CVE-2026-43287 Référence CVE CVE-2026-43289 https://www.cve.org/CVERecord?id=CVE-2026-43289 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2026-014932LinuxのLinux Kernelにおける有効期限後のメモリの解放の欠如に関する脆弱性

Linuxカーネルのdrm/atmel-hlcdcに存在する脆弱性は、atomic_destroy_stateコールバックによるメモリリークが修正されたものです。この問題は複数のコミットの後にslabメモリの増加が観察され、一部のdrm_crtc_commitオブジェクトが解放されていなかったことに起因していました。atomic_destroy_stateコールバックはフレームバッファのみを解放していましたが、不要なオブジェクトをすべて解放するために__drm_atomic_helper_plane_destroy_state()関数を使用するように変更されました。これにより、グラフィックスアプリケーションを長時間使用した後やkmemleak使用時に検出されていたメモリリークが解消されました。

Official advisory ↗

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: kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP3
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
kernel-default as component of SUSE Linux Enterprise Micro 5.0
kernel-default as component of SUSE Linux Enterprise Micro 5.1
kernel-default as component of SUSE Linux Enterprise Micro 5.2
and 100 more
Fixed: Linux: < 4.1, 5.10.252 ≤ 5.10.*, 5.15.202 ≤ 5.15.*, 6.1.165 ≤ 6.1.*, 6.6.128 ≤ 6.6.*, 6.12.75 ≤ 6.12.*, 6.18.16 ≤ 6.18.*, 6.19.6 ≤ 6.19.*, 7.0 ≤ *
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.

Evidence and provenance

Published 6 May 2026 · Last source change 11 May 2026, 22:21 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

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-27668

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 ↗

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

2026-05-06CVE published

2026-05-11Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-27668↗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.

drm/atmel-hlcdc: fix memory leak from the atomic_destroy_state callback

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

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

ENISA European Vulnerability Database

EUVD-2026-27668

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication