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

f2fs: Require FMODE_WRITE for atomic write ioctls

Linux · Linux

7.1HighCVSS 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.

17 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-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical 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.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical 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-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical 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
Inf2fs: Require FMODE_WRITE for atomic write ioctls. The F2FS ioctls for starting and committing atomic writes check for inode_owner_or_capable(), but this does not give LSMs like SELinux or Landlock an opportunity to deny the write access - if the caller's FSUID matches the inode's UID, inode_owner_or_capable() immediately returns true.
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-42657

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: f2fs: Require FMODE_WRITE for atomic write ioctls The F2FS ioctls for starting and committing atomic writes check for inode_owner_or_capable(), but this does not give LSMs like SELinux or Landlock an opportunity to deny the write access - if the caller's FSUID matches the inode's UID, inode_owner_or_capable() immediately returns true. There are scenarios where LSMs want to deny a process the ability to write particular files, even files that the FSUID of the process owns; but this can currently partially be bypassed using atomic write ioctls in two ways: - F2FS_IOC_START_ATOMIC_REPLACE + F2FS_IOC_COMMIT_ATOMIC_WRITE can truncate an inode to size 0 - F2FS_IOC_START_ATOMIC_WRITE + F2FS_IOC_ABORT_ATOMIC_WRITE can revert changes another process concurrently made to a file Fix it by requiring FMODE_WRITE for these operations, just like for F2FS_IOC_MOVE_RANGE. Since any legitimate caller should only be using these ioctls when intending to write into the file, that seems unlikely to break anything.

What

In the Linux kernel, the following vulnerability has been resolved: f2fs: Require FMODE_WRITE for atomic write ioctls The F2FS ioctls for starting and committing atomic writes check for inode_owner_or_capable(), but this does not give LSMs like SELinux or Landlock an opportunity to deny the write access - if the caller's FSUID matches the inode's UID, inode_owner_or_capable() immediately returns true. There are scenarios where LSMs want to deny a process the ability to write particular files, even files that the FSUID of the process owns; but this can currently partially be bypassed using atomic write ioctls in two ways: - F2FS_IOC_START_ATOMIC_REPLACE + F2FS_IOC_COMMIT_ATOMIC_WRITE can truncate an inode to size 0 - F2FS_IOC_START_ATOMIC_WRITE + F2FS_IOC_ABORT_ATOMIC_WRITE can revert changes another process concurrently made to a file Fix it by requiring FMODE_WRITE for these operations, just like for F2FS_IOC_MOVE_RANGE. Since any legitimate caller should only be using these ioctls when intending to write into the file, that seems unlikely to break anything.

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: f2fs: Require FMODE_WRITE for atomic write ioctls The F2FS ioctls for starting and committing atomic writes check for inode_owner_or_capable(), but this does not give LSMs like SELinux or Landlock an opportunity to deny the write access - if the caller's FSUID matches the inode's UID, inode_owner_or_capable() immediately returns true. There are scenarios where LSMs want to deny a process the ability to write particular files, even files that the FSUID of the process owns; but this can currently partially be bypassed using atomic write ioctls in two ways: - F2FS_IOC_START_ATOMIC_REPLACE + F2FS_IOC_COMMIT_ATOMIC_WRITE can truncate an inode to size 0 - F2FS_IOC_START_ATOMIC_WRITE + F2FS_IOC_ABORT_ATOMIC_WRITE can revert changes another process concurrently made to a file Fix it by requiring FMODE_WRITE for these operations, just like for F2FS_IOC_MOVE_RANGE. Since any legitimate caller should only be using these ioctls when intending to write into the file, that seems unlikely to break anything.

Why

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

How

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

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I: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.CNoneConfidentiality impact: No direct loss is represented by this metric.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-3251Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..

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

d?id=CVE-2024-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=CVE-2024-47710 Référence CVE CVE-2024-47712 https://www.cve.org/CVERecord?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=CVE-2024-47713 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47756 https://www.cve.org/CVERecord?id=CVE-2024-47756 Référence CVE CVE-2024-47757 https://www.cve.org/CVERecord?id=CVE-2024-47757 Référence CVE CVE-2024-48881 https://www.cve.org/CVERecord?id=CVE-2024-48881 Référence CVE CVE-2024-49851 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47723 Référence CVE CVE-2024-47726 https://www.cve.org/CVERecord?id=CVE-2024-47726 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47730 https://www.cve.org/CVERecord?id=CVE-2024-47730 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47756 https://www.cve.org/CVERecord?id=CVE-2024-47756 Référence CVE CVE-2024-47757 https://www.cve.org/CVERecord?id=CVE-2024-47757 Référence CVE CVE-2024-47794 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47730 Référence CVE CVE-2024-47731 https://www.cve.org/CVERecord?id=CVE-2024-47731 Référence CVE CVE-2024-47732 https://www.cve.org/CVERecord?id=CVE-2024-47732 Référence CVE CVE-2024-47733 https://www.cve.org/CVERecord?id=CVE-2024-47733 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47741 https://www.cve.org/CVERecord?id=CVE-2024-47741 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47743 https://www.cve.org/CVERecord?id=CVE-2024-47743 Référence CVE CVE-2024-47744 https://www.cve.org/CVERecord?id=CVE-2024-47744 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47731 Référence CVE CVE-2024-47732 https://www.cve.org/CVERecord?id=CVE-2024-47732 Référence CVE CVE-2024-47733 https://www.cve.org/CVERecord?id=CVE-2024-47733 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47736 https://www.cve.org/CVERecord?id=CVE-2024-47736 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47741 https://www.cve.org/CVERecord?id=CVE-2024-47741 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47743 https://www.cve.org/CVERecord?id=CVE-2024-47743 Référence CVE CVE-2024-47744 https://www.cve.org/CVERecord?id=CVE-2024-47744 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47746 https://www.cve.org/CVERecord?id=CVE-2024-47746 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47709 Référence CVE CVE-2024-47710 https://www.cve.org/CVERecord?id=CVE-2024-47710 Référence CVE CVE-2024-47712 https://www.cve.org/CVERecord?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=CVE-2024-47713 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47756 https://www.cve.org/CVERecord?id=CVE-2024-47756 Référence CVE CVE-2024-47757 https://www.cve.org/CVERecord?id=CVE-2024-47757 Référence CVE CVE-2024-48881 https://www.cve.org/CVERecord?id=CVE-2024-48881 Référence CVE CVE-2024-49571 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47730 Référence CVE CVE-2024-47731 https://www.cve.org/CVERecord?id=CVE-2024-47731 Référence CVE CVE-2024-47732 https://www.cve.org/CVERecord?id=CVE-2024-47732 Référence CVE CVE-2024-47733 https://www.cve.org/CVERecord?id=CVE-2024-47733 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47741 https://www.cve.org/CVERecord?id=CVE-2024-47741 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47743 https://www.cve.org/CVERecord?id=CVE-2024-47743 Référence CVE CVE-2024-47744 https://www.cve.org/CVERecord?id=CVE-2024-47744 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47731 Référence CVE CVE-2024-47732 https://www.cve.org/CVERecord?id=CVE-2024-47732 Référence CVE CVE-2024-47733 https://www.cve.org/CVERecord?id=CVE-2024-47733 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47736 https://www.cve.org/CVERecord?id=CVE-2024-47736 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47741 https://www.cve.org/CVERecord?id=CVE-2024-47741 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47743 https://www.cve.org/CVERecord?id=CVE-2024-47743 Référence CVE CVE-2024-47744 https://www.cve.org/CVERecord?id=CVE-2024-47744 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=CVE-2024-47745 Référence CVE CVE-2024-47746 https://www.cve.org/CVERecord?id=CVE-2024-47746 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=CVE-2024-47713 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47720 https://www.cve.org/CVERecord?id=CVE-2024-47720 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47756 https://www.cve.org/CVERecord?id=CVE-2024-47756 Référence CVE CVE-2024-47757 https://www.cve.org/CVERecord?id=CVE-2024-47757 Référence CVE CVE-2024-49851 https://www.cve.org/CVERecord?id=CVE-2024-49851 Référence CVE CVE-2024-49852 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-47713 Référence CVE CVE-2024-47715 https://www.cve.org/CVERecord?id=CVE-2024-47715 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47720 https://www.cve.org/CVERecord?id=CVE-2024-47720 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47756 https://www.cve.org/CVERecord?id=CVE-2024-47756 Référence CVE CVE-2024-47757 https://www.cve.org/CVERecord?id=CVE-2024-47757 Référence CVE CVE-2024-49851 https://www.cve.org/CVERecord?id=CVE-2024-49851 Référence CVE CVE-2024-49852 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-47727 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47730 https://www.cve.org/CVERecord?id=CVE-2024-47730 Référence CVE CVE-2024-47731 https://www.cve.org/CVERecord?id=CVE-2024-47731 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47743 https://www.cve.org/CVERecord?id=CVE-2024-47743 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47750 https://www.cve.org/CVERecord?id=CVE-2024-47750 Référence CVE CVE-2024-47751 https://www.cve.org/CVERecord?id=CVE-2024-47751 Référence CVE CVE-2024-47756 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=CVE-2024-47713 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47720 https://www.cve.org/CVERecord?id=CVE-2024-47720 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47756 https://www.cve.org/CVERecord?id=CVE-2024-47756 Référence CVE CVE-2024-47757 https://www.cve.org/CVERecord?id=CVE-2024-47757 Référence CVE CVE-2024-49851 https://www.cve.org/CVERecord?id=CVE-2024-49851 Référence CVE CVE-2024-49852 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47712 Référence CVE CVE-2024-47713 https://www.cve.org/CVERecord?id=CVE-2024-47713 Référence CVE CVE-2024-47718 https://www.cve.org/CVERecord?id=CVE-2024-47718 Référence CVE CVE-2024-47720 https://www.cve.org/CVERecord?id=CVE-2024-47720 Référence CVE CVE-2024-47723 https://www.cve.org/CVERecord?id=CVE-2024-47723 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-47735 https://www.cve.org/CVERecord?id=CVE-2024-47735 Référence CVE CVE-2024-47737 https://www.cve.org/CVERecord?id=CVE-2024-47737 Référence CVE CVE-2024-47739 https://www.cve.org/CVERecord?id=CVE-2024-47739 Référence CVE CVE-2024-47740 https://www.cve.org/CVERecord?id=CVE-2024-47740 Référence CVE CVE-2024-47742 https://www.cve.org/CVERecord?id=CVE-2024-47742 Référence CVE CVE-2024-47747 https://www.cve.org/CVERecord?id=CVE-2024-47747 Référence CVE CVE-2024-47748 https://www.cve.org/CVERecord?id=CVE-2024-47748 Référence CVE CVE-2024-47749 https://www.cve.org/CVERecord?id=CVE-2024-47749 Référence CVE CVE-2024-47756 https://www.cve.org/CVERecord?id=CVE-2024-47756 Référence CVE CVE-2024-47757 https://www.cve.org/CVERecord?id=CVE-2024-47757 Référence CVE CVE-2024-49851 https://www.cve.org/CVERecord?id=CVE-2024-49851 Référence CVE CVE-2024-49852 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
< 3.18; 4.19.323 ≤ 4.19.*; 5.4.285 ≤ 5.4.*; 5.10.227 ≤ 5.10.*; 5.15.168 ≤ 5.15.*; 6.1.113 ≤ 6.1.*; 6.6.54 ≤ 6.6.*; 6.10.13 ≤ 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 21 Oct 2024 · Last source change 5 Aug 2026, 11:39 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-42657
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
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-47740 · cve.blacktree.nl