CVE-2024-40916: drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found

Ubuntu release	Source package	Vendor state	Fixed version	Evidence
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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.8`	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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 2026

01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found When reading EDID fails and driver reports no modes available, the DRM core adds an artificial 1024x786 mode to the connector. Unfortunately some variants of the Exynos HDMI (like the one in Exynos4 SoCs) are not able to drive such mode, so report a safe 640x480 mode instead of nothing in case of the EDID reading failure. This fixes the following issue observed on Trats2 board since commit 13d5b040363c ("drm/exynos: do not return negative values from .get_modes()"): [drm] Exynos DRM: using 11c00000.fimd device for DMA mapping operations exynos-drm exynos-drm: bound 11c00000.fimd (ops fimd_component_ops) exynos-drm exynos-drm: bound 12c10000.mixer (ops mixer_component_ops) exynos-dsi 11c80000.dsi: [drm:samsung_dsim_host_attach] Attached s6e8aa0 device (lanes:4 bpp:24 mode-flags:0x10b) exynos-drm exynos-drm: bound 11c80000.dsi (ops exynos_dsi_component_ops) exynos-drm exynos-drm: bound 12d00000.hdmi (ops hdmi_component_ops) [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 1 exynos-hdmi 12d00000.hdmi: [drm:hdmiphy_enable.part.0] *ERROR* PLL could not reach steady state panel-samsung-s6e8aa0 11c80000.dsi.0: ID: 0xa2, 0x20, 0x8c exynos-mixer 12c10000.mixer: timeout waiting for VSYNC ------------[ cut here ]------------ WARNING: CPU: 1 PID: 11 at drivers/gpu/drm/drm_atomic_helper.c:1682 drm_atomic_helper_wait_for_vblanks.part.0+0x2b0/0x2b8 [CRTC:70:crtc-1] vblank wait timed out Modules linked in: CPU: 1 PID: 11 Comm: kworker/u16:0 Not tainted 6.9.0-rc5-next-20240424 #14913 Hardware name: Samsung Exynos (Flattened Device Tree) Workqueue: events_unbound deferred_probe_work_func Call trace: unwind_backtrace from show_stack+0x10/0x14 show_stack from dump_stack_lvl+0x68/0x88 dump_stack_lvl from __warn+0x7c/0x1c4 __warn from warn_slowpath_fmt+0x11c/0x1a8 warn_slowpath_fmt from drm_atomic_helper_wait_for_vblanks.part.0+0x2b0/0x2b8 drm_atomic_helper_wait_for_vblanks.part.0 from drm_atomic_helper_commit_tail_rpm+0x7c/0x8c drm_atomic_helper_commit_tail_rpm from commit_tail+0x9c/0x184 commit_tail from drm_atomic_helper_commit+0x168/0x190 drm_atomic_helper_commit from drm_atomic_commit+0xb4/0xe0 drm_atomic_commit from drm_client_modeset_commit_atomic+0x23c/0x27c drm_client_modeset_commit_atomic from drm_client_modeset_commit_locked+0x60/0x1cc drm_client_modeset_commit_locked from drm_client_modeset_commit+0x24/0x40 drm_client_modeset_commit from __drm_fb_helper_restore_fbdev_mode_unlocked+0x9c/0xc4 __drm_fb_helper_restore_fbdev_mode_unlocked from drm_fb_helper_set_par+0x2c/0x3c drm_fb_helper_set_par from fbcon_init+0x3d8/0x550 fbcon_init from visual_init+0xc0/0x108 visual_init from do_bind_con_driver+0x1b8/0x3a4 do_bind_con_driver from do_take_over_console+0x140/0x1ec do_take_over_console from do_fbcon_takeover+0x70/0xd0 do_fbcon_takeover from fbcon_fb_registered+0x19c/0x1ac fbcon_fb_registered from register_framebuffer+0x190/0x21c register_framebuffer from __drm_fb_helper_initial_config_and_unlock+0x350/0x574 __drm_fb_helper_initial_config_and_unlock from exynos_drm_fbdev_client_hotplug+0x6c/0xb0 exynos_drm_fbdev_client_hotplug from drm_client_register+0x58/0x94 drm_client_register from exynos_drm_bind+0x160/0x190 exynos_drm_bind from try_to_bring_up_aggregate_device+0x200/0x2d8 try_to_bring_up_aggregate_device from __component_add+0xb0/0x170 __component_add from mixer_probe+0x74/0xcc mixer_probe from platform_probe+0x5c/0xb8 platform_probe from really_probe+0xe0/0x3d8 really_probe from __driver_probe_device+0x9c/0x1e4 __driver_probe_device from driver_probe_device+0x30/0xc0 driver_probe_device from __device_attach_driver+0xa8/0x120 __device_attach_driver from bus_for_each_drv+0x80/0xcc bus_for_each_drv from __device_attach+0xac/0x1fc __device_attach from bus_probe_device+0x8c/0x90 bus_probe_device from deferred_probe_work_func+0 ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found When reading EDID fails and driver reports no modes available, the DRM core adds an artificial 1024x786 mode to the connector. Unfortunately some variants of the Exynos HDMI (like the one in Exynos4 SoCs) are not able to drive such mode, so report a safe 640x480 mode instead of nothing in case of the EDID reading failure. This fixes the following issue observed on Trats2 board since commit 13d5b040363c ("drm/exynos: do not return negative values from .get_modes()"): [drm] Exynos DRM: using 11c00000.fimd device for DMA mapping operations exynos-drm exynos-drm: bound 11c00000.fimd (ops fimd_component_ops) exynos-drm exynos-drm: bound 12c10000.mixer (ops mixer_component_ops) exynos-dsi 11c80000.dsi: [drm:samsung_dsim_host_attach] Attached s6e8aa0 device (lanes:4 bpp:24 mode-flags:0x10b) exynos-drm exynos-drm: bound 11c80000.dsi (ops exynos_dsi_component_ops) exynos-drm exynos-drm: bound 12d00000.hdmi (ops hdmi_component_ops) [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 1 exynos-hdmi 12d00000.hdmi: [drm:hdmiphy_enable.part.0] *ERROR* PLL could not reach steady state panel-samsung-s6e8aa0 11c80000.dsi.0: ID: 0xa2, 0x20, 0x8c exynos-mixer 12c10000.mixer: timeout waiting for VSYNC ------------[ cut here ]------------ WARNING: CPU: 1 PID: 11 at drivers/gpu/drm/drm_atomic_helper.c:1682 drm_atomic_helper_wait_for_vblanks.part.0+0x2b0/0x2b8 [CRTC:70:crtc-1] vblank wait timed out Modules linked in: CPU: 1 PID: 11 Comm: kworker/u16:0 Not tainted 6.9.0-rc5-next-20240424 #14913 Hardware name: Samsung Exynos (Flattened Device Tree) Workqueue: events_unbound deferred_probe_work_func Call trace: unwind_backtrace from show_stack+0x10/0x14 show_stack from dump_stack_lvl+0x68/0x88 dump_stack_lvl from __warn+0x7c/0x1c4 __warn from warn_slowpath_fmt+0x11c/0x1a8 warn_slowpath_fmt from drm_atomic_helper_wait_for_vblanks.part.0+0x2b0/0x2b8 drm_atomic_helper_wait_for_vblanks.part.0 from drm_atomic_helper_commit_tail_rpm+0x7c/0x8c drm_atomic_helper_commit_tail_rpm from commit_tail+0x9c/0x184 commit_tail from drm_atomic_helper_commit+0x168/0x190 drm_atomic_helper_commit from drm_atomic_commit+0xb4/0xe0 drm_atomic_commit from drm_client_modeset_commit_atomic+0x23c/0x27c drm_client_modeset_commit_atomic from drm_client_modeset_commit_locked+0x60/0x1cc drm_client_modeset_commit_locked from drm_client_modeset_commit+0x24/0x40 drm_client_modeset_commit from __drm_fb_helper_restore_fbdev_mode_unlocked+0x9c/0xc4 __drm_fb_helper_restore_fbdev_mode_unlocked from drm_fb_helper_set_par+0x2c/0x3c drm_fb_helper_set_par from fbcon_init+0x3d8/0x550 fbcon_init from visual_init+0xc0/0x108 visual_init from do_bind_con_driver+0x1b8/0x3a4 do_bind_con_driver from do_take_over_console+0x140/0x1ec do_take_over_console from do_fbcon_takeover+0x70/0xd0 do_fbcon_takeover from fbcon_fb_registered+0x19c/0x1ac fbcon_fb_registered from register_framebuffer+0x190/0x21c register_framebuffer from __drm_fb_helper_initial_config_and_unlock+0x350/0x574 __drm_fb_helper_initial_config_and_unlock from exynos_drm_fbdev_client_hotplug+0x6c/0xb0 exynos_drm_fbdev_client_hotplug from drm_client_register+0x58/0x94 drm_client_register from exynos_drm_bind+0x160/0x190 exynos_drm_bind from try_to_bring_up_aggregate_device+0x200/0x2d8 try_to_bring_up_aggregate_device from __component_add+0xb0/0x170 __component_add from mixer_probe+0x74/0xcc mixer_probe from platform_probe+0x5c/0xb8 platform_probe from really_probe+0xe0/0x3d8 really_probe from __driver_probe_device+0x9c/0x1e4 __driver_probe_device from driver_probe_device+0x30/0xc0 driver_probe_device from __device_attach_driver+0xa8/0x120 __device_attach_driver from bus_for_each_drv+0x80/0xcc bus_for_each_drv from __device_attach+0xac/0x1fc __device_attach from bus_probe_device+0x8c/0x90 bus_probe_device from deferred_probe_work_func+0 ---truncated---

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: drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found When reading EDID fails and driver reports no modes available, the DRM core adds an artificial 1024x786 mode to the connector. Unfortunately some variants of the Exynos HDMI (like the one in Exynos4 SoCs) are not able to drive such mode, so report a safe 640x480 mode instead of nothing in case of the EDID reading failure. This fixes the following issue observed on Trats2 board since commit 13d5b040363c ("drm/exynos: do not return negative values from .get_modes()"): [drm] Exynos DRM: using 11c00000.fimd device for DMA mapping operations exynos-drm exynos-drm: bound 11c00000.fimd (ops fimd_component_ops) exynos-drm exynos-drm: bound 12c10000.mixer (ops mixer_component_ops) exynos-dsi 11c80000.dsi: [drm:samsung_dsim_host_attach] Attached s6e8aa0 device (lanes:4 bpp:24 mode-flags:0x10b) exynos-drm exynos-drm: bound 11c80000.dsi (ops exynos_dsi_component_ops) exynos-drm exynos-drm: bound 12d00000.hdmi (ops hdmi_component_ops) [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 1 exynos-hdmi 12d00000.hdmi: [drm:hdmiphy_enable.part.0] *ERROR* PLL could not reach steady state panel-samsung-s6e8aa0 11c80000.dsi.0: ID: 0xa2, 0x20, 0x8c exynos-mixer 12c10000.mixer: timeout waiting for VSYNC ------------[ cut here ]------------ WARNING: CPU: 1 PID: 11 at drivers/gpu/drm/drm_atomic_helper.c:1682 drm_atomic_helper_wait_for_vblanks.part.0+0x2b0/0x2b8 [CRTC:70:crtc-1] vblank wait timed out Modules linked in: CPU: 1 PID: 11 Comm: kworker/u16:0 Not tainted 6.9.0-rc5-next-20240424 #14913 Hardware name: Samsung Exynos (Flattened Device Tree) Workqueue: events_unbound deferred_probe_work_func Call trace: unwind_backtrace from show_stack+0x10/0x14 show_stack from dump_stack_lvl+0x68/0x88 dump_stack_lvl from __warn+0x7c/0x1c4 __warn from warn_slowpath_fmt+0x11c/0x1a8 warn_slowpath_fmt from drm_atomic_helper_wait_for_vblanks.part.0+0x2b0/0x2b8 drm_atomic_helper_wait_for_vblanks.part.0 from drm_atomic_helper_commit_tail_rpm+0x7c/0x8c drm_atomic_helper_commit_tail_rpm from commit_tail+0x9c/0x184 commit_tail from drm_atomic_helper_commit+0x168/0x190 drm_atomic_helper_commit from drm_atomic_commit+0xb4/0xe0 drm_atomic_commit from drm_client_modeset_commit_atomic+0x23c/0x27c drm_client_modeset_commit_atomic from drm_client_modeset_commit_locked+0x60/0x1cc drm_client_modeset_commit_locked from drm_client_modeset_commit+0x24/0x40 drm_client_modeset_commit from __drm_fb_helper_restore_fbdev_mode_unlocked+0x9c/0xc4 __drm_fb_helper_restore_fbdev_mode_unlocked from drm_fb_helper_set_par+0x2c/0x3c drm_fb_helper_set_par from fbcon_init+0x3d8/0x550 fbcon_init from visual_init+0xc0/0x108 visual_init from do_bind_con_driver+0x1b8/0x3a4 do_bind_con_driver from do_take_over_console+0x140/0x1ec do_take_over_console from do_fbcon_takeover+0x70/0xd0 do_fbcon_takeover from fbcon_fb_registered+0x19c/0x1ac fbcon_fb_registered from register_framebuffer+0x190/0x21c register_framebuffer from __drm_fb_helper_initial_config_and_unlock+0x350/0x574 __drm_fb_helper_initial_config_and_unlock from exynos_drm_fbdev_client_hotplug+0x6c/0xb0 exynos_drm_fbdev_client_hotplug from drm_client_register+0x58/0x94 drm_client_register from exynos_drm_bind+0x160/0x190 exynos_drm_bind from try_to_bring_up_aggregate_device+0x200/0x2d8 try_to_bring_up_aggregate_device from __component_add+0xb0/0x170 __component_add from mixer_probe+0x74/0xcc mixer_probe from platform_probe+0x5c/0xb8 platform_probe from really_probe+0xe0/0x3d8 really_probe from __driver_probe_device+0x9c/0x1e4 __driver_probe_device from driver_probe_device+0x30/0xc0 driver_probe_device from __device_attach_driver+0xa8/0x120 __device_attach_driver from bus_for_each_drv+0x80/0xcc bus_for_each_drv from __device_attach+0xac/0x1fc __device_attach from bus_probe_device+0x8c/0x90 bus_probe_device from deferred_probe_work_func+0 ---truncated---

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: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.

A

Official authority intelligence

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

ENISA EUVD · EUVD-2024-38727Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-W-2024-1607Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um seine Privilegien zu erweitern, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen oder einen unspezifischen Angriff durchzuführen.

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0677Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2024-39503 Référence CVE CVE-2024-39505 https://www.cve.org/CVERecord?id=CVE-2024-39505 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-39509 https://www.cve.org/CVERecord?id=CVE-2024-39509 Référence CVE CVE-2024-40901 https://www.cve.org/CVERecord?id=CVE-2024-40901 Référence CVE CVE-2024-40902 https://www.cve.org/CVERecord?id=CVE-2024-40902 Référence CVE CVE-2024-40904 https://www.cve.org/CVERecord?id=CVE-2024-40904 Référence CVE CVE-2024-40905 https://www.cve.org/CVERecord?id=CVE-2024-40905 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40931 https://www.cve.org/CVERecord?id=CVE-2024-40931 Référence CVE CVE-2024-40932 https://www.cve.org/CVERecord?id=CVE-2024-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-40905 Référence CVE CVE-2024-40906 https://www.cve.org/CVERecord?id=CVE-2024-40906 Référence CVE CVE-2024-40908 https://www.cve.org/CVERecord?id=CVE-2024-40908 Référence CVE CVE-2024-40910 https://www.cve.org/CVERecord?id=CVE-2024-40910 Référence CVE CVE-2024-40911 https://www.cve.org/CVERecord?id=CVE-2024-40911 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40913 https://www.cve.org/CVERecord?id=CVE-2024-40913 Référence CVE CVE-2024-40914 https://www.cve.org/CVERecord?id=CVE-2024-40914 Référence CVE CVE-2024-40915 https://www.cve.org/CVERecord?id=CVE-2024-40915 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40919 https://www.cve.org/CVERecord?id=CVE-2024-40919 Référence CVE CVE-2024-40920 https://www.cve.org/CVERecord?id=CVE-2024-40920 Référence CVE CVE-2024-40921 https://www.cve.org/CVERecord?id=CVE-2024-40921 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=CVE-2024-40924 Référence CVE CVE-2024-40927 https://www.cve.org/CVERecord?id=CVE-2024-40927 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40931 https://www.cve.org/CVERecord?id=CVE-2024-40931 Référence CVE CVE-2024-40932 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-39503 Référence CVE CVE-2024-39505 https://www.cve.org/CVERecord?id=CVE-2024-39505 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-39509 https://www.cve.org/CVERecord?id=CVE-2024-39509 Référence CVE CVE-2024-40901 https://www.cve.org/CVERecord?id=CVE-2024-40901 Référence CVE CVE-2024-40902 https://www.cve.org/CVERecord?id=CVE-2024-40902 Référence CVE CVE-2024-40904 https://www.cve.org/CVERecord?id=CVE-2024-40904 Référence CVE CVE-2024-40905 https://www.cve.org/CVERecord?id=CVE-2024-40905 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40932 https://www.cve.org/CVERecord?id=CVE-2024-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40942 https://www.cve.org/CVERecord?id=CVE-2024-40942 Référence CVE CVE-2024-40943 https://www.cve.org/CVERecord?id=CVE-2024-40943 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40958 https://www.cve.org/CVERecord?id=CVE-2024-40958 Référence CVE CVE-2024-40959 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-40906 Référence CVE CVE-2024-40908 https://www.cve.org/CVERecord?id=CVE-2024-40908 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40910 https://www.cve.org/CVERecord?id=CVE-2024-40910 Référence CVE CVE-2024-40911 https://www.cve.org/CVERecord?id=CVE-2024-40911 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40913 https://www.cve.org/CVERecord?id=CVE-2024-40913 Référence CVE CVE-2024-40914 https://www.cve.org/CVERecord?id=CVE-2024-40914 Référence CVE CVE-2024-40915 https://www.cve.org/CVERecord?id=CVE-2024-40915 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40917 https://www.cve.org/CVERecord?id=CVE-2024-40917 Référence CVE CVE-2024-40918 https://www.cve.org/CVERecord?id=CVE-2024-40918 Référence CVE CVE-2024-40919 https://www.cve.org/CVERecord?id=CVE-2024-40919 Référence CVE CVE-2024-40920 https://www.cve.org/CVERecord?id=CVE-2024-40920 Référence CVE CVE-2024-40921 https://www.cve.org/CVERecord?id=CVE-2024-40921 Référence CVE CVE-2024-40922 https://www.cve.org/CVERecord?id=CVE-2024-40922 Référence CVE CVE-2024-40923 https://www.cve.org/CVERecord?id=CVE-2024-40923 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-40902 Référence CVE CVE-2024-40903 https://www.cve.org/CVERecord?id=CVE-2024-40903 Référence CVE CVE-2024-40904 https://www.cve.org/CVERecord?id=CVE-2024-40904 Référence CVE CVE-2024-40905 https://www.cve.org/CVERecord?id=CVE-2024-40905 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40910 https://www.cve.org/CVERecord?id=CVE-2024-40910 Référence CVE CVE-2024-40911 https://www.cve.org/CVERecord?id=CVE-2024-40911 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40913 https://www.cve.org/CVERecord?id=CVE-2024-40913 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40920 https://www.cve.org/CVERecord?id=CVE-2024-40920 Référence CVE CVE-2024-40921 https://www.cve.org/CVERecord?id=CVE-2024-40921 Référence CVE CVE-2024-40922 https://www.cve.org/CVERecord?id=CVE-2024-40922 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=CVE-2024-40924 Référence CVE CVE-2024-40926 https://www.cve.org/CVERecord?id=CVE-2024-40926 Référence CVE CVE-2024-40927 https://www.cve.org/CVERecord?id=CVE-2024-40927 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40930 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-40906 Référence CVE CVE-2024-40908 https://www.cve.org/CVERecord?id=CVE-2024-40908 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40910 https://www.cve.org/CVERecord?id=CVE-2024-40910 Référence CVE CVE-2024-40911 https://www.cve.org/CVERecord?id=CVE-2024-40911 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40913 https://www.cve.org/CVERecord?id=CVE-2024-40913 Référence CVE CVE-2024-40914 https://www.cve.org/CVERecord?id=CVE-2024-40914 Référence CVE CVE-2024-40915 https://www.cve.org/CVERecord?id=CVE-2024-40915 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40917 https://www.cve.org/CVERecord?id=CVE-2024-40917 Référence CVE CVE-2024-40918 https://www.cve.org/CVERecord?id=CVE-2024-40918 Référence CVE CVE-2024-40919 https://www.cve.org/CVERecord?id=CVE-2024-40919 Référence CVE CVE-2024-40920 https://www.cve.org/CVERecord?id=CVE-2024-40920 Référence CVE CVE-2024-40921 https://www.cve.org/CVERecord?id=CVE-2024-40921 Référence CVE CVE-2024-40922 https://www.cve.org/CVERecord?id=CVE-2024-40922 Référence CVE CVE-2024-40923 https://www.cve.org/CVERecord?id=CVE-2024-40923 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-40906 Référence CVE CVE-2024-40908 https://www.cve.org/CVERecord?id=CVE-2024-40908 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40910 https://www.cve.org/CVERecord?id=CVE-2024-40910 Référence CVE CVE-2024-40911 https://www.cve.org/CVERecord?id=CVE-2024-40911 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40913 https://www.cve.org/CVERecord?id=CVE-2024-40913 Référence CVE CVE-2024-40914 https://www.cve.org/CVERecord?id=CVE-2024-40914 Référence CVE CVE-2024-40915 https://www.cve.org/CVERecord?id=CVE-2024-40915 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40917 https://www.cve.org/CVERecord?id=CVE-2024-40917 Référence CVE CVE-2024-40918 https://www.cve.org/CVERecord?id=CVE-2024-40918 Référence CVE CVE-2024-40919 https://www.cve.org/CVERecord?id=CVE-2024-40919 Référence CVE CVE-2024-40920 https://www.cve.org/CVERecord?id=CVE-2024-40920 Référence CVE CVE-2024-40921 https://www.cve.org/CVERecord?id=CVE-2024-40921 Référence CVE CVE-2024-40922 https://www.cve.org/CVERecord?id=CVE-2024-40922 Référence CVE CVE-2024-40923 https://www.cve.org/CVERecord?id=CVE-2024-40923 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-40902 Référence CVE CVE-2024-40903 https://www.cve.org/CVERecord?id=CVE-2024-40903 Référence CVE CVE-2024-40904 https://www.cve.org/CVERecord?id=CVE-2024-40904 Référence CVE CVE-2024-40905 https://www.cve.org/CVERecord?id=CVE-2024-40905 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40910 https://www.cve.org/CVERecord?id=CVE-2024-40910 Référence CVE CVE-2024-40911 https://www.cve.org/CVERecord?id=CVE-2024-40911 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40913 https://www.cve.org/CVERecord?id=CVE-2024-40913 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40920 https://www.cve.org/CVERecord?id=CVE-2024-40920 Référence CVE CVE-2024-40921 https://www.cve.org/CVERecord?id=CVE-2024-40921 Référence CVE CVE-2024-40922 https://www.cve.org/CVERecord?id=CVE-2024-40922 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=CVE-2024-40924 Référence CVE CVE-2024-40926 https://www.cve.org/CVERecord?id=CVE-2024-40926 Référence CVE CVE-2024-40927 https://www.cve.org/CVERecord?id=CVE-2024-40927 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40930 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-40901 Référence CVE CVE-2024-40902 https://www.cve.org/CVERecord?id=CVE-2024-40902 Référence CVE CVE-2024-40903 https://www.cve.org/CVERecord?id=CVE-2024-40903 Référence CVE CVE-2024-40904 https://www.cve.org/CVERecord?id=CVE-2024-40904 Référence CVE CVE-2024-40906 https://www.cve.org/CVERecord?id=CVE-2024-40906 Référence CVE CVE-2024-40908 https://www.cve.org/CVERecord?id=CVE-2024-40908 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40911 https://www.cve.org/CVERecord?id=CVE-2024-40911 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40919 https://www.cve.org/CVERecord?id=CVE-2024-40919 Référence CVE CVE-2024-40923 https://www.cve.org/CVERecord?id=CVE-2024-40923 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=CVE-2024-40924 Référence CVE CVE-2024-40925 https://www.cve.org/CVERecord?id=CVE-2024-40925 Référence CVE CVE-2024-40927 https://www.cve.org/CVERecord?id=CVE-2024-40927 Référence CVE CVE-2024-40928 https://www.cve.org/CVERecord?id=CVE-2024-40928 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40931 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2024-40901 Référence CVE CVE-2024-40902 https://www.cve.org/CVERecord?id=CVE-2024-40902 Référence CVE CVE-2024-40903 https://www.cve.org/CVERecord?id=CVE-2024-40903 Référence CVE CVE-2024-40904 https://www.cve.org/CVERecord?id=CVE-2024-40904 Référence CVE CVE-2024-40906 https://www.cve.org/CVERecord?id=CVE-2024-40906 Référence CVE CVE-2024-40908 https://www.cve.org/CVERecord?id=CVE-2024-40908 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40911 https://www.cve.org/CVERecord?id=CVE-2024-40911 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40919 https://www.cve.org/CVERecord?id=CVE-2024-40919 Référence CVE CVE-2024-40923 https://www.cve.org/CVERecord?id=CVE-2024-40923 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=CVE-2024-40924 Référence CVE CVE-2024-40925 https://www.cve.org/CVERecord?id=CVE-2024-40925 Référence CVE CVE-2024-40927 https://www.cve.org/CVERecord?id=CVE-2024-40927 Référence CVE CVE-2024-40928 https://www.cve.org/CVERecord?id=CVE-2024-40928 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40931 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2024-AVI-0613Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2024-40905 Référence CVE CVE-2024-40906 https://www.cve.org/CVERecord?id=CVE-2024-40906 Référence CVE CVE-2024-40908 https://www.cve.org/CVERecord?id=CVE-2024-40908 Référence CVE CVE-2024-40910 https://www.cve.org/CVERecord?id=CVE-2024-40910 Référence CVE CVE-2024-40911 https://www.cve.org/CVERecord?id=CVE-2024-40911 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40913 https://www.cve.org/CVERecord?id=CVE-2024-40913 Référence CVE CVE-2024-40914 https://www.cve.org/CVERecord?id=CVE-2024-40914 Référence CVE CVE-2024-40915 https://www.cve.org/CVERecord?id=CVE-2024-40915 Référence CVE CVE-2024-40916 https://www.cve.org/CVERecord?id=CVE-2024-40916 Référence CVE CVE-2024-40919 https://www.cve.org/CVERecord?id=CVE-2024-40919 Référence CVE CVE-2024-40920 https://www.cve.org/CVERecord?id=CVE-2024-40920 Référence CVE CVE-2024-40921 https://www.cve.org/CVERecord?id=CVE-2024-40921 Référence CVE CVE-2024-40924 https://www.cve.org/CVERecord?id=CVE-2024-40924 Référence CVE CVE-2024-40927 https://www.cve.org/CVERecord?id=CVE-2024-40927 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40931 https://www.cve.org/CVERecord?id=CVE-2024-40931 Référence CVE CVE-2024-40932 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.: Patch available
Affected: SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
Fixed: < 6.9; 5.4.279 ≤ 5.4.*; 5.10.221 ≤ 5.10.*; 5.15.162 ≤ 5.15.*; 6.1.95 ≤ 6.1.*; 6.6.35 ≤ 6.6.*; 6.9.6 ≤ 6.9.*; 6.10 ≤ *
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

04

Evidence and provenance

Published 12 Jul 2024 · Last source change 23 May 2026, 15:50 UTC · CWE not yet assigned

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-2024-38727

Product sourceVendor CSAF · Siemens ProductCERT

Remediation sourceVendor CSAF · Siemens ProductCERT

CWE sourceUnavailable

NVD statusNVD modified after enrichment

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.

2024-07-12CVE published

2026-05-23Fixed release or patch reference recorded

ENISA EUVD · EUVD-2024-38727↗Vendor CSAF · Siemens ProductCERT↗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↗

drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found

Ubuntu vendor 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-2024-38727

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication

drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found

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

EUVD-2024-38727

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

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