BlackTreeIndependent security intelligence

Full vulnerability report · 2024

CVE-2024-41004High confidence

tracing: Build event generation tests only as modules

Linux · Linux

5.5MediumCVSS 3.1

Recommended action

Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

13 package states

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.

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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 Sept 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.

3 current

SSA-265688 · CSAF 2.0 · revision 13 · interimSiemens ProductCERTSSA-265688: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.1

1 known affected

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

SIMATIC S7-1500 TM MFP - GNU/Linux subsystem

Summary: tracing: Build event generation tests only as modules The kprobes and synth event generation test modules add events and lock (get a reference) those event file reference in module init function, and unlock and delete it in module exit function. This is because those are designed for playing as modules. If we make those modules as built-in, those events are left locked in the kernel, and never be removed.
Remediation: Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

SSA-355557 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-355557: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.2

3 known not affected

The vendor explicitly states that these products are not affected by this CVE.

RUGGEDCOM RST2428P (6GK6242-6PA00)
SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
SCALANCE XCM-/XRM-/XCH-/XRH-300 family

Summary: tracing: Build event generation tests only as modules The kprobes and synth event generation test modules add events and lock (get a reference) those event file reference in module init function, and unlock and delete it in module exit function. This is because those are designed for playing as modules. If we make those modules as built-in, those events are left locked in the kernel, and never be removed.
Remediation: No remediation text is recorded.

SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1

2 known affected

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

RUGGEDCOM RST2428P (6GK6242-6PA00)
SCALANCE XCM-/XRM-/XCH-/XRH-300 family

Summary: tracing: Build event generation tests only as modules The kprobes and synth event generation test modules add events and lock (get a reference) those event file reference in module init function, and unlock and delete it in module exit function. This is because those are designed for playing as modules. If we make those modules as built-in, those events are left locked in the kernel, and never be removed.
Remediation: Update to V3.1 or later version

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

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

What, why and how

In the Linux kernel, the following vulnerability has been resolved: tracing: Build event generation tests only as modules The kprobes and synth event generation test modules add events and lock (get a reference) those event file reference in module init function, and unlock and delete it in module exit function. This is because those are designed for playing as modules. If we make those modules as built-in, those events are left locked in the kernel, and never be removed. This causes kprobe event self-test failure as below. [ 97.349708] ------------[ cut here ]------------ [ 97.353453] WARNING: CPU: 3 PID: 1 at kernel/trace/trace_kprobe.c:2133 kprobe_trace_self_tests_init+0x3f1/0x480 [ 97.357106] Modules linked in: [ 97.358488] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 6.9.0-g699646734ab5-dirty #14 [ 97.361556] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 [ 97.363880] RIP: 0010:kprobe_trace_self_tests_init+0x3f1/0x480 [ 97.365538] Code: a8 24 08 82 e9 ae fd ff ff 90 0f 0b 90 48 c7 c7 e5 aa 0b 82 e9 ee fc ff ff 90 0f 0b 90 48 c7 c7 2d 61 06 82 e9 8e fd ff ff 90 <0f> 0b 90 48 c7 c7 33 0b 0c 82 89 c6 e8 6e 03 1f ff 41 ff c7 e9 90 [ 97.370429] RSP: 0000:ffffc90000013b50 EFLAGS: 00010286 [ 97.371852] RAX: 00000000fffffff0 RBX: ffff888005919c00 RCX: 0000000000000000 [ 97.373829] RDX: ffff888003f40000 RSI: ffffffff8236a598 RDI: ffff888003f40a68 [ 97.375715] RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 [ 97.377675] R10: ffffffff811c9ae5 R11: ffffffff8120c4e0 R12: 0000000000000000 [ 97.379591] R13: 0000000000000001 R14: 0000000000000015 R15: 0000000000000000 [ 97.381536] FS: 0000000000000000(0000) GS:ffff88807dcc0000(0000) knlGS:0000000000000000 [ 97.383813] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 97.385449] CR2: 0000000000000000 CR3: 0000000002244000 CR4: 00000000000006b0 [ 97.387347] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 97.389277] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 97.391196] Call Trace: [ 97.391967] <TASK> [ 97.392647] ? __warn+0xcc/0x180 [ 97.393640] ? kprobe_trace_self_tests_init+0x3f1/0x480 [ 97.395181] ? report_bug+0xbd/0x150 [ 97.396234] ? handle_bug+0x3e/0x60 [ 97.397311] ? exc_invalid_op+0x1a/0x50 [ 97.398434] ? asm_exc_invalid_op+0x1a/0x20 [ 97.399652] ? trace_kprobe_is_busy+0x20/0x20 [ 97.400904] ? tracing_reset_all_online_cpus+0x15/0x90 [ 97.402304] ? kprobe_trace_self_tests_init+0x3f1/0x480 [ 97.403773] ? init_kprobe_trace+0x50/0x50 [ 97.404972] do_one_initcall+0x112/0x240 [ 97.406113] do_initcall_level+0x95/0xb0 [ 97.407286] ? kernel_init+0x1a/0x1a0 [ 97.408401] do_initcalls+0x3f/0x70 [ 97.409452] kernel_init_freeable+0x16f/0x1e0 [ 97.410662] ? rest_init+0x1f0/0x1f0 [ 97.411738] kernel_init+0x1a/0x1a0 [ 97.412788] ret_from_fork+0x39/0x50 [ 97.413817] ? rest_init+0x1f0/0x1f0 [ 97.414844] ret_from_fork_asm+0x11/0x20 [ 97.416285] </TASK> [ 97.417134] irq event stamp: 13437323 [ 97.418376] hardirqs last enabled at (13437337): [<ffffffff8110bc0c>] console_unlock+0x11c/0x150 [ 97.421285] hardirqs last disabled at (13437370): [<ffffffff8110bbf1>] console_unlock+0x101/0x150 [ 97.423838] softirqs last enabled at (13437366): [<ffffffff8108e17f>] handle_softirqs+0x23f/0x2a0 [ 97.426450] softirqs last disabled at (13437393): [<ffffffff8108e346>] __irq_exit_rcu+0x66/0xd0 [ 97.428850] ---[ end trace 0000000000000000 ]--- And also, since we can not cleanup dynamic_event file, ftracetest are failed too. To avoid these issues, build these tests only as modules.

What

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

Why

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

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → 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.

Official authority intelligence

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

ENISA EUVD · EUVD-2024-39353Official 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-40980 Référence CVE CVE-2024-40981 https://www.cve.org/CVERecord?id=CVE-2024-40981 Référence CVE CVE-2024-40983 https://www.cve.org/CVERecord?id=CVE-2024-40983 Référence CVE CVE-2024-40984 https://www.cve.org/CVERecord?id=CVE-2024-40984 Référence CVE CVE-2024-40987 https://www.cve.org/CVERecord?id=CVE-2024-40987 Référence CVE CVE-2024-40988 https://www.cve.org/CVERecord?id=CVE-2024-40988 Référence CVE CVE-2024-40990 https://www.cve.org/CVERecord?id=CVE-2024-40990 Référence CVE CVE-2024-40995 https://www.cve.org/CVERecord?id=CVE-2024-40995 Référence CVE CVE-2024-41000 https://www.cve.org/CVERecord?id=CVE-2024-41000 Référence CVE CVE-2024-41004 https://www.cve.org/CVERecord?id=CVE-2024-41004 Référence CVE CVE-2024-41005 https://www.cve.org/CVERecord?id=CVE-2024-41005 Référence CVE CVE-2024-41006 https://www.cve.org/CVERecord?id=CVE-2024-41006 Référence CVE CVE-2024-41007 https://www.cve.org/CVERecord?id=CVE-2024-41007 Référence CVE CVE-2024-41009 https://www.cve.org/CVERecord?id=CVE-2024-41009 Référence CVE CVE-2024-41012 https://www.cve.org/CVERecord?id=CVE-2024-41012 Référence CVE CVE-2024-41015 https://www.cve.org/CVERecord?id=CVE-2024-41015 Référence CVE CVE-2024-41017 https://www.cve.org/CVERecord?id=CVE-2024-41017 Référence CVE CVE-2024-41020 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-40989 Référence CVE CVE-2024-40990 https://www.cve.org/CVERecord?id=CVE-2024-40990 Référence CVE CVE-2024-40993 https://www.cve.org/CVERecord?id=CVE-2024-40993 Référence CVE CVE-2024-40994 https://www.cve.org/CVERecord?id=CVE-2024-40994 Référence CVE CVE-2024-40995 https://www.cve.org/CVERecord?id=CVE-2024-40995 Référence CVE CVE-2024-40996 https://www.cve.org/CVERecord?id=CVE-2024-40996 Référence CVE CVE-2024-41000 https://www.cve.org/CVERecord?id=CVE-2024-41000 Référence CVE CVE-2024-41001 https://www.cve.org/CVERecord?id=CVE-2024-41001 Référence CVE CVE-2024-41002 https://www.cve.org/CVERecord?id=CVE-2024-41002 Référence CVE CVE-2024-41004 https://www.cve.org/CVERecord?id=CVE-2024-41004 Référence CVE CVE-2024-41005 https://www.cve.org/CVERecord?id=CVE-2024-41005 Référence CVE CVE-2024-41006 https://www.cve.org/CVERecord?id=CVE-2024-41006 Référence CVE CVE-2024-41007 https://www.cve.org/CVERecord?id=CVE-2024-41007 Référence CVE CVE-2024-41009 https://www.cve.org/CVERecord?id=CVE-2024-41009 Référence CVE CVE-2024-41012 https://www.cve.org/CVERecord?id=CVE-2024-41012 Référence CVE CVE-2024-41015 https://www.cve.org/CVERecord?id=CVE-2024-41015 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=CVE-2024-41016 Référence CVE CVE-2024-41017 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-40995 Référence CVE CVE-2024-40996 https://www.cve.org/CVERecord?id=CVE-2024-40996 Référence CVE CVE-2024-40997 https://www.cve.org/CVERecord?id=CVE-2024-40997 Référence CVE CVE-2024-40998 https://www.cve.org/CVERecord?id=CVE-2024-40998 Référence CVE CVE-2024-40999 https://www.cve.org/CVERecord?id=CVE-2024-40999 Référence CVE CVE-2024-41000 https://www.cve.org/CVERecord?id=CVE-2024-41000 Référence CVE CVE-2024-41001 https://www.cve.org/CVERecord?id=CVE-2024-41001 Référence CVE CVE-2024-41002 https://www.cve.org/CVERecord?id=CVE-2024-41002 Référence CVE CVE-2024-41003 https://www.cve.org/CVERecord?id=CVE-2024-41003 Référence CVE CVE-2024-41004 https://www.cve.org/CVERecord?id=CVE-2024-41004 Référence CVE CVE-2024-41005 https://www.cve.org/CVERecord?id=CVE-2024-41005 Référence CVE CVE-2024-41006 https://www.cve.org/CVERecord?id=CVE-2024-41006 Référence CVE CVE-2024-41007 https://www.cve.org/CVERecord?id=CVE-2024-41007 Référence CVE CVE-2024-41009 https://www.cve.org/CVERecord?id=CVE-2024-41009 Référence CVE CVE-2024-41027 https://www.cve.org/CVERecord?id=CVE-2024-41027 Référence CVE CVE-2024-41034 https://www.cve.org/CVERecord?id=CVE-2024-41034 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41040 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-40989 Référence CVE CVE-2024-40990 https://www.cve.org/CVERecord?id=CVE-2024-40990 Référence CVE CVE-2024-40992 https://www.cve.org/CVERecord?id=CVE-2024-40992 Référence CVE CVE-2024-40994 https://www.cve.org/CVERecord?id=CVE-2024-40994 Référence CVE CVE-2024-40995 https://www.cve.org/CVERecord?id=CVE-2024-40995 Référence CVE CVE-2024-40997 https://www.cve.org/CVERecord?id=CVE-2024-40997 Référence CVE CVE-2024-41000 https://www.cve.org/CVERecord?id=CVE-2024-41000 Référence CVE CVE-2024-41001 https://www.cve.org/CVERecord?id=CVE-2024-41001 Référence CVE CVE-2024-41002 https://www.cve.org/CVERecord?id=CVE-2024-41002 Référence CVE CVE-2024-41004 https://www.cve.org/CVERecord?id=CVE-2024-41004 Référence CVE CVE-2024-41007 https://www.cve.org/CVERecord?id=CVE-2024-41007 Référence CVE CVE-2024-41009 https://www.cve.org/CVERecord?id=CVE-2024-41009 Référence CVE CVE-2024-41010 https://www.cve.org/CVERecord?id=CVE-2024-41010 Référence CVE CVE-2024-41011 https://www.cve.org/CVERecord?id=CVE-2024-41011 Référence CVE CVE-2024-41012 https://www.cve.org/CVERecord?id=CVE-2024-41012 Référence CVE CVE-2024-41015 https://www.cve.org/CVERecord?id=CVE-2024-41015 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=CVE-2024-41016 Référence CVE CVE-2024-41020 https://www.cve.org/CVERecord?id=

Official advisory

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

Official advisory

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

d?id=CVE-2024-40995 Référence CVE CVE-2024-40996 https://www.cve.org/CVERecord?id=CVE-2024-40996 Référence CVE CVE-2024-40997 https://www.cve.org/CVERecord?id=CVE-2024-40997 Référence CVE CVE-2024-40998 https://www.cve.org/CVERecord?id=CVE-2024-40998 Référence CVE CVE-2024-40999 https://www.cve.org/CVERecord?id=CVE-2024-40999 Référence CVE CVE-2024-41000 https://www.cve.org/CVERecord?id=CVE-2024-41000 Référence CVE CVE-2024-41001 https://www.cve.org/CVERecord?id=CVE-2024-41001 Référence CVE CVE-2024-41002 https://www.cve.org/CVERecord?id=CVE-2024-41002 Référence CVE CVE-2024-41003 https://www.cve.org/CVERecord?id=CVE-2024-41003 Référence CVE CVE-2024-41004 https://www.cve.org/CVERecord?id=CVE-2024-41004 Référence CVE CVE-2024-41005 https://www.cve.org/CVERecord?id=CVE-2024-41005 Référence CVE CVE-2024-41006 https://www.cve.org/CVERecord?id=CVE-2024-41006 Référence CVE CVE-2024-41007 https://www.cve.org/CVERecord?id=CVE-2024-41007 Référence CVE CVE-2024-41027 https://www.cve.org/CVERecord?id=CVE-2024-41027 Référence CVE CVE-2024-41034 https://www.cve.org/CVERecord?id=CVE-2024-41034 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41040 https://www.cve.org/CVERecord?id=CVE-2024-41040 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=

Official advisory

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

Official advisory

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

d?id=CVE-2024-40987 Référence CVE CVE-2024-40988 https://www.cve.org/CVERecord?id=CVE-2024-40988 Référence CVE CVE-2024-40989 https://www.cve.org/CVERecord?id=CVE-2024-40989 Référence CVE CVE-2024-40990 https://www.cve.org/CVERecord?id=CVE-2024-40990 Référence CVE CVE-2024-40994 https://www.cve.org/CVERecord?id=CVE-2024-40994 Référence CVE CVE-2024-40995 https://www.cve.org/CVERecord?id=CVE-2024-40995 Référence CVE CVE-2024-40998 https://www.cve.org/CVERecord?id=CVE-2024-40998 Référence CVE CVE-2024-40999 https://www.cve.org/CVERecord?id=CVE-2024-40999 Référence CVE CVE-2024-41002 https://www.cve.org/CVERecord?id=CVE-2024-41002 Référence CVE CVE-2024-41004 https://www.cve.org/CVERecord?id=CVE-2024-41004 Référence CVE CVE-2024-41006 https://www.cve.org/CVERecord?id=CVE-2024-41006 Référence CVE CVE-2024-41009 https://www.cve.org/CVERecord?id=CVE-2024-41009 Référence CVE CVE-2024-41011 https://www.cve.org/CVERecord?id=CVE-2024-41011 Référence CVE CVE-2024-41012 https://www.cve.org/CVERecord?id=CVE-2024-41012 Référence CVE CVE-2024-41013 https://www.cve.org/CVERecord?id=CVE-2024-41013 Référence CVE CVE-2024-41014 https://www.cve.org/CVERecord?id=CVE-2024-41014 Référence CVE CVE-2024-41015 https://www.cve.org/CVERecord?id=CVE-2024-41015 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=

Official advisory

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

Official advisory

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

d?id=CVE-2024-40989 Référence CVE CVE-2024-40990 https://www.cve.org/CVERecord?id=CVE-2024-40990 Référence CVE CVE-2024-40993 https://www.cve.org/CVERecord?id=CVE-2024-40993 Référence CVE CVE-2024-40994 https://www.cve.org/CVERecord?id=CVE-2024-40994 Référence CVE CVE-2024-40995 https://www.cve.org/CVERecord?id=CVE-2024-40995 Référence CVE CVE-2024-40996 https://www.cve.org/CVERecord?id=CVE-2024-40996 Référence CVE CVE-2024-41000 https://www.cve.org/CVERecord?id=CVE-2024-41000 Référence CVE CVE-2024-41001 https://www.cve.org/CVERecord?id=CVE-2024-41001 Référence CVE CVE-2024-41002 https://www.cve.org/CVERecord?id=CVE-2024-41002 Référence CVE CVE-2024-41004 https://www.cve.org/CVERecord?id=CVE-2024-41004 Référence CVE CVE-2024-41005 https://www.cve.org/CVERecord?id=CVE-2024-41005 Référence CVE CVE-2024-41006 https://www.cve.org/CVERecord?id=CVE-2024-41006 Gestion détaillée du document le 19 juillet 2024 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
Fixed: < 5.6; 5.10.221 ≤ 5.10.*; 5.15.162 ≤ 5.15.*; 6.1.96 ≤ 6.1.*; 6.6.36 ≤ 6.6.*; 6.9.7 ≤ 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.

Evidence and provenance

Published 12 Jul 2024 · Last source change 12 May 2026, 11:56 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-39353

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-12Fixed release or patch reference recorded

ENISA EUVD · EUVD-2024-39353↗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↗

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.

tracing: Build event generation tests only as modules

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

EUVD-2024-39353

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.