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

can: bcm: Remove proc entry when dev is unregistered.

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.

15 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 9 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 9 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 9 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 9 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 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 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 9 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 9 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 9 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 9 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 9 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 9 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 9 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 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 9 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.

1 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 affected

The vendor explicitly identifies these products as 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
can: bcm: Remove proc entry when dev is unregistered.
Remediation
Update to V3.2 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-42032

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: can: bcm: Remove proc entry when dev is unregistered. syzkaller reported a warning in bcm_connect() below. [0] The repro calls connect() to vxcan1, removes vxcan1, and calls connect() with ifindex == 0. Calling connect() for a BCM socket allocates a proc entry. Then, bcm_sk(sk)->bound is set to 1 to prevent further connect(). However, removing the bound device resets bcm_sk(sk)->bound to 0 in bcm_notify(). The 2nd connect() tries to allocate a proc entry with the same name and sets NULL to bcm_sk(sk)->bcm_proc_read, leaking the original proc entry. Since the proc entry is available only for connect()ed sockets, let's clean up the entry when the bound netdev is unregistered. [0]: proc_dir_entry 'can-bcm/2456' already registered WARNING: CPU: 1 PID: 394 at fs/proc/generic.c:376 proc_register+0x645/0x8f0 fs/proc/generic.c:375 Modules linked in: CPU: 1 PID: 394 Comm: syz-executor403 Not tainted 6.10.0-rc7-g852e42cc2dd4 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:proc_register+0x645/0x8f0 fs/proc/generic.c:375 Code: 00 00 00 00 00 48 85 ed 0f 85 97 02 00 00 4d 85 f6 0f 85 9f 02 00 00 48 c7 c7 9b cb cf 87 48 89 de 4c 89 fa e8 1c 6f eb fe 90 <0f> 0b 90 90 48 c7 c7 98 37 99 89 e8 cb 7e 22 05 bb 00 00 00 10 48 RSP: 0018:ffa0000000cd7c30 EFLAGS: 00010246 RAX: 9e129be1950f0200 RBX: ff1100011b51582c RCX: ff1100011857cd80 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002 RBP: 0000000000000000 R08: ffd400000000000f R09: ff1100013e78cac0 R10: ffac800000cd7980 R11: ff1100013e12b1f0 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: ff1100011a99a2ec FS: 00007fbd7086f740(0000) GS:ff1100013fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200071c0 CR3: 0000000118556004 CR4: 0000000000771ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> proc_create_net_single+0x144/0x210 fs/proc/proc_net.c:220 bcm_connect+0x472/0x840 net/can/bcm.c:1673 __sys_connect_file net/socket.c:2049 [inline] __sys_connect+0x5d2/0x690 net/socket.c:2066 __do_sys_connect net/socket.c:2076 [inline] __se_sys_connect net/socket.c:2073 [inline] __x64_sys_connect+0x8f/0x100 net/socket.c:2073 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd9/0x1c0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7fbd708b0e5d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 9f 1b 00 f7 d8 64 89 01 48 RSP: 002b:00007fff8cd33f08 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fbd708b0e5d RDX: 0000000000000010 RSI: 0000000020000040 RDI: 0000000000000003 RBP: 0000000000000000 R08: 0000000000000040 R09: 0000000000000040 R10: 0000000000000040 R11: 0000000000000246 R12: 00007fff8cd34098 R13: 0000000000401280 R14: 0000000000406de8 R15: 00007fbd70ab9000 </TASK> remove_proc_entry: removing non-empty directory 'net/can-bcm', leaking at least '2456'

What

In the Linux kernel, the following vulnerability has been resolved: can: bcm: Remove proc entry when dev is unregistered. syzkaller reported a warning in bcm_connect() below. [0] The repro calls connect() to vxcan1, removes vxcan1, and calls connect() with ifindex == 0. Calling connect() for a BCM socket allocates a proc entry. Then, bcm_sk(sk)->bound is set to 1 to prevent further connect(). However, removing the bound device resets bcm_sk(sk)->bound to 0 in bcm_notify(). The 2nd connect() tries to allocate a proc entry with the same name and sets NULL to bcm_sk(sk)->bcm_proc_read, leaking the original proc entry. Since the proc entry is available only for connect()ed sockets, let's clean up the entry when the bound netdev is unregistered. [0]: proc_dir_entry 'can-bcm/2456' already registered WARNING: CPU: 1 PID: 394 at fs/proc/generic.c:376 proc_register+0x645/0x8f0 fs/proc/generic.c:375 Modules linked in: CPU: 1 PID: 394 Comm: syz-executor403 Not tainted 6.10.0-rc7-g852e42cc2dd4 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:proc_register+0x645/0x8f0 fs/proc/generic.c:375 Code: 00 00 00 00 00 48 85 ed 0f 85 97 02 00 00 4d 85 f6 0f 85 9f 02 00 00 48 c7 c7 9b cb cf 87 48 89 de 4c 89 fa e8 1c 6f eb fe 90 <0f> 0b 90 90 48 c7 c7 98 37 99 89 e8 cb 7e 22 05 bb 00 00 00 10 48 RSP: 0018:ffa0000000cd7c30 EFLAGS: 00010246 RAX: 9e129be1950f0200 RBX: ff1100011b51582c RCX: ff1100011857cd80 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002 RBP: 0000000000000000 R08: ffd400000000000f R09: ff1100013e78cac0 R10: ffac800000cd7980 R11: ff1100013e12b1f0 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: ff1100011a99a2ec FS: 00007fbd7086f740(0000) GS:ff1100013fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200071c0 CR3: 0000000118556004 CR4: 0000000000771ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> proc_create_net_single+0x144/0x210 fs/proc/proc_net.c:220 bcm_connect+0x472/0x840 net/can/bcm.c:1673 __sys_connect_file net/socket.c:2049 [inline] __sys_connect+0x5d2/0x690 net/socket.c:2066 __do_sys_connect net/socket.c:2076 [inline] __se_sys_connect net/socket.c:2073 [inline] __x64_sys_connect+0x8f/0x100 net/socket.c:2073 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd9/0x1c0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7fbd708b0e5d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 9f 1b 00 f7 d8 64 89 01 48 RSP: 002b:00007fff8cd33f08 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fbd708b0e5d RDX: 0000000000000010 RSI: 0000000020000040 RDI: 0000000000000003 RBP: 0000000000000000 R08: 0000000000000040 R09: 0000000000000040 R10: 0000000000000040 R11: 0000000000000246 R12: 00007fff8cd34098 R13: 0000000000401280 R14: 0000000000406de8 R15: 00007fbd70ab9000 </TASK> remove_proc_entry: removing non-empty directory 'net/can-bcm', leaking at least '2456'

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: can: bcm: Remove proc entry when dev is unregistered. syzkaller reported a warning in bcm_connect() below. [0] The repro calls connect() to vxcan1, removes vxcan1, and calls connect() with ifindex == 0. Calling connect() for a BCM socket allocates a proc entry. Then, bcm_sk(sk)->bound is set to 1 to prevent further connect(). However, removing the bound device resets bcm_sk(sk)->bound to 0 in bcm_notify(). The 2nd connect() tries to allocate a proc entry with the same name and sets NULL to bcm_sk(sk)->bcm_proc_read, leaking the original proc entry. Since the proc entry is available only for connect()ed sockets, let's clean up the entry when the bound netdev is unregistered. [0]: proc_dir_entry 'can-bcm/2456' already registered WARNING: CPU: 1 PID: 394 at fs/proc/generic.c:376 proc_register+0x645/0x8f0 fs/proc/generic.c:375 Modules linked in: CPU: 1 PID: 394 Comm: syz-executor403 Not tainted 6.10.0-rc7-g852e42cc2dd4 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:proc_register+0x645/0x8f0 fs/proc/generic.c:375 Code: 00 00 00 00 00 48 85 ed 0f 85 97 02 00 00 4d 85 f6 0f 85 9f 02 00 00 48 c7 c7 9b cb cf 87 48 89 de 4c 89 fa e8 1c 6f eb fe 90 <0f> 0b 90 90 48 c7 c7 98 37 99 89 e8 cb 7e 22 05 bb 00 00 00 10 48 RSP: 0018:ffa0000000cd7c30 EFLAGS: 00010246 RAX: 9e129be1950f0200 RBX: ff1100011b51582c RCX: ff1100011857cd80 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002 RBP: 0000000000000000 R08: ffd400000000000f R09: ff1100013e78cac0 R10: ffac800000cd7980 R11: ff1100013e12b1f0 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: ff1100011a99a2ec FS: 00007fbd7086f740(0000) GS:ff1100013fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200071c0 CR3: 0000000118556004 CR4: 0000000000771ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> proc_create_net_single+0x144/0x210 fs/proc/proc_net.c:220 bcm_connect+0x472/0x840 net/can/bcm.c:1673 __sys_connect_file net/socket.c:2049 [inline] __sys_connect+0x5d2/0x690 net/socket.c:2066 __do_sys_connect net/socket.c:2076 [inline] __se_sys_connect net/socket.c:2073 [inline] __x64_sys_connect+0x8f/0x100 net/socket.c:2073 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd9/0x1c0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7fbd708b0e5d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 9f 1b 00 f7 d8 64 89 01 48 RSP: 002b:00007fff8cd33f08 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fbd708b0e5d RDX: 0000000000000010 RSI: 0000000020000040 RDI: 0000000000000003 RBP: 0000000000000000 R08: 0000000000000040 R09: 0000000000000040 R10: 0000000000000040 R11: 0000000000000246 R12: 00007fff8cd34098 R13: 0000000000401280 R14: 0000000000406de8 R15: 00007fbd70ab9000 </TASK> remove_proc_entry: removing non-empty directory 'net/can-bcm', leaking at least '2456'

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

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

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

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

Official authority intelligence

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

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

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen 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-46747 Référence CVE CVE-2024-46750 https://www.cve.org/CVERecord?id=CVE-2024-46750 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46756 https://www.cve.org/CVERecord?id=CVE-2024-46756 Référence CVE CVE-2024-46757 https://www.cve.org/CVERecord?id=CVE-2024-46757 Référence CVE CVE-2024-46758 https://www.cve.org/CVERecord?id=CVE-2024-46758 Référence CVE CVE-2024-46759 https://www.cve.org/CVERecord?id=CVE-2024-46759 Référence CVE CVE-2024-46761 https://www.cve.org/CVERecord?id=CVE-2024-46761 Référence CVE CVE-2024-46763 https://www.cve.org/CVERecord?id=CVE-2024-46763 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46780 https://www.cve.org/CVERecord?id=CVE-2024-46780 Référence CVE CVE-2024-46781 https://www.cve.org/CVERecord?id=CVE-2024-46781 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46783 https://www.cve.org/CVERecord?id=CVE-2024-46783 Référence CVE CVE-2024-46791 https://www.cve.org/CVERecord?id=CVE-2024-46791 Référence CVE CVE-2024-46798 https://www.cve.org/CVERecord?id=CVE-2024-46798 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26837 Référence CVE CVE-2024-26915 https://www.cve.org/CVERecord?id=CVE-2024-26915 Référence CVE CVE-2024-26928 https://www.cve.org/CVERecord?id=CVE-2024-26928 Référence CVE CVE-2024-26974 https://www.cve.org/CVERecord?id=CVE-2024-26974 Référence CVE CVE-2024-26996 https://www.cve.org/CVERecord?id=CVE-2024-26996 Référence CVE CVE-2024-35864 https://www.cve.org/CVERecord?id=CVE-2024-35864 Référence CVE CVE-2024-35958 https://www.cve.org/CVERecord?id=CVE-2024-35958 Référence CVE CVE-2024-36015 https://www.cve.org/CVERecord?id=CVE-2024-36015 Référence CVE CVE-2024-36934 https://www.cve.org/CVERecord?id=CVE-2024-36934 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46780 https://www.cve.org/CVERecord?id=CVE-2024-46780 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=CVE-2024-46826 Référence CVE CVE-2024-49925 https://www.cve.org/CVERecord?id=CVE-2024-49925 Référence CVE CVE-2024-49944 https://www.cve.org/CVERecord?id=CVE-2024-49944 Référence CVE CVE-2024-49974 https://www.cve.org/CVERecord?id=CVE-2024-49974 Référence CVE CVE-2024-50237 https://www.cve.org/CVERecord?id=CVE-2024-50237 Référence CVE CVE-2024-50248 https://www.cve.org/CVERecord?id=CVE-2024-50248 Référence CVE CVE-2024-50256 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42133 Référence CVE CVE-2024-42232 https://www.cve.org/CVERecord?id=CVE-2024-42232 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-43913 https://www.cve.org/CVERecord?id=CVE-2024-43913 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-45828 https://www.cve.org/CVERecord?id=CVE-2024-45828 Référence CVE CVE-2024-46680 https://www.cve.org/CVERecord?id=CVE-2024-46680 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-46896 https://www.cve.org/CVERecord?id=CVE-2024-46896 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42145 Référence CVE CVE-2024-42229 https://www.cve.org/CVERecord?id=CVE-2024-42229 Référence CVE CVE-2024-42253 https://www.cve.org/CVERecord?id=CVE-2024-42253 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44958 https://www.cve.org/CVERecord?id=CVE-2024-44958 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-46724 https://www.cve.org/CVERecord?id=CVE-2024-46724 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-46802 https://www.cve.org/CVERecord?id=CVE-2024-46802 Référence CVE CVE-2024-46809 https://www.cve.org/CVERecord?id=CVE-2024-46809 Référence CVE CVE-2024-46813 https://www.cve.org/CVERecord?id=CVE-2024-46813 Référence CVE CVE-2024-46816 https://www.cve.org/CVERecord?id=CVE-2024-46816 Référence CVE CVE-2024-46818 https://www.cve.org/CVERecord?id=CVE-2024-46818 Référence CVE CVE-2024-46826 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46760 Référence CVE CVE-2024-46761 https://www.cve.org/CVERecord?id=CVE-2024-46761 Référence CVE CVE-2024-46762 https://www.cve.org/CVERecord?id=CVE-2024-46762 Référence CVE CVE-2024-46763 https://www.cve.org/CVERecord?id=CVE-2024-46763 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46766 https://www.cve.org/CVERecord?id=CVE-2024-46766 Référence CVE CVE-2024-46767 https://www.cve.org/CVERecord?id=CVE-2024-46767 Référence CVE CVE-2024-46768 https://www.cve.org/CVERecord?id=CVE-2024-46768 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46772 https://www.cve.org/CVERecord?id=CVE-2024-46772 Référence CVE CVE-2024-46773 https://www.cve.org/CVERecord?id=CVE-2024-46773 Référence CVE CVE-2024-46774 https://www.cve.org/CVERecord?id=CVE-2024-46774 Référence CVE CVE-2024-46775 https://www.cve.org/CVERecord?id=CVE-2024-46775 Référence CVE CVE-2024-46776 https://www.cve.org/CVERecord?id=CVE-2024-46776 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46778 https://www.cve.org/CVERecord?id=CVE-2024-46778 Référence CVE CVE-2024-46779 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-46752 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46756 https://www.cve.org/CVERecord?id=CVE-2024-46756 Référence CVE CVE-2024-46757 https://www.cve.org/CVERecord?id=CVE-2024-46757 Référence CVE CVE-2024-46758 https://www.cve.org/CVERecord?id=CVE-2024-46758 Référence CVE CVE-2024-46759 https://www.cve.org/CVERecord?id=CVE-2024-46759 Référence CVE CVE-2024-46761 https://www.cve.org/CVERecord?id=CVE-2024-46761 Référence CVE CVE-2024-46763 https://www.cve.org/CVERecord?id=CVE-2024-46763 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46773 https://www.cve.org/CVERecord?id=CVE-2024-46773 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46780 https://www.cve.org/CVERecord?id=CVE-2024-46780 Référence CVE CVE-2024-46781 https://www.cve.org/CVERecord?id=CVE-2024-46781 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46783 https://www.cve.org/CVERecord?id=CVE-2024-46783 Référence CVE CVE-2024-46784 https://www.cve.org/CVERecord?id=CVE-2024-46784 Référence CVE CVE-2024-46791 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46680 Référence CVE CVE-2024-46681 https://www.cve.org/CVERecord?id=CVE-2024-46681 Référence CVE CVE-2024-46716 https://www.cve.org/CVERecord?id=CVE-2024-46716 Référence CVE CVE-2024-46719 https://www.cve.org/CVERecord?id=CVE-2024-46719 Référence CVE CVE-2024-46721 https://www.cve.org/CVERecord?id=CVE-2024-46721 Référence CVE CVE-2024-46754 https://www.cve.org/CVERecord?id=CVE-2024-46754 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46766 https://www.cve.org/CVERecord?id=CVE-2024-46766 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46775 https://www.cve.org/CVERecord?id=CVE-2024-46775 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46788 https://www.cve.org/CVERecord?id=CVE-2024-46788 Référence CVE CVE-2024-46797 https://www.cve.org/CVERecord?id=CVE-2024-46797 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-46802 https://www.cve.org/CVERecord?id=CVE-2024-46802 Référence CVE CVE-2024-46803 https://www.cve.org/CVERecord?id=CVE-2024-46803 Référence CVE CVE-2024-46804 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46760 Référence CVE CVE-2024-46761 https://www.cve.org/CVERecord?id=CVE-2024-46761 Référence CVE CVE-2024-46762 https://www.cve.org/CVERecord?id=CVE-2024-46762 Référence CVE CVE-2024-46763 https://www.cve.org/CVERecord?id=CVE-2024-46763 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46766 https://www.cve.org/CVERecord?id=CVE-2024-46766 Référence CVE CVE-2024-46767 https://www.cve.org/CVERecord?id=CVE-2024-46767 Référence CVE CVE-2024-46768 https://www.cve.org/CVERecord?id=CVE-2024-46768 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46772 https://www.cve.org/CVERecord?id=CVE-2024-46772 Référence CVE CVE-2024-46773 https://www.cve.org/CVERecord?id=CVE-2024-46773 Référence CVE CVE-2024-46774 https://www.cve.org/CVERecord?id=CVE-2024-46774 Référence CVE CVE-2024-46775 https://www.cve.org/CVERecord?id=CVE-2024-46775 Référence CVE CVE-2024-46776 https://www.cve.org/CVERecord?id=CVE-2024-46776 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46778 https://www.cve.org/CVERecord?id=CVE-2024-46778 Référence CVE CVE-2024-46779 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46750 Référence CVE CVE-2024-46752 https://www.cve.org/CVERecord?id=CVE-2024-46752 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46756 https://www.cve.org/CVERecord?id=CVE-2024-46756 Référence CVE CVE-2024-46757 https://www.cve.org/CVERecord?id=CVE-2024-46757 Référence CVE CVE-2024-46758 https://www.cve.org/CVERecord?id=CVE-2024-46758 Référence CVE CVE-2024-46759 https://www.cve.org/CVERecord?id=CVE-2024-46759 Référence CVE CVE-2024-46761 https://www.cve.org/CVERecord?id=CVE-2024-46761 Référence CVE CVE-2024-46763 https://www.cve.org/CVERecord?id=CVE-2024-46763 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46780 https://www.cve.org/CVERecord?id=CVE-2024-46780 Référence CVE CVE-2024-46781 https://www.cve.org/CVERecord?id=CVE-2024-46781 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46783 https://www.cve.org/CVERecord?id=CVE-2024-46783 Référence CVE CVE-2024-46791 https://www.cve.org/CVERecord?id=CVE-2024-46791 Référence CVE CVE-2024-46795 https://www.cve.org/CVERecord?id=CVE-2024-46795 Référence CVE CVE-2024-46798 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46750 Référence CVE CVE-2024-46752 https://www.cve.org/CVERecord?id=CVE-2024-46752 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46756 https://www.cve.org/CVERecord?id=CVE-2024-46756 Référence CVE CVE-2024-46757 https://www.cve.org/CVERecord?id=CVE-2024-46757 Référence CVE CVE-2024-46758 https://www.cve.org/CVERecord?id=CVE-2024-46758 Référence CVE CVE-2024-46759 https://www.cve.org/CVERecord?id=CVE-2024-46759 Référence CVE CVE-2024-46761 https://www.cve.org/CVERecord?id=CVE-2024-46761 Référence CVE CVE-2024-46763 https://www.cve.org/CVERecord?id=CVE-2024-46763 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46780 https://www.cve.org/CVERecord?id=CVE-2024-46780 Référence CVE CVE-2024-46781 https://www.cve.org/CVERecord?id=CVE-2024-46781 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46783 https://www.cve.org/CVERecord?id=CVE-2024-46783 Référence CVE CVE-2024-46791 https://www.cve.org/CVERecord?id=CVE-2024-46791 Référence CVE CVE-2024-46795 https://www.cve.org/CVERecord?id=CVE-2024-46795 Référence CVE CVE-2024-46798 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46745 Référence CVE CVE-2024-46747 https://www.cve.org/CVERecord?id=CVE-2024-46747 Référence CVE CVE-2024-46750 https://www.cve.org/CVERecord?id=CVE-2024-46750 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46756 https://www.cve.org/CVERecord?id=CVE-2024-46756 Référence CVE CVE-2024-46757 https://www.cve.org/CVERecord?id=CVE-2024-46757 Référence CVE CVE-2024-46758 https://www.cve.org/CVERecord?id=CVE-2024-46758 Référence CVE CVE-2024-46759 https://www.cve.org/CVERecord?id=CVE-2024-46759 Référence CVE CVE-2024-46761 https://www.cve.org/CVERecord?id=CVE-2024-46761 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46780 https://www.cve.org/CVERecord?id=CVE-2024-46780 Référence CVE CVE-2024-46781 https://www.cve.org/CVERecord?id=CVE-2024-46781 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46783 https://www.cve.org/CVERecord?id=CVE-2024-46783 Référence CVE CVE-2024-46798 https://www.cve.org/CVERecord?id=CVE-2024-46798 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-46815 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46745 Référence CVE CVE-2024-46747 https://www.cve.org/CVERecord?id=CVE-2024-46747 Référence CVE CVE-2024-46750 https://www.cve.org/CVERecord?id=CVE-2024-46750 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46756 https://www.cve.org/CVERecord?id=CVE-2024-46756 Référence CVE CVE-2024-46757 https://www.cve.org/CVERecord?id=CVE-2024-46757 Référence CVE CVE-2024-46758 https://www.cve.org/CVERecord?id=CVE-2024-46758 Référence CVE CVE-2024-46759 https://www.cve.org/CVERecord?id=CVE-2024-46759 Référence CVE CVE-2024-46763 https://www.cve.org/CVERecord?id=CVE-2024-46763 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46780 https://www.cve.org/CVERecord?id=CVE-2024-46780 Référence CVE CVE-2024-46781 https://www.cve.org/CVERecord?id=CVE-2024-46781 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46783 https://www.cve.org/CVERecord?id=CVE-2024-46783 Référence CVE CVE-2024-46791 https://www.cve.org/CVERecord?id=CVE-2024-46791 Référence CVE CVE-2024-46798 https://www.cve.org/CVERecord?id=CVE-2024-46798 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46755 Référence CVE CVE-2024-46756 https://www.cve.org/CVERecord?id=CVE-2024-46756 Référence CVE CVE-2024-46757 https://www.cve.org/CVERecord?id=CVE-2024-46757 Référence CVE CVE-2024-46758 https://www.cve.org/CVERecord?id=CVE-2024-46758 Référence CVE CVE-2024-46759 https://www.cve.org/CVERecord?id=CVE-2024-46759 Référence CVE CVE-2024-46760 https://www.cve.org/CVERecord?id=CVE-2024-46760 Référence CVE CVE-2024-46761 https://www.cve.org/CVERecord?id=CVE-2024-46761 Référence CVE CVE-2024-46767 https://www.cve.org/CVERecord?id=CVE-2024-46767 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46772 https://www.cve.org/CVERecord?id=CVE-2024-46772 Référence CVE CVE-2024-46773 https://www.cve.org/CVERecord?id=CVE-2024-46773 Référence CVE CVE-2024-46774 https://www.cve.org/CVERecord?id=CVE-2024-46774 Référence CVE CVE-2024-46775 https://www.cve.org/CVERecord?id=CVE-2024-46775 Référence CVE CVE-2024-46776 https://www.cve.org/CVERecord?id=CVE-2024-46776 Référence CVE CVE-2024-46778 https://www.cve.org/CVERecord?id=CVE-2024-46778 Référence CVE CVE-2024-46780 https://www.cve.org/CVERecord?id=CVE-2024-46780 Référence CVE CVE-2024-46781 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46752 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46756 https://www.cve.org/CVERecord?id=CVE-2024-46756 Référence CVE CVE-2024-46757 https://www.cve.org/CVERecord?id=CVE-2024-46757 Référence CVE CVE-2024-46758 https://www.cve.org/CVERecord?id=CVE-2024-46758 Référence CVE CVE-2024-46759 https://www.cve.org/CVERecord?id=CVE-2024-46759 Référence CVE CVE-2024-46761 https://www.cve.org/CVERecord?id=CVE-2024-46761 Référence CVE CVE-2024-46763 https://www.cve.org/CVERecord?id=CVE-2024-46763 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46773 https://www.cve.org/CVERecord?id=CVE-2024-46773 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46780 https://www.cve.org/CVERecord?id=CVE-2024-46780 Référence CVE CVE-2024-46781 https://www.cve.org/CVERecord?id=CVE-2024-46781 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46783 https://www.cve.org/CVERecord?id=CVE-2024-46783 Référence CVE CVE-2024-46784 https://www.cve.org/CVERecord?id=CVE-2024-46784 Référence CVE CVE-2024-46791 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 XC-300/XR-300/XC-400/XR-500WG/XR-500 family; SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Fixed
< 2.6.25; 4.19.322 ≤ 4.19.*; 5.4.284 ≤ 5.4.*; 5.10.226 ≤ 5.10.*; 5.15.167 ≤ 5.15.*; 6.1.110 ≤ 6.1.*; 6.6.51 ≤ 6.6.*; 6.10.10 ≤ 6.10.*
Action
Update to V3.2 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 18 Sept 2024 · Last source change 5 Aug 2026, 11:38 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-42032
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.

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-42032↗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-46771 · cve.blacktree.nl