BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-68175High confidence

media: nxp: imx8-isi: Fix streaming cleanup on release

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.15% for the current model date.

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.8-1Debian Security Tracker ↗Source updated 5 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
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-2025-203721

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: nxp: imx8-isi: Fix streaming cleanup on release The current implementation unconditionally calls mxc_isi_video_cleanup_streaming() in mxc_isi_video_release(). This can lead to situations where any release call (like from a simple "v4l2-ctl -l") may release a currently streaming queue when called on such a device. This is reproducible on an i.MX8MP board by streaming from an ISI capture device using gstreamer: gst-launch-1.0 -v v4l2src device=/dev/videoX ! \ video/x-raw,format=GRAY8,width=1280,height=800,framerate=1/120 ! \ fakesink While this stream is running, querying the caps of the same device provokes the error state: v4l2-ctl -l -d /dev/videoX This results in the following trace: [ 155.452152] ------------[ cut here ]------------ [ 155.452163] WARNING: CPU: 0 PID: 1708 at drivers/media/platform/nxp/imx8-isi/imx8-isi-pipe.c:713 mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] [ 157.004248] Modules linked in: cfg80211 rpmsg_ctrl rpmsg_char rpmsg_tty virtio_rpmsg_bus rpmsg_ns rpmsg_core rfkill nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables mcp251x6 [ 157.053499] CPU: 0 UID: 0 PID: 1708 Comm: python3 Not tainted 6.15.4-00114-g1f61ca5cad76 #1 PREEMPT [ 157.064369] Hardware name: imx8mp_board_01 (DT) [ 157.068205] pstate: 400000c5 (nZcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 157.075169] pc : mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] [ 157.081195] lr : mxc_isi_pipe_irq_handler+0x38/0x1b0 [imx8_isi] [ 157.087126] sp : ffff800080003ee0 [ 157.090438] x29: ffff800080003ee0 x28: ffff0000c3688000 x27: 0000000000000000 [ 157.097580] x26: 0000000000000000 x25: ffff0000c1e7ac00 x24: ffff800081b5ad50 [ 157.104723] x23: 00000000000000d1 x22: 0000000000000000 x21: ffff0000c25e4000 [ 157.111866] x20: 0000000060000200 x19: ffff80007a0608d0 x18: 0000000000000000 [ 157.119008] x17: ffff80006a4e3000 x16: ffff800080000000 x15: 0000000000000000 [ 157.126146] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 [ 157.133287] x11: 0000000000000040 x10: ffff0000c01445f0 x9 : ffff80007a053a38 [ 157.140425] x8 : ffff0000c04004b8 x7 : 0000000000000000 x6 : 0000000000000000 [ 157.147567] x5 : ffff0000c0400490 x4 : ffff80006a4e3000 x3 : ffff0000c25e4000 [ 157.154706] x2 : 0000000000000000 x1 : ffff8000825c0014 x0 : 0000000060000200 [ 157.161850] Call trace: [ 157.164296] mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] (P) [ 157.170319] __handle_irq_event_percpu+0x58/0x218 [ 157.175029] handle_irq_event+0x54/0xb8 [ 157.178867] handle_fasteoi_irq+0xac/0x248 [ 157.182968] handle_irq_desc+0x48/0x68 [ 157.186723] generic_handle_domain_irq+0x24/0x38 [ 157.191346] gic_handle_irq+0x54/0x120 [ 157.195098] call_on_irq_stack+0x24/0x30 [ 157.199027] do_interrupt_handler+0x88/0x98 [ 157.203212] el0_interrupt+0x44/0xc0 [ 157.206792] __el0_irq_handler_common+0x18/0x28 [ 157.211328] el0t_64_irq_handler+0x10/0x20 [ 157.215429] el0t_64_irq+0x198/0x1a0 [ 157.219009] ---[ end trace 0000000000000000 ]--- Address this issue by moving the streaming preparation and cleanup to the vb2 .prepare_streaming() and .unprepare_streaming() operations. This also simplifies the driver by allowing direct usage of the vb2_ioctl_streamon() and vb2_ioctl_streamoff() helpers, and removal of the manual cleanup from mxc_isi_video_release().

What

In the Linux kernel, the following vulnerability has been resolved: media: nxp: imx8-isi: Fix streaming cleanup on release The current implementation unconditionally calls mxc_isi_video_cleanup_streaming() in mxc_isi_video_release(). This can lead to situations where any release call (like from a simple "v4l2-ctl -l") may release a currently streaming queue when called on such a device. This is reproducible on an i.MX8MP board by streaming from an ISI capture device using gstreamer: gst-launch-1.0 -v v4l2src device=/dev/videoX ! \ video/x-raw,format=GRAY8,width=1280,height=800,framerate=1/120 ! \ fakesink While this stream is running, querying the caps of the same device provokes the error state: v4l2-ctl -l -d /dev/videoX This results in the following trace: [ 155.452152] ------------[ cut here ]------------ [ 155.452163] WARNING: CPU: 0 PID: 1708 at drivers/media/platform/nxp/imx8-isi/imx8-isi-pipe.c:713 mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] [ 157.004248] Modules linked in: cfg80211 rpmsg_ctrl rpmsg_char rpmsg_tty virtio_rpmsg_bus rpmsg_ns rpmsg_core rfkill nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables mcp251x6 [ 157.053499] CPU: 0 UID: 0 PID: 1708 Comm: python3 Not tainted 6.15.4-00114-g1f61ca5cad76 #1 PREEMPT [ 157.064369] Hardware name: imx8mp_board_01 (DT) [ 157.068205] pstate: 400000c5 (nZcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 157.075169] pc : mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] [ 157.081195] lr : mxc_isi_pipe_irq_handler+0x38/0x1b0 [imx8_isi] [ 157.087126] sp : ffff800080003ee0 [ 157.090438] x29: ffff800080003ee0 x28: ffff0000c3688000 x27: 0000000000000000 [ 157.097580] x26: 0000000000000000 x25: ffff0000c1e7ac00 x24: ffff800081b5ad50 [ 157.104723] x23: 00000000000000d1 x22: 0000000000000000 x21: ffff0000c25e4000 [ 157.111866] x20: 0000000060000200 x19: ffff80007a0608d0 x18: 0000000000000000 [ 157.119008] x17: ffff80006a4e3000 x16: ffff800080000000 x15: 0000000000000000 [ 157.126146] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 [ 157.133287] x11: 0000000000000040 x10: ffff0000c01445f0 x9 : ffff80007a053a38 [ 157.140425] x8 : ffff0000c04004b8 x7 : 0000000000000000 x6 : 0000000000000000 [ 157.147567] x5 : ffff0000c0400490 x4 : ffff80006a4e3000 x3 : ffff0000c25e4000 [ 157.154706] x2 : 0000000000000000 x1 : ffff8000825c0014 x0 : 0000000060000200 [ 157.161850] Call trace: [ 157.164296] mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] (P) [ 157.170319] __handle_irq_event_percpu+0x58/0x218 [ 157.175029] handle_irq_event+0x54/0xb8 [ 157.178867] handle_fasteoi_irq+0xac/0x248 [ 157.182968] handle_irq_desc+0x48/0x68 [ 157.186723] generic_handle_domain_irq+0x24/0x38 [ 157.191346] gic_handle_irq+0x54/0x120 [ 157.195098] call_on_irq_stack+0x24/0x30 [ 157.199027] do_interrupt_handler+0x88/0x98 [ 157.203212] el0_interrupt+0x44/0xc0 [ 157.206792] __el0_irq_handler_common+0x18/0x28 [ 157.211328] el0t_64_irq_handler+0x10/0x20 [ 157.215429] el0t_64_irq+0x198/0x1a0 [ 157.219009] ---[ end trace 0000000000000000 ]--- Address this issue by moving the streaming preparation and cleanup to the vb2 .prepare_streaming() and .unprepare_streaming() operations. This also simplifies the driver by allowing direct usage of the vb2_ioctl_streamon() and vb2_ioctl_streamoff() helpers, and removal of the manual cleanup from mxc_isi_video_release().

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: nxp: imx8-isi: Fix streaming cleanup on release The current implementation unconditionally calls mxc_isi_video_cleanup_streaming() in mxc_isi_video_release(). This can lead to situations where any release call (like from a simple "v4l2-ctl -l") may release a currently streaming queue when called on such a device. This is reproducible on an i.MX8MP board by streaming from an ISI capture device using gstreamer: gst-launch-1.0 -v v4l2src device=/dev/videoX ! \ video/x-raw,format=GRAY8,width=1280,height=800,framerate=1/120 ! \ fakesink While this stream is running, querying the caps of the same device provokes the error state: v4l2-ctl -l -d /dev/videoX This results in the following trace: [ 155.452152] ------------[ cut here ]------------ [ 155.452163] WARNING: CPU: 0 PID: 1708 at drivers/media/platform/nxp/imx8-isi/imx8-isi-pipe.c:713 mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] [ 157.004248] Modules linked in: cfg80211 rpmsg_ctrl rpmsg_char rpmsg_tty virtio_rpmsg_bus rpmsg_ns rpmsg_core rfkill nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables mcp251x6 [ 157.053499] CPU: 0 UID: 0 PID: 1708 Comm: python3 Not tainted 6.15.4-00114-g1f61ca5cad76 #1 PREEMPT [ 157.064369] Hardware name: imx8mp_board_01 (DT) [ 157.068205] pstate: 400000c5 (nZcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 157.075169] pc : mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] [ 157.081195] lr : mxc_isi_pipe_irq_handler+0x38/0x1b0 [imx8_isi] [ 157.087126] sp : ffff800080003ee0 [ 157.090438] x29: ffff800080003ee0 x28: ffff0000c3688000 x27: 0000000000000000 [ 157.097580] x26: 0000000000000000 x25: ffff0000c1e7ac00 x24: ffff800081b5ad50 [ 157.104723] x23: 00000000000000d1 x22: 0000000000000000 x21: ffff0000c25e4000 [ 157.111866] x20: 0000000060000200 x19: ffff80007a0608d0 x18: 0000000000000000 [ 157.119008] x17: ffff80006a4e3000 x16: ffff800080000000 x15: 0000000000000000 [ 157.126146] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 [ 157.133287] x11: 0000000000000040 x10: ffff0000c01445f0 x9 : ffff80007a053a38 [ 157.140425] x8 : ffff0000c04004b8 x7 : 0000000000000000 x6 : 0000000000000000 [ 157.147567] x5 : ffff0000c0400490 x4 : ffff80006a4e3000 x3 : ffff0000c25e4000 [ 157.154706] x2 : 0000000000000000 x1 : ffff8000825c0014 x0 : 0000000060000200 [ 157.161850] Call trace: [ 157.164296] mxc_isi_pipe_irq_handler+0x19c/0x1b0 [imx8_isi] (P) [ 157.170319] __handle_irq_event_percpu+0x58/0x218 [ 157.175029] handle_irq_event+0x54/0xb8 [ 157.178867] handle_fasteoi_irq+0xac/0x248 [ 157.182968] handle_irq_desc+0x48/0x68 [ 157.186723] generic_handle_domain_irq+0x24/0x38 [ 157.191346] gic_handle_irq+0x54/0x120 [ 157.195098] call_on_irq_stack+0x24/0x30 [ 157.199027] do_interrupt_handler+0x88/0x98 [ 157.203212] el0_interrupt+0x44/0xc0 [ 157.206792] __el0_irq_handler_common+0x18/0x28 [ 157.211328] el0t_64_irq_handler+0x10/0x20 [ 157.215429] el0t_64_irq+0x198/0x1a0 [ 157.219009] ---[ end trace 0000000000000000 ]--- Address this issue by moving the streaming preparation and cleanup to the vb2 .prepare_streaming() and .unprepare_streaming() operations. This also simplifies the driver by allowing direct usage of the vb2_ioctl_streamon() and vb2_ioctl_streamoff() helpers, and removal of the manual cleanup from mxc_isi_video_release().

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
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.
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-2868Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

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

d?id=CVE-2025-22116 Référence CVE CVE-2025-27558 https://www.cve.org/CVERecord?id=CVE-2025-27558 Référence CVE CVE-2025-38426 https://www.cve.org/CVERecord?id=CVE-2025-38426 Référence CVE CVE-2025-39764 https://www.cve.org/CVERecord?id=CVE-2025-39764 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40150 https://www.cve.org/CVERecord?id=CVE-2025-40150 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-62626 https://www.cve.org/CVERecord?id=CVE-2025-62626 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68334 https://www.cve.org/CVERecord?id=CVE-2025-68334 Référence CVE CVE-2025-68736 https://www.cve.org/CVERecord?id=CVE-2025-68736 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=CVE-2025-71161 Référence CVE CVE-2025-71203 https://www.cve.org/CVERecord?id=CVE-2025-71203 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71269 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-2025-40016 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40150 https://www.cve.org/CVERecord?id=CVE-2025-40150 Référence CVE CVE-2025-40323 https://www.cve.org/CVERecord?id=CVE-2025-40323 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-62626 https://www.cve.org/CVERecord?id=CVE-2025-62626 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68334 https://www.cve.org/CVERecord?id=CVE-2025-68334 Référence CVE CVE-2025-68358 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-2025-40005 Référence CVE CVE-2025-40016 https://www.cve.org/CVERecord?id=CVE-2025-40016 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40150 https://www.cve.org/CVERecord?id=CVE-2025-40150 Référence CVE CVE-2025-40323 https://www.cve.org/CVERecord?id=CVE-2025-40323 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-62626 https://www.cve.org/CVERecord?id=CVE-2025-62626 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68334 https://www.cve.org/CVERecord?id=CVE-2025-68334 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68736 https://www.cve.org/CVERecord?id=CVE-2025-68736 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40005 Référence CVE CVE-2025-40016 https://www.cve.org/CVERecord?id=CVE-2025-40016 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40147 https://www.cve.org/CVERecord?id=CVE-2025-40147 Référence CVE CVE-2025-40150 https://www.cve.org/CVERecord?id=CVE-2025-40150 Référence CVE CVE-2025-40219 https://www.cve.org/CVERecord?id=CVE-2025-40219 Référence CVE CVE-2025-40242 https://www.cve.org/CVERecord?id=CVE-2025-40242 Référence CVE CVE-2025-40261 https://www.cve.org/CVERecord?id=CVE-2025-40261 Référence CVE CVE-2025-40358 https://www.cve.org/CVERecord?id=CVE-2025-40358 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68334 https://www.cve.org/CVERecord?id=CVE-2025-68334 Référence CVE CVE-2025-68736 https://www.cve.org/CVERecord?id=CVE-2025-68736 Référence CVE CVE-2025-71067 https://www.cve.org/CVERecord?id=CVE-2025-71067 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-67735 Référence CVE CVE-2025-68119 https://www.cve.org/CVERecord?id=CVE-2025-68119 Référence CVE CVE-2025-68121 https://www.cve.org/CVERecord?id=CVE-2025-68121 Référence CVE CVE-2025-68160 https://www.cve.org/CVERecord?id=CVE-2025-68160 Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2025-68168 https://www.cve.org/CVERecord?id=CVE-2025-68168 Référence CVE CVE-2025-68171 https://www.cve.org/CVERecord?id=CVE-2025-68171 Référence CVE CVE-2025-68173 https://www.cve.org/CVERecord?id=CVE-2025-68173 Référence CVE CVE-2025-68174 https://www.cve.org/CVERecord?id=CVE-2025-68174 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68176 https://www.cve.org/CVERecord?id=CVE-2025-68176 Référence CVE CVE-2025-68177 https://www.cve.org/CVERecord?id=CVE-2025-68177 Référence CVE CVE-2025-68178 https://www.cve.org/CVERecord?id=CVE-2025-68178 Référence CVE CVE-2025-68183 https://www.cve.org/CVERecord?id=CVE-2025-68183 Référence CVE CVE-2025-68184 https://www.cve.org/CVERecord?id=CVE-2025-68184 Référence CVE CVE-2025-68185 https://www.cve.org/CVERecord?id=CVE-2025-68185 Référence CVE CVE-2025-68188 https://www.cve.org/CVERecord?id=CVE-2025-68188 Référence CVE CVE-2025-68190 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-66865 Référence CVE CVE-2025-66866 https://www.cve.org/CVERecord?id=CVE-2025-66866 Référence CVE CVE-2025-68119 https://www.cve.org/CVERecord?id=CVE-2025-68119 Référence CVE CVE-2025-68121 https://www.cve.org/CVERecord?id=CVE-2025-68121 Référence CVE CVE-2025-68160 https://www.cve.org/CVERecord?id=CVE-2025-68160 Référence CVE CVE-2025-68168 https://www.cve.org/CVERecord?id=CVE-2025-68168 Référence CVE CVE-2025-68171 https://www.cve.org/CVERecord?id=CVE-2025-68171 Référence CVE CVE-2025-68173 https://www.cve.org/CVERecord?id=CVE-2025-68173 Référence CVE CVE-2025-68174 https://www.cve.org/CVERecord?id=CVE-2025-68174 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68176 https://www.cve.org/CVERecord?id=CVE-2025-68176 Référence CVE CVE-2025-68177 https://www.cve.org/CVERecord?id=CVE-2025-68177 Référence CVE CVE-2025-68178 https://www.cve.org/CVERecord?id=CVE-2025-68178 Référence CVE CVE-2025-68183 https://www.cve.org/CVERecord?id=CVE-2025-68183 Référence CVE CVE-2025-68184 https://www.cve.org/CVERecord?id=CVE-2025-68184 Référence CVE CVE-2025-68185 https://www.cve.org/CVERecord?id=CVE-2025-68185 Référence CVE CVE-2025-68188 https://www.cve.org/CVERecord?id=CVE-2025-68188 Référence CVE CVE-2025-68190 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40363 Référence CVE CVE-2025-68167 https://www.cve.org/CVERecord?id=CVE-2025-68167 Référence CVE CVE-2025-68168 https://www.cve.org/CVERecord?id=CVE-2025-68168 Référence CVE CVE-2025-68169 https://www.cve.org/CVERecord?id=CVE-2025-68169 Référence CVE CVE-2025-68170 https://www.cve.org/CVERecord?id=CVE-2025-68170 Référence CVE CVE-2025-68171 https://www.cve.org/CVERecord?id=CVE-2025-68171 Référence CVE CVE-2025-68172 https://www.cve.org/CVERecord?id=CVE-2025-68172 Référence CVE CVE-2025-68173 https://www.cve.org/CVERecord?id=CVE-2025-68173 Référence CVE CVE-2025-68174 https://www.cve.org/CVERecord?id=CVE-2025-68174 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68176 https://www.cve.org/CVERecord?id=CVE-2025-68176 Référence CVE CVE-2025-68177 https://www.cve.org/CVERecord?id=CVE-2025-68177 Référence CVE CVE-2025-68178 https://www.cve.org/CVERecord?id=CVE-2025-68178 Référence CVE CVE-2025-68179 https://www.cve.org/CVERecord?id=CVE-2025-68179 Référence CVE CVE-2025-68180 https://www.cve.org/CVERecord?id=CVE-2025-68180 Référence CVE CVE-2025-68181 https://www.cve.org/CVERecord?id=CVE-2025-68181 Référence CVE CVE-2025-68182 https://www.cve.org/CVERecord?id=CVE-2025-68182 Référence CVE CVE-2025-68183 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40363 Référence CVE CVE-2025-68167 https://www.cve.org/CVERecord?id=CVE-2025-68167 Référence CVE CVE-2025-68168 https://www.cve.org/CVERecord?id=CVE-2025-68168 Référence CVE CVE-2025-68169 https://www.cve.org/CVERecord?id=CVE-2025-68169 Référence CVE CVE-2025-68170 https://www.cve.org/CVERecord?id=CVE-2025-68170 Référence CVE CVE-2025-68171 https://www.cve.org/CVERecord?id=CVE-2025-68171 Référence CVE CVE-2025-68172 https://www.cve.org/CVERecord?id=CVE-2025-68172 Référence CVE CVE-2025-68173 https://www.cve.org/CVERecord?id=CVE-2025-68173 Référence CVE CVE-2025-68174 https://www.cve.org/CVERecord?id=CVE-2025-68174 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68176 https://www.cve.org/CVERecord?id=CVE-2025-68176 Référence CVE CVE-2025-68177 https://www.cve.org/CVERecord?id=CVE-2025-68177 Référence CVE CVE-2025-68178 https://www.cve.org/CVERecord?id=CVE-2025-68178 Référence CVE CVE-2025-68179 https://www.cve.org/CVERecord?id=CVE-2025-68179 Référence CVE CVE-2025-68180 https://www.cve.org/CVERecord?id=CVE-2025-68180 Référence CVE CVE-2025-68181 https://www.cve.org/CVERecord?id=CVE-2025-68181 Référence CVE CVE-2025-68182 https://www.cve.org/CVERecord?id=CVE-2025-68182 Référence CVE CVE-2025-68183 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40363 Référence CVE CVE-2025-68167 https://www.cve.org/CVERecord?id=CVE-2025-68167 Référence CVE CVE-2025-68168 https://www.cve.org/CVERecord?id=CVE-2025-68168 Référence CVE CVE-2025-68169 https://www.cve.org/CVERecord?id=CVE-2025-68169 Référence CVE CVE-2025-68170 https://www.cve.org/CVERecord?id=CVE-2025-68170 Référence CVE CVE-2025-68171 https://www.cve.org/CVERecord?id=CVE-2025-68171 Référence CVE CVE-2025-68172 https://www.cve.org/CVERecord?id=CVE-2025-68172 Référence CVE CVE-2025-68173 https://www.cve.org/CVERecord?id=CVE-2025-68173 Référence CVE CVE-2025-68174 https://www.cve.org/CVERecord?id=CVE-2025-68174 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68176 https://www.cve.org/CVERecord?id=CVE-2025-68176 Référence CVE CVE-2025-68177 https://www.cve.org/CVERecord?id=CVE-2025-68177 Référence CVE CVE-2025-68178 https://www.cve.org/CVERecord?id=CVE-2025-68178 Référence CVE CVE-2025-68179 https://www.cve.org/CVERecord?id=CVE-2025-68179 Référence CVE CVE-2025-68180 https://www.cve.org/CVERecord?id=CVE-2025-68180 Référence CVE CVE-2025-68181 https://www.cve.org/CVERecord?id=CVE-2025-68181 Référence CVE CVE-2025-68182 https://www.cve.org/CVERecord?id=CVE-2025-68182 Référence CVE CVE-2025-68183 https://www.cve.org/CVERecord?id=

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
Linux: cf21f328fcafacf4f96e7a30ef9dceede1076378 < a2008925ed7361d69f92f63f0a779c300432610a, cf21f328fcafacf4f96e7a30ef9dceede1076378 < 029914306b93b37c6e7060793d2b6f76b935cfa6, cf21f328fcafacf4f96e7a30ef9dceede1076378 < 47773031a148ad7973b809cc7723cba77eda2b42, 6.4
Fixed
Linux: < 6.4, 6.12.80 ≤ 6.12.*, 6.17.8 ≤ 6.17.*, 6.18 ≤ *
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 16 Dec 2025 · Last source change 5 Aug 2026, 12:10 UTC · CWE not yet assigned

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-2025-203721
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD not scheduled

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

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