BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-40947High confidence

ima: Avoid blocking in RCU read-side critical section

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

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 releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 Sept 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 record ↗Source updated 8 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.

2 current
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
ima: Avoid blocking in RCU read-side critical section, a panic happens in ima_match_policy.
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
ima: Avoid blocking in RCU read-side critical section, a panic happens in ima_match_policy.
Remediation
Update to V3.1 or later version
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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

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 actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ima: Avoid blocking in RCU read-side critical section A panic happens in ima_match_policy: BUG: unable to handle kernel NULL pointer dereference at 0000000000000010 PGD 42f873067 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 5 PID: 1286325 Comm: kubeletmonit.sh Kdump: loaded Tainted: P Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 RIP: 0010:ima_match_policy+0x84/0x450 Code: 49 89 fc 41 89 cf 31 ed 89 44 24 14 eb 1c 44 39 7b 18 74 26 41 83 ff 05 74 20 48 8b 1b 48 3b 1d f2 b9 f4 00 0f 84 9c 01 00 00 <44> 85 73 10 74 ea 44 8b 6b 14 41 f6 c5 01 75 d4 41 f6 c5 02 74 0f RSP: 0018:ff71570009e07a80 EFLAGS: 00010207 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000200 RDX: ffffffffad8dc7c0 RSI: 0000000024924925 RDI: ff3e27850dea2000 RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffffabfce739 R10: ff3e27810cc42400 R11: 0000000000000000 R12: ff3e2781825ef970 R13: 00000000ff3e2785 R14: 000000000000000c R15: 0000000000000001 FS: 00007f5195b51740(0000) GS:ff3e278b12d40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000010 CR3: 0000000626d24002 CR4: 0000000000361ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ima_get_action+0x22/0x30 process_measurement+0xb0/0x830 ? page_add_file_rmap+0x15/0x170 ? alloc_set_pte+0x269/0x4c0 ? prep_new_page+0x81/0x140 ? simple_xattr_get+0x75/0xa0 ? selinux_file_open+0x9d/0xf0 ima_file_check+0x64/0x90 path_openat+0x571/0x1720 do_filp_open+0x9b/0x110 ? page_counter_try_charge+0x57/0xc0 ? files_cgroup_alloc_fd+0x38/0x60 ? __alloc_fd+0xd4/0x250 ? do_sys_open+0x1bd/0x250 do_sys_open+0x1bd/0x250 do_syscall_64+0x5d/0x1d0 entry_SYSCALL_64_after_hwframe+0x65/0xca Commit c7423dbdbc9e ("ima: Handle -ESTALE returned by ima_filter_rule_match()") introduced call to ima_lsm_copy_rule within a RCU read-side critical section which contains kmalloc with GFP_KERNEL. This implies a possible sleep and violates limitations of RCU read-side critical sections on non-PREEMPT systems. Sleeping within RCU read-side critical section might cause synchronize_rcu() returning early and break RCU protection, allowing a UAF to happen. The root cause of this issue could be described as follows: | Thread A | Thread B | | |ima_match_policy | | | rcu_read_lock | |ima_lsm_update_rule | | | synchronize_rcu | | | | kmalloc(GFP_KERNEL)| | | sleep | ==> synchronize_rcu returns early | kfree(entry) | | | | entry = entry->next| ==> UAF happens and entry now becomes NULL (or could be anything). | | entry->action | ==> Accessing entry might cause panic. To fix this issue, we are converting all kmalloc that is called within RCU read-side critical section to use GFP_ATOMIC. [PM: fixed missing comment, long lines, !CONFIG_IMA_LSM_RULES case]

What

In the Linux kernel, the following vulnerability has been resolved: ima: Avoid blocking in RCU read-side critical section A panic happens in ima_match_policy: BUG: unable to handle kernel NULL pointer dereference at 0000000000000010 PGD 42f873067 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 5 PID: 1286325 Comm: kubeletmonit.sh Kdump: loaded Tainted: P Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 RIP: 0010:ima_match_policy+0x84/0x450 Code: 49 89 fc 41 89 cf 31 ed 89 44 24 14 eb 1c 44 39 7b 18 74 26 41 83 ff 05 74 20 48 8b 1b 48 3b 1d f2 b9 f4 00 0f 84 9c 01 00 00 <44> 85 73 10 74 ea 44 8b 6b 14 41 f6 c5 01 75 d4 41 f6 c5 02 74 0f RSP: 0018:ff71570009e07a80 EFLAGS: 00010207 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000200 RDX: ffffffffad8dc7c0 RSI: 0000000024924925 RDI: ff3e27850dea2000 RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffffabfce739 R10: ff3e27810cc42400 R11: 0000000000000000 R12: ff3e2781825ef970 R13: 00000000ff3e2785 R14: 000000000000000c R15: 0000000000000001 FS: 00007f5195b51740(0000) GS:ff3e278b12d40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000010 CR3: 0000000626d24002 CR4: 0000000000361ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ima_get_action+0x22/0x30 process_measurement+0xb0/0x830 ? page_add_file_rmap+0x15/0x170 ? alloc_set_pte+0x269/0x4c0 ? prep_new_page+0x81/0x140 ? simple_xattr_get+0x75/0xa0 ? selinux_file_open+0x9d/0xf0 ima_file_check+0x64/0x90 path_openat+0x571/0x1720 do_filp_open+0x9b/0x110 ? page_counter_try_charge+0x57/0xc0 ? files_cgroup_alloc_fd+0x38/0x60 ? __alloc_fd+0xd4/0x250 ? do_sys_open+0x1bd/0x250 do_sys_open+0x1bd/0x250 do_syscall_64+0x5d/0x1d0 entry_SYSCALL_64_after_hwframe+0x65/0xca Commit c7423dbdbc9e ("ima: Handle -ESTALE returned by ima_filter_rule_match()") introduced call to ima_lsm_copy_rule within a RCU read-side critical section which contains kmalloc with GFP_KERNEL. This implies a possible sleep and violates limitations of RCU read-side critical sections on non-PREEMPT systems. Sleeping within RCU read-side critical section might cause synchronize_rcu() returning early and break RCU protection, allowing a UAF to happen. The root cause of this issue could be described as follows: | Thread A | Thread B | | |ima_match_policy | | | rcu_read_lock | |ima_lsm_update_rule | | | synchronize_rcu | | | | kmalloc(GFP_KERNEL)| | | sleep | ==> synchronize_rcu returns early | kfree(entry) | | | | entry = entry->next| ==> UAF happens and entry now becomes NULL (or could be anything). | | entry->action | ==> Accessing entry might cause panic. To fix this issue, we are converting all kmalloc that is called within RCU read-side critical section to use GFP_ATOMIC. [PM: fixed missing comment, long lines, !CONFIG_IMA_LSM_RULES case]

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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: ima: Avoid blocking in RCU read-side critical section A panic happens in ima_match_policy: BUG: unable to handle kernel NULL pointer dereference at 0000000000000010 PGD 42f873067 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 5 PID: 1286325 Comm: kubeletmonit.sh Kdump: loaded Tainted: P Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 RIP: 0010:ima_match_policy+0x84/0x450 Code: 49 89 fc 41 89 cf 31 ed 89 44 24 14 eb 1c 44 39 7b 18 74 26 41 83 ff 05 74 20 48 8b 1b 48 3b 1d f2 b9 f4 00 0f 84 9c 01 00 00 <44> 85 73 10 74 ea 44 8b 6b 14 41 f6 c5 01 75 d4 41 f6 c5 02 74 0f RSP: 0018:ff71570009e07a80 EFLAGS: 00010207 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000200 RDX: ffffffffad8dc7c0 RSI: 0000000024924925 RDI: ff3e27850dea2000 RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffffabfce739 R10: ff3e27810cc42400 R11: 0000000000000000 R12: ff3e2781825ef970 R13: 00000000ff3e2785 R14: 000000000000000c R15: 0000000000000001 FS: 00007f5195b51740(0000) GS:ff3e278b12d40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000010 CR3: 0000000626d24002 CR4: 0000000000361ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ima_get_action+0x22/0x30 process_measurement+0xb0/0x830 ? page_add_file_rmap+0x15/0x170 ? alloc_set_pte+0x269/0x4c0 ? prep_new_page+0x81/0x140 ? simple_xattr_get+0x75/0xa0 ? selinux_file_open+0x9d/0xf0 ima_file_check+0x64/0x90 path_openat+0x571/0x1720 do_filp_open+0x9b/0x110 ? page_counter_try_charge+0x57/0xc0 ? files_cgroup_alloc_fd+0x38/0x60 ? __alloc_fd+0xd4/0x250 ? do_sys_open+0x1bd/0x250 do_sys_open+0x1bd/0x250 do_syscall_64+0x5d/0x1d0 entry_SYSCALL_64_after_hwframe+0x65/0xca Commit c7423dbdbc9e ("ima: Handle -ESTALE returned by ima_filter_rule_match()") introduced call to ima_lsm_copy_rule within a RCU read-side critical section which contains kmalloc with GFP_KERNEL. This implies a possible sleep and violates limitations of RCU read-side critical sections on non-PREEMPT systems. Sleeping within RCU read-side critical section might cause synchronize_rcu() returning early and break RCU protection, allowing a UAF to happen. The root cause of this issue could be described as follows: | Thread A | Thread B | | |ima_match_policy | | | rcu_read_lock | |ima_lsm_update_rule | | | synchronize_rcu | | | | kmalloc(GFP_KERNEL)| | | sleep | ==> synchronize_rcu returns early | kfree(entry) | | | | entry = entry->next| ==> UAF happens and entry now becomes NULL (or could be anything). | | entry->action | ==> Accessing entry might cause panic. To fix this issue, we are converting all kmalloc that is called within RCU read-side critical section to use GFP_ATOMIC. [PM: fixed missing comment, long lines, !CONFIG_IMA_LSM_RULES case]

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-476
A

Official authority intelligence

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

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-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=CVE-2024-40945 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 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=CVE-2024-40959 Référence CVE CVE-2024-40960 https://www.cve.org/CVERecord?id=CVE-2024-40960 Référence CVE CVE-2024-40961 https://www.cve.org/CVERecord?id=CVE-2024-40961 Référence CVE CVE-2024-40963 https://www.cve.org/CVERecord?id=CVE-2024-40963 Référence CVE CVE-2024-40968 https://www.cve.org/CVERecord?id=CVE-2024-40968 Référence CVE CVE-2024-40971 https://www.cve.org/CVERecord?id=CVE-2024-40971 Référence CVE CVE-2024-40974 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-40934 Référence CVE CVE-2024-40935 https://www.cve.org/CVERecord?id=CVE-2024-40935 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 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-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40956 https://www.cve.org/CVERecord?id=CVE-2024-40956 Référence CVE CVE-2024-40957 https://www.cve.org/CVERecord?id=CVE-2024-40957 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=CVE-2024-40959 Référence CVE CVE-2024-40960 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-40937 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 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-40944 https://www.cve.org/CVERecord?id=CVE-2024-40944 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40949 https://www.cve.org/CVERecord?id=CVE-2024-40949 Référence CVE CVE-2024-40951 https://www.cve.org/CVERecord?id=CVE-2024-40951 Référence CVE CVE-2024-40952 https://www.cve.org/CVERecord?id=CVE-2024-40952 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40955 https://www.cve.org/CVERecord?id=CVE-2024-40955 Référence CVE CVE-2024-40956 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-40937 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 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-40944 https://www.cve.org/CVERecord?id=CVE-2024-40944 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40949 https://www.cve.org/CVERecord?id=CVE-2024-40949 Référence CVE CVE-2024-40951 https://www.cve.org/CVERecord?id=CVE-2024-40951 Référence CVE CVE-2024-40952 https://www.cve.org/CVERecord?id=CVE-2024-40952 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40955 https://www.cve.org/CVERecord?id=CVE-2024-40955 Référence CVE CVE-2024-40956 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-40937 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 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-40944 https://www.cve.org/CVERecord?id=CVE-2024-40944 Référence CVE CVE-2024-40945 https://www.cve.org/CVERecord?id=CVE-2024-40945 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40949 https://www.cve.org/CVERecord?id=CVE-2024-40949 Référence CVE CVE-2024-40951 https://www.cve.org/CVERecord?id=CVE-2024-40951 Référence CVE CVE-2024-40952 https://www.cve.org/CVERecord?id=CVE-2024-40952 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40955 https://www.cve.org/CVERecord?id=CVE-2024-40955 Référence CVE CVE-2024-40956 https://www.cve.org/CVERecord?id=

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

ons Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian DSA-5747-1 du 12 août 2024 https://lists.debian.org/debian-security-announce/2024/msg00159.html Référence CVE CVE-2022-48666 https://www.cve.org/CVERecord?id=CVE-2022-48666 Référence CVE CVE-2024-36484 https://www.cve.org/CVERecord?id=CVE-2024-36484 Référence CVE CVE-2024-36901 https://www.cve.org/CVERecord?id=CVE-2024-36901 Référence CVE CVE-2024-36938 https://www.cve.org/CVERecord?id=CVE-2024-36938 Référence CVE CVE-2024-39487 https://www.cve.org/CVERecord?id=CVE-2024-39487 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 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=CVE-2024-41020 Référence CVE CVE-2024-41022 https://www.cve.org/CVERecord?id=CVE-2024-41022 Référence CVE CVE-2024-41034 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-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40935 https://www.cve.org/CVERecord?id=CVE-2024-40935 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 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-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40956 https://www.cve.org/CVERecord?id=CVE-2024-40956 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=CVE-2024-40959 Référence CVE CVE-2024-40960 https://www.cve.org/CVERecord?id=CVE-2024-40960 Référence CVE CVE-2024-40961 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-40932 Référence CVE CVE-2024-40934 https://www.cve.org/CVERecord?id=CVE-2024-40934 Référence CVE CVE-2024-40935 https://www.cve.org/CVERecord?id=CVE-2024-40935 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 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-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40956 https://www.cve.org/CVERecord?id=CVE-2024-40956 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=CVE-2024-40959 Référence CVE CVE-2024-40960 https://www.cve.org/CVERecord?id=CVE-2024-40960 Référence CVE CVE-2024-40961 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40908 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-40925 https://www.cve.org/CVERecord?id=CVE-2024-40925 Référence CVE CVE-2024-40928 https://www.cve.org/CVERecord?id=CVE-2024-40928 Référence CVE CVE-2024-40931 https://www.cve.org/CVERecord?id=CVE-2024-40931 Référence CVE CVE-2024-40935 https://www.cve.org/CVERecord?id=CVE-2024-40935 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 Référence CVE CVE-2024-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40960 https://www.cve.org/CVERecord?id=CVE-2024-40960 Référence CVE CVE-2024-40961 https://www.cve.org/CVERecord?id=CVE-2024-40961 Référence CVE CVE-2024-40966 https://www.cve.org/CVERecord?id=CVE-2024-40966 Référence CVE CVE-2024-40970 https://www.cve.org/CVERecord?id=CVE-2024-40970 Référence CVE CVE-2024-40972 https://www.cve.org/CVERecord?id=CVE-2024-40972 Référence CVE CVE-2024-40975 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-40935 Référence CVE CVE-2024-40937 https://www.cve.org/CVERecord?id=CVE-2024-40937 Référence CVE CVE-2024-40938 https://www.cve.org/CVERecord?id=CVE-2024-40938 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40940 https://www.cve.org/CVERecord?id=CVE-2024-40940 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-40947 https://www.cve.org/CVERecord?id=CVE-2024-40947 Référence CVE CVE-2024-40948 https://www.cve.org/CVERecord?id=CVE-2024-40948 Référence CVE CVE-2024-40953 https://www.cve.org/CVERecord?id=CVE-2024-40953 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40956 https://www.cve.org/CVERecord?id=CVE-2024-40956 Référence CVE CVE-2024-40957 https://www.cve.org/CVERecord?id=CVE-2024-40957 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=CVE-2024-40959 Référence CVE CVE-2024-40960 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
RUGGEDCOM RST2428P (6GK6242-6PA00); SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Fixed
< 6.2; 5.10.222 ≤ 5.10.*; 5.15.163 ≤ 5.15.*; 6.1.98 ≤ 6.1.*; 6.6.39 ≤ 6.6.*; 6.9.7 ≤ 6.9.*; 6.10 ≤ *
Action
Update to V3.1 or later version
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 12 Jul 2024 · Last source change 5 Aug 2026, 11:34 UTC · CWE-476 · NULL Pointer Dereference

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-2024-38834
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-38834↗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.
Free version - for non-commercial use only.CVE-2024-40947 · cve.blacktree.nl