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

media: mtk-jpeg: fix use-after-free in release path due to uncancelled work

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 5 Aug 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.86-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-1Debian Security Tracker ↗Source updated 7 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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-46011 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-46011
47 known affected

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

  • cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • gfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-macros as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-source as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • ocfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
  • dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
Summary
In the Linux kernel, the following vulnerability has been resolved: media: mtk-jpeg: fix use-after-free in release path due to uncancelled work The mtk_jpeg_release() function frees the context structure (ctx) without first cancelling any pending or running work in ctx->jpeg_work. This creates a race window where the workqueue callback may still be accessing the context memory after it has been freed. Race condition: CPU 0 (release) CPU 1 (workqueue) ---------------- ------------------ close() mtk_jpeg_release() mtk_jpegenc_worker() ctx = work->data // accessing ctx kfree(ctx) // freed! access ctx // UAF! The work is queued via queue_work() during JPEG encode/decode operations (via mtk_jpeg_device_run). If the device is closed while work is pending or running, the work handler will access freed memory. Fix this by calling cancel_work_sync() BEFORE acquiring the mutex. This ordering is critical: if cancel_work_sync() is called after mutex_lock(), and the work handler also tries to acquire the same mutex, it would cause a deadlock. Note: The open error path does NOT need cancel_work_sync() because INIT_WORK() only initializes the work structure - it does not schedule it. Work is only scheduled later during ioctl operations.
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-32308

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: mtk-jpeg: fix use-after-free in release path due to uncancelled work The mtk_jpeg_release() function frees the context structure (ctx) without first cancelling any pending or running work in ctx->jpeg_work. This creates a race window where the workqueue callback may still be accessing the context memory after it has been freed. Race condition: CPU 0 (release) CPU 1 (workqueue) ---------------- ------------------ close() mtk_jpeg_release() mtk_jpegenc_worker() ctx = work->data // accessing ctx kfree(ctx) // freed! access ctx // UAF! The work is queued via queue_work() during JPEG encode/decode operations (via mtk_jpeg_device_run). If the device is closed while work is pending or running, the work handler will access freed memory. Fix this by calling cancel_work_sync() BEFORE acquiring the mutex. This ordering is critical: if cancel_work_sync() is called after mutex_lock(), and the work handler also tries to acquire the same mutex, it would cause a deadlock. Note: The open error path does NOT need cancel_work_sync() because INIT_WORK() only initializes the work structure - it does not schedule it. Work is only scheduled later during ioctl operations.

What

In the Linux kernel, the following vulnerability has been resolved: media: mtk-jpeg: fix use-after-free in release path due to uncancelled work The mtk_jpeg_release() function frees the context structure (ctx) without first cancelling any pending or running work in ctx->jpeg_work. This creates a race window where the workqueue callback may still be accessing the context memory after it has been freed. Race condition: CPU 0 (release) CPU 1 (workqueue) ---------------- ------------------ close() mtk_jpeg_release() mtk_jpegenc_worker() ctx = work->data // accessing ctx kfree(ctx) // freed! access ctx // UAF! The work is queued via queue_work() during JPEG encode/decode operations (via mtk_jpeg_device_run). If the device is closed while work is pending or running, the work handler will access freed memory. Fix this by calling cancel_work_sync() BEFORE acquiring the mutex. This ordering is critical: if cancel_work_sync() is called after mutex_lock(), and the work handler also tries to acquire the same mutex, it would cause a deadlock. Note: The open error path does NOT need cancel_work_sync() because INIT_WORK() only initializes the work structure - it does not schedule it. Work is only scheduled later during ioctl operations.

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: mtk-jpeg: fix use-after-free in release path due to uncancelled work The mtk_jpeg_release() function frees the context structure (ctx) without first cancelling any pending or running work in ctx->jpeg_work. This creates a race window where the workqueue callback may still be accessing the context memory after it has been freed. Race condition: CPU 0 (release) CPU 1 (workqueue) ---------------- ------------------ close() mtk_jpeg_release() mtk_jpegenc_worker() ctx = work->data // accessing ctx kfree(ctx) // freed! access ctx // UAF! The work is queued via queue_work() during JPEG encode/decode operations (via mtk_jpeg_device_run). If the device is closed while work is pending or running, the work handler will access freed memory. Fix this by calling cancel_work_sync() BEFORE acquiring the mutex. This ordering is critical: if cancel_work_sync() is called after mutex_lock(), and the work handler also tries to acquire the same mutex, it would cause a deadlock. Note: The open error path does NOT need cancel_work_sync() because INIT_WORK() only initializes the work structure - it does not schedule it. Work is only scheduled later during ioctl operations.

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-1700Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

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

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

d?id=CVE-2026-45997 Référence CVE CVE-2026-45999 https://www.cve.org/CVERecord?id=CVE-2026-45999 Référence CVE CVE-2026-46002 https://www.cve.org/CVERecord?id=CVE-2026-46002 Référence CVE CVE-2026-46003 https://www.cve.org/CVERecord?id=CVE-2026-46003 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46005 https://www.cve.org/CVERecord?id=CVE-2026-46005 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46007 https://www.cve.org/CVERecord?id=CVE-2026-46007 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46012 https://www.cve.org/CVERecord?id=CVE-2026-46012 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46021 https://www.cve.org/CVERecord?id=CVE-2026-46021 Référence CVE CVE-2026-46022 https://www.cve.org/CVERecord?id=CVE-2026-46022 Référence CVE CVE-2026-46023 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-45986 Référence CVE CVE-2026-45987 https://www.cve.org/CVERecord?id=CVE-2026-45987 Référence CVE CVE-2026-45994 https://www.cve.org/CVERecord?id=CVE-2026-45994 Référence CVE CVE-2026-45996 https://www.cve.org/CVERecord?id=CVE-2026-45996 Référence CVE CVE-2026-46001 https://www.cve.org/CVERecord?id=CVE-2026-46001 Référence CVE CVE-2026-46003 https://www.cve.org/CVERecord?id=CVE-2026-46003 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46026 https://www.cve.org/CVERecord?id=CVE-2026-46026 Référence CVE CVE-2026-46027 https://www.cve.org/CVERecord?id=CVE-2026-46027 Référence CVE CVE-2026-46033 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-46002 Référence CVE CVE-2026-46003 https://www.cve.org/CVERecord?id=CVE-2026-46003 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46005 https://www.cve.org/CVERecord?id=CVE-2026-46005 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46007 https://www.cve.org/CVERecord?id=CVE-2026-46007 Référence CVE CVE-2026-46008 https://www.cve.org/CVERecord?id=CVE-2026-46008 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46010 https://www.cve.org/CVERecord?id=CVE-2026-46010 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46012 https://www.cve.org/CVERecord?id=CVE-2026-46012 Référence CVE CVE-2026-46013 https://www.cve.org/CVERecord?id=CVE-2026-46013 Référence CVE CVE-2026-46014 https://www.cve.org/CVERecord?id=CVE-2026-46014 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46020 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-45986 Référence CVE CVE-2026-45987 https://www.cve.org/CVERecord?id=CVE-2026-45987 Référence CVE CVE-2026-45994 https://www.cve.org/CVERecord?id=CVE-2026-45994 Référence CVE CVE-2026-45996 https://www.cve.org/CVERecord?id=CVE-2026-45996 Référence CVE CVE-2026-45997 https://www.cve.org/CVERecord?id=CVE-2026-45997 Référence CVE CVE-2026-45999 https://www.cve.org/CVERecord?id=CVE-2026-45999 Référence CVE CVE-2026-46005 https://www.cve.org/CVERecord?id=CVE-2026-46005 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46024 https://www.cve.org/CVERecord?id=CVE-2026-46024 Référence CVE CVE-2026-46027 https://www.cve.org/CVERecord?id=CVE-2026-46027 Référence CVE CVE-2026-46033 https://www.cve.org/CVERecord?id=CVE-2026-46033 Référence CVE CVE-2026-46037 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-46002 Référence CVE CVE-2026-46003 https://www.cve.org/CVERecord?id=CVE-2026-46003 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46005 https://www.cve.org/CVERecord?id=CVE-2026-46005 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46007 https://www.cve.org/CVERecord?id=CVE-2026-46007 Référence CVE CVE-2026-46008 https://www.cve.org/CVERecord?id=CVE-2026-46008 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46010 https://www.cve.org/CVERecord?id=CVE-2026-46010 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46012 https://www.cve.org/CVERecord?id=CVE-2026-46012 Référence CVE CVE-2026-46013 https://www.cve.org/CVERecord?id=CVE-2026-46013 Référence CVE CVE-2026-46014 https://www.cve.org/CVERecord?id=CVE-2026-46014 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46020 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-46002 Référence CVE CVE-2026-46003 https://www.cve.org/CVERecord?id=CVE-2026-46003 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46005 https://www.cve.org/CVERecord?id=CVE-2026-46005 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46007 https://www.cve.org/CVERecord?id=CVE-2026-46007 Référence CVE CVE-2026-46008 https://www.cve.org/CVERecord?id=CVE-2026-46008 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46010 https://www.cve.org/CVERecord?id=CVE-2026-46010 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46012 https://www.cve.org/CVERecord?id=CVE-2026-46012 Référence CVE CVE-2026-46013 https://www.cve.org/CVERecord?id=CVE-2026-46013 Référence CVE CVE-2026-46014 https://www.cve.org/CVERecord?id=CVE-2026-46014 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46020 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-46002 Référence CVE CVE-2026-46003 https://www.cve.org/CVERecord?id=CVE-2026-46003 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46005 https://www.cve.org/CVERecord?id=CVE-2026-46005 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46007 https://www.cve.org/CVERecord?id=CVE-2026-46007 Référence CVE CVE-2026-46008 https://www.cve.org/CVERecord?id=CVE-2026-46008 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46010 https://www.cve.org/CVERecord?id=CVE-2026-46010 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46012 https://www.cve.org/CVERecord?id=CVE-2026-46012 Référence CVE CVE-2026-46013 https://www.cve.org/CVERecord?id=CVE-2026-46013 Référence CVE CVE-2026-46014 https://www.cve.org/CVERecord?id=CVE-2026-46014 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46020 https://www.cve.org/CVERecord?id=

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

mai 2026 Bulletin de sécurité Microsoft CVE-2026-45997 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45998 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45999 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46000 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46002 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46003 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46004 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46005 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46006 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46009 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46011 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46012 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46015 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46016 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46018 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46019 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46021 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46022 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46023 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46024 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46026 du 28 mai 2026 Bulletin de sécurité Mic

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

Linuxカーネルのmedia: mtk-jpegドライバにおいて、mtk_jpeg_release()関数が取り消されていない作業による解放パスのuse-after-freeの脆弱性を修正しました。この関数はctx-jpeg_work内の未完了の作業をキャンセルせずにctx構造体を解放していたため、作業キューのコールバックが解放後のメモリにアクセスし、競合状態が発生する可能性がありました。問題の原因は、作業ワーカーがctxを参照している間にkfree(ctx)が呼ばれることでuse-after-freeが生じる点です。この脆弱性は、mtk_jpeg_release()内でmutex_lock()を取得する前にcancel_work_sync()を呼び出して作業をキャンセルすることで修正されました。この修正により、解放前に保留中の作業が適切にキャンセルされ、解放後の不正アクセスを防止します。なお、cancel_work_sync()の呼び出し順序は重要で、mutex_lock()の前に呼ぶ必要があります。なぜなら、逆の場合にデッドロックが発生する可能性があるためです。

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: < 6.2, 6.6.140 ≤ 6.6.*, 6.12.86 ≤ 6.12.*, 6.18.27 ≤ 6.18.*, 7.0.4 ≤ 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 27 May 2026 · Last source change 5 Aug 2026, 12:29 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-32308
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.

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-32308↗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-46011 · cve.blacktree.nl