BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-53187High confidence

io_uring: check for overflows in io_pin_pages

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 30 Oct 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.28% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

23 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.3-1Debian Security Tracker ↗Source updated 4 Nov 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 4 Nov 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.3-1Debian Security Tracker ↗Source updated 4 Nov 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.3-1Debian Security Tracker ↗Source updated 4 Nov 2026
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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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 Ubuntu Security ↗Source updated 4 Nov 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
CVE-2024-53187 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: io_uring: check for overflows in io_pin_pages
199 known not affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
In the Linux kernel, the following vulnerability has been resolved: io_uring: check for overflows in io_pin_pages WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144 CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0 Call Trace: __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183 io_rings_map io_uring/io_uring.c:2611 [inline] io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470 io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692 io_uring_setup io_uring/io_uring.c:3781 [inline] ... io_pin_pages()'s uaddr parameter came directly from the user and can be garbage. Don't just add size to it as it can overflow.
Remediation
No remediation text is recorded.
CVE-2024-53187 · CSAF 2.0 · revision 67 · interimSUSE Product Security TeamCVE-2024-53187
154 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP5
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
Summary
In the Linux kernel, the following vulnerability has been resolved: io_uring: check for overflows in io_pin_pages WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144 CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0 Call Trace: __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183 io_rings_map io_uring/io_uring.c:2611 [inline] io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470 io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692 io_uring_setup io_uring/io_uring.c:3781 [inline] ... io_pin_pages()'s uaddr parameter came directly from the user and can be garbage. Don't just add size to it as it can overflow.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: io_uring: check for overflows in io_pin_pages WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144 CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0 Call Trace: <TASK> __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183 io_rings_map io_uring/io_uring.c:2611 [inline] io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470 io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692 io_uring_setup io_uring/io_uring.c:3781 [inline] ... </TASK> io_pin_pages()'s uaddr parameter came directly from the user and can be garbage. Don't just add size to it as it can overflow.

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
5.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: io_uring: check for overflows in io_pin_pages WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144 CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0 Call Trace: <TASK> __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183 io_rings_map io_uring/io_uring.c:2611 [inline] io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470 io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692 io_uring_setup io_uring/io_uring.c:3781 [inline] ... </TASK> io_pin_pages()'s uaddr parameter came directly from the user and can be garbage. Don't just add size to it as it can overflow.

What

In the Linux kernel, the following vulnerability has been resolved: io_uring: check for overflows in io_pin_pages WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144 CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0 Call Trace: <TASK> __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183 io_rings_map io_uring/io_uring.c:2611 [inline] io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470 io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692 io_uring_setup io_uring/io_uring.c:3781 [inline] ... </TASK> io_pin_pages()'s uaddr parameter came directly from the user and can be garbage. Don't just add size to it as it can overflow.

Why

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

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: io_uring: check for overflows in io_pin_pages WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144 CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0 Call Trace: <TASK> __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183 io_rings_map io_uring/io_uring.c:2611 [inline] io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470 io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692 io_uring_setup io_uring/io_uring.c:3781 [inline] ... </TASK> io_pin_pages()'s uaddr parameter came directly from the user and can be garbage. Don't just add size to it as it can overflow.

Why

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

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 → Integer Overflow or Wraparound → 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-190 ↗

CWE-190: Integer Overflow or Wraparound. The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

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

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

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

Official authority intelligence

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

ENISA EUVD · EUVD-2024-51859Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: io_uring: check for overflows in io_pin_pages WARNING: CPU: 0 PID: 5834 at io_uring/memmap.c:144 io_pin_pages+0x149/0x180 io_uring/memmap.c:144 CPU: 0 UID: 0 PID: 5834 Comm: syz-executor825 Not tainted 6.12.0-next-20241118-syzkaller #0 Call Trace: <TASK> __io_uaddr_map+0xfb/0x2d0 io_uring/memmap.c:183 io_rings_map io_uring/io_uring.c:2611 [inline] io_allocate_scq_urings+0x1c0/0x650 io_uring/io_uring.c:3470 io_uring_create+0x5b5/0xc00 io_uring/io_uring.c:3692 io_uring_setup io_uring/io_uring.c:3781 [inline] ... </TASK> io_pin_pages()'s uaddr parameter came directly from the user and can be garbage. Don't just add size to it as it can overflow.

Official EUVD record ↗
BSI · German · WID-SEC-2024-3762Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250101Security Bulletin 01 Jan 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 01 Jan 2025, published on 1 January 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1595Avis du CERT-FR

d?id=CVE-2024-53091 Référence CVE CVE-2024-53094 https://www.cve.org/CVERecord?id=CVE-2024-53094 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53114 https://www.cve.org/CVERecord?id=CVE-2024-53114 Référence CVE CVE-2024-53134 https://www.cve.org/CVERecord?id=CVE-2024-53134 Référence CVE CVE-2024-53147 https://www.cve.org/CVERecord?id=CVE-2024-53147 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53179 https://www.cve.org/CVERecord?id=CVE-2024-53179 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53195 https://www.cve.org/CVERecord?id=CVE-2024-53195 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-56538 https://www.cve.org/CVERecord?id=CVE-2024-56538 Référence CVE CVE-2024-56565 https://www.cve.org/CVERecord?id=CVE-2024-56565 Référence CVE CVE-2024-56566 https://www.cve.org/CVERecord?id=CVE-2024-56566 Référence CVE CVE-2024-56583 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1537Avis du CERT-FR

d?id=CVE-2023-54125 Référence CVE CVE-2023-54271 https://www.cve.org/CVERecord?id=CVE-2023-54271 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-41062 https://www.cve.org/CVERecord?id=CVE-2024-41062 Référence CVE CVE-2024-46754 https://www.cve.org/CVERecord?id=CVE-2024-46754 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-52560 https://www.cve.org/CVERecord?id=CVE-2024-52560 Référence CVE CVE-2024-53056 https://www.cve.org/CVERecord?id=CVE-2024-53056 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53194 https://www.cve.org/CVERecord?id=CVE-2024-53194 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-56552 https://www.cve.org/CVERecord?id=CVE-2024-56552 Référence CVE CVE-2024-56570 https://www.cve.org/CVERecord?id=CVE-2024-56570 Référence CVE CVE-2024-56616 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1469Avis du CERT-FR

d?id=CVE-2023-53231 Référence CVE CVE-2023-53320 https://www.cve.org/CVERecord?id=CVE-2023-53320 Référence CVE CVE-2023-53707 https://www.cve.org/CVERecord?id=CVE-2023-53707 Référence CVE CVE-2023-54125 https://www.cve.org/CVERecord?id=CVE-2023-54125 Référence CVE CVE-2023-54271 https://www.cve.org/CVERecord?id=CVE-2023-54271 Référence CVE CVE-2024-41062 https://www.cve.org/CVERecord?id=CVE-2024-41062 Référence CVE CVE-2024-46754 https://www.cve.org/CVERecord?id=CVE-2024-46754 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-56763 https://www.cve.org/CVERecord?id=CVE-2024-56763 Référence CVE CVE-2024-57945 https://www.cve.org/CVERecord?id=CVE-2024-57945 Référence CVE CVE-2024-57982 https://www.cve.org/CVERecord?id=CVE-2024-57982 Référence CVE CVE-2024-57999 https://www.cve.org/CVERecord?id=CVE-2024-57999 Référence CVE CVE-2024-58094 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1333Avis du CERT-FR

d?id=CVE-2022-49111 Référence CVE CVE-2022-49114 https://www.cve.org/CVERecord?id=CVE-2022-49114 Référence CVE CVE-2022-49149 https://www.cve.org/CVERecord?id=CVE-2022-49149 Référence CVE CVE-2022-49170 https://www.cve.org/CVERecord?id=CVE-2022-49170 Référence CVE CVE-2022-49182 https://www.cve.org/CVERecord?id=CVE-2022-49182 Référence CVE CVE-2022-49201 https://www.cve.org/CVERecord?id=CVE-2022-49201 Référence CVE CVE-2023-20585 https://www.cve.org/CVERecord?id=CVE-2023-20585 Référence CVE CVE-2023-54125 https://www.cve.org/CVERecord?id=CVE-2023-54125 Référence CVE CVE-2023-54271 https://www.cve.org/CVERecord?id=CVE-2023-54271 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53194 https://www.cve.org/CVERecord?id=CVE-2024-53194 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53214 https://www.cve.org/CVERecord?id=CVE-2024-53214 Référence CVE CVE-2024-56552 https://www.cve.org/CVERecord?id=CVE-2024-56552 Référence CVE CVE-2024-56570 https://www.cve.org/CVERecord?id=CVE-2024-56570 Référence CVE CVE-2024-56763 https://www.cve.org/CVERecord?id=CVE-2024-56763 Référence CVE CVE-2024-56779 https://www.cve.org/CVERecord?id=CVE-2024-56779 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-53095 Référence CVE CVE-2024-53098 https://www.cve.org/CVERecord?id=CVE-2024-53098 Référence CVE CVE-2024-53133 https://www.cve.org/CVERecord?id=CVE-2024-53133 Référence CVE CVE-2024-53147 https://www.cve.org/CVERecord?id=CVE-2024-53147 Référence CVE CVE-2024-53175 https://www.cve.org/CVERecord?id=CVE-2024-53175 Référence CVE CVE-2024-53176 https://www.cve.org/CVERecord?id=CVE-2024-53176 Référence CVE CVE-2024-53177 https://www.cve.org/CVERecord?id=CVE-2024-53177 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53179 https://www.cve.org/CVERecord?id=CVE-2024-53179 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53190 https://www.cve.org/CVERecord?id=CVE-2024-53190 Référence CVE CVE-2024-53195 https://www.cve.org/CVERecord?id=CVE-2024-53195 Référence CVE CVE-2024-53196 https://www.cve.org/CVERecord?id=CVE-2024-53196 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53219 https://www.cve.org/CVERecord?id=CVE-2024-53219 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-53095 Référence CVE CVE-2024-53098 https://www.cve.org/CVERecord?id=CVE-2024-53098 Référence CVE CVE-2024-53133 https://www.cve.org/CVERecord?id=CVE-2024-53133 Référence CVE CVE-2024-53147 https://www.cve.org/CVERecord?id=CVE-2024-53147 Référence CVE CVE-2024-53175 https://www.cve.org/CVERecord?id=CVE-2024-53175 Référence CVE CVE-2024-53176 https://www.cve.org/CVERecord?id=CVE-2024-53176 Référence CVE CVE-2024-53177 https://www.cve.org/CVERecord?id=CVE-2024-53177 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53179 https://www.cve.org/CVERecord?id=CVE-2024-53179 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53190 https://www.cve.org/CVERecord?id=CVE-2024-53190 Référence CVE CVE-2024-53195 https://www.cve.org/CVERecord?id=CVE-2024-53195 Référence CVE CVE-2024-53196 https://www.cve.org/CVERecord?id=CVE-2024-53196 Référence CVE CVE-2024-53210 https://www.cve.org/CVERecord?id=CVE-2024-53210 Référence CVE CVE-2024-53216 https://www.cve.org/CVERecord?id=CVE-2024-53216 Référence CVE CVE-2024-53219 https://www.cve.org/CVERecord?id=CVE-2024-53219 Référence CVE CVE-2024-53220 https://www.cve.org/CVERecord?id=CVE-2024-53220 Référence CVE CVE-2024-53221 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-53174 Référence CVE CVE-2024-53175 https://www.cve.org/CVERecord?id=CVE-2024-53175 Référence CVE CVE-2024-53176 https://www.cve.org/CVERecord?id=CVE-2024-53176 Référence CVE CVE-2024-53177 https://www.cve.org/CVERecord?id=CVE-2024-53177 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53180 https://www.cve.org/CVERecord?id=CVE-2024-53180 Référence CVE CVE-2024-53181 https://www.cve.org/CVERecord?id=CVE-2024-53181 Référence CVE CVE-2024-53183 https://www.cve.org/CVERecord?id=CVE-2024-53183 Référence CVE CVE-2024-53184 https://www.cve.org/CVERecord?id=CVE-2024-53184 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53188 https://www.cve.org/CVERecord?id=CVE-2024-53188 Référence CVE CVE-2024-53190 https://www.cve.org/CVERecord?id=CVE-2024-53190 Référence CVE CVE-2024-53191 https://www.cve.org/CVERecord?id=CVE-2024-53191 Référence CVE CVE-2024-53194 https://www.cve.org/CVERecord?id=CVE-2024-53194 Référence CVE CVE-2024-53195 https://www.cve.org/CVERecord?id=CVE-2024-53195 Référence CVE CVE-2024-53196 https://www.cve.org/CVERecord?id=CVE-2024-53196 Référence CVE CVE-2024-53197 https://www.cve.org/CVERecord?id=CVE-2024-53197 Référence CVE CVE-2024-53198 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53175 Référence CVE CVE-2024-53176 https://www.cve.org/CVERecord?id=CVE-2024-53176 Référence CVE CVE-2024-53177 https://www.cve.org/CVERecord?id=CVE-2024-53177 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53180 https://www.cve.org/CVERecord?id=CVE-2024-53180 Référence CVE CVE-2024-53181 https://www.cve.org/CVERecord?id=CVE-2024-53181 Référence CVE CVE-2024-53183 https://www.cve.org/CVERecord?id=CVE-2024-53183 Référence CVE CVE-2024-53184 https://www.cve.org/CVERecord?id=CVE-2024-53184 Référence CVE CVE-2024-53185 https://www.cve.org/CVERecord?id=CVE-2024-53185 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53188 https://www.cve.org/CVERecord?id=CVE-2024-53188 Référence CVE CVE-2024-53190 https://www.cve.org/CVERecord?id=CVE-2024-53190 Référence CVE CVE-2024-53191 https://www.cve.org/CVERecord?id=CVE-2024-53191 Référence CVE CVE-2024-53194 https://www.cve.org/CVERecord?id=CVE-2024-53194 Référence CVE CVE-2024-53195 https://www.cve.org/CVERecord?id=CVE-2024-53195 Référence CVE CVE-2024-53196 https://www.cve.org/CVERecord?id=CVE-2024-53196 Référence CVE CVE-2024-53197 https://www.cve.org/CVERecord?id=CVE-2024-53197 Référence CVE CVE-2024-53198 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-53174 Référence CVE CVE-2024-53175 https://www.cve.org/CVERecord?id=CVE-2024-53175 Référence CVE CVE-2024-53176 https://www.cve.org/CVERecord?id=CVE-2024-53176 Référence CVE CVE-2024-53177 https://www.cve.org/CVERecord?id=CVE-2024-53177 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53180 https://www.cve.org/CVERecord?id=CVE-2024-53180 Référence CVE CVE-2024-53181 https://www.cve.org/CVERecord?id=CVE-2024-53181 Référence CVE CVE-2024-53183 https://www.cve.org/CVERecord?id=CVE-2024-53183 Référence CVE CVE-2024-53184 https://www.cve.org/CVERecord?id=CVE-2024-53184 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53188 https://www.cve.org/CVERecord?id=CVE-2024-53188 Référence CVE CVE-2024-53189 https://www.cve.org/CVERecord?id=CVE-2024-53189 Référence CVE CVE-2024-53190 https://www.cve.org/CVERecord?id=CVE-2024-53190 Référence CVE CVE-2024-53191 https://www.cve.org/CVERecord?id=CVE-2024-53191 Référence CVE CVE-2024-53192 https://www.cve.org/CVERecord?id=CVE-2024-53192 Référence CVE CVE-2024-53193 https://www.cve.org/CVERecord?id=CVE-2024-53193 Référence CVE CVE-2024-53194 https://www.cve.org/CVERecord?id=CVE-2024-53194 Référence CVE CVE-2024-53195 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-53174 Référence CVE CVE-2024-53175 https://www.cve.org/CVERecord?id=CVE-2024-53175 Référence CVE CVE-2024-53176 https://www.cve.org/CVERecord?id=CVE-2024-53176 Référence CVE CVE-2024-53177 https://www.cve.org/CVERecord?id=CVE-2024-53177 Référence CVE CVE-2024-53178 https://www.cve.org/CVERecord?id=CVE-2024-53178 Référence CVE CVE-2024-53180 https://www.cve.org/CVERecord?id=CVE-2024-53180 Référence CVE CVE-2024-53181 https://www.cve.org/CVERecord?id=CVE-2024-53181 Référence CVE CVE-2024-53183 https://www.cve.org/CVERecord?id=CVE-2024-53183 Référence CVE CVE-2024-53184 https://www.cve.org/CVERecord?id=CVE-2024-53184 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53188 https://www.cve.org/CVERecord?id=CVE-2024-53188 Référence CVE CVE-2024-53189 https://www.cve.org/CVERecord?id=CVE-2024-53189 Référence CVE CVE-2024-53190 https://www.cve.org/CVERecord?id=CVE-2024-53190 Référence CVE CVE-2024-53191 https://www.cve.org/CVERecord?id=CVE-2024-53191 Référence CVE CVE-2024-53192 https://www.cve.org/CVERecord?id=CVE-2024-53192 Référence CVE CVE-2024-53193 https://www.cve.org/CVERecord?id=CVE-2024-53193 Référence CVE CVE-2024-53194 https://www.cve.org/CVERecord?id=CVE-2024-53194 Référence CVE CVE-2024-53195 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53169 Référence CVE CVE-2024-53170 https://www.cve.org/CVERecord?id=CVE-2024-53170 Référence CVE CVE-2024-53171 https://www.cve.org/CVERecord?id=CVE-2024-53171 Référence CVE CVE-2024-53172 https://www.cve.org/CVERecord?id=CVE-2024-53172 Référence CVE CVE-2024-53173 https://www.cve.org/CVERecord?id=CVE-2024-53173 Référence CVE CVE-2024-53174 https://www.cve.org/CVERecord?id=CVE-2024-53174 Référence CVE CVE-2024-53175 https://www.cve.org/CVERecord?id=CVE-2024-53175 Référence CVE CVE-2024-53177 https://www.cve.org/CVERecord?id=CVE-2024-53177 Référence CVE CVE-2024-53185 https://www.cve.org/CVERecord?id=CVE-2024-53185 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53194 https://www.cve.org/CVERecord?id=CVE-2024-53194 Référence CVE CVE-2024-53195 https://www.cve.org/CVERecord?id=CVE-2024-53195 Référence CVE CVE-2024-53196 https://www.cve.org/CVERecord?id=CVE-2024-53196 Référence CVE CVE-2024-53197 https://www.cve.org/CVERecord?id=CVE-2024-53197 Référence CVE CVE-2024-53198 https://www.cve.org/CVERecord?id=CVE-2024-53198 Référence CVE CVE-2024-53203 https://www.cve.org/CVERecord?id=CVE-2024-53203 Référence CVE CVE-2024-53208 https://www.cve.org/CVERecord?id=CVE-2024-53208 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53091 Référence CVE CVE-2024-53095 https://www.cve.org/CVERecord?id=CVE-2024-53095 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53164 https://www.cve.org/CVERecord?id=CVE-2024-53164 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53170 https://www.cve.org/CVERecord?id=CVE-2024-53170 Référence CVE CVE-2024-53172 https://www.cve.org/CVERecord?id=CVE-2024-53172 Référence CVE CVE-2024-53175 https://www.cve.org/CVERecord?id=CVE-2024-53175 Référence CVE CVE-2024-53185 https://www.cve.org/CVERecord?id=CVE-2024-53185 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53194 https://www.cve.org/CVERecord?id=CVE-2024-53194 Référence CVE CVE-2024-53195 https://www.cve.org/CVERecord?id=CVE-2024-53195 Référence CVE CVE-2024-53196 https://www.cve.org/CVERecord?id=CVE-2024-53196 Référence CVE CVE-2024-53197 https://www.cve.org/CVERecord?id=CVE-2024-53197 Référence CVE CVE-2024-53198 https://www.cve.org/CVERecord?id=CVE-2024-53198 Référence CVE CVE-2024-53203 https://www.cve.org/CVERecord?id=CVE-2024-53203 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-016843Linux の Linux Kernel における整数オーバーフローの脆弱性

Linux の Linux Kernel には、整数オーバーフローの脆弱性が存在します。

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.
Fix availability varies by product
Affected
Fixed
Linux: < 5.1, 6.1.191 ≤ 6.1.*, 6.6.160 ≤ 6.6.*, 6.11.11 ≤ 6.11.*, 6.12.2 ≤ 6.12.*, 6.13 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 27 Dec 2024 · Last source change 30 Oct 2026, 12:20 UTC · CWE-190 · Integer Overflow or Wraparound

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-51859
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    Linux: 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 1a0aecabff72a95d240e6d7645949bfe0620dcd7, 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 29eac3eca72d4c2a71122050c37cd7d8f73ac4f3, 2b188cc1bb857a9d4701ae59aa7768b5124e262e < aaa90844afd499c9142d0199dfda74439314c013, 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 0c0a4eae26ac78379d0c1db053de168a8febc6c9, 5.1 · Fixed: Linux: < 5.1, 6.6.160 ≤ 6.6.*, 6.11.11 ≤ 6.11.*, 6.12.2 ≤ 6.12.*, 6.13 ≤ *
    After
    Linux: 2b188cc1bb857a9d4701ae59aa7768b5124e262e < f1938217aee05be1c1dc53f581a3c353d033b508, 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 1a0aecabff72a95d240e6d7645949bfe0620dcd7, 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 29eac3eca72d4c2a71122050c37cd7d8f73ac4f3, 2b188cc1bb857a9d4701ae59aa7768b5124e262e < aaa90844afd499c9142d0199dfda74439314c013, 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 0c0a4eae26ac78379d0c1db053de168a8febc6c9, 5.1 · Fixed: Linux: < 5.1, 6.1.191 ≤ 6.1.*, 6.6.160 ≤ 6.6.*, 6.11.11 ≤ 6.11.*, 6.12.2 ≤ 6.12.*, 6.13 ≤ *
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    2b188cc1bb857a9d4701ae59aa7768b5124e262e < 29eac3eca72d4c2a71122050c37cd7d8f73ac4f3; 2b188cc1bb857a9d4701ae59aa7768b5124e262e < aaa90844afd499c9142d0199dfda74439314c013; 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 0c0a4eae26ac78379d0c1db053de168a8febc6c9; 5.1 · Fixed: < 5.1; 6.11.11 ≤ 6.11.*; 6.12.2 ≤ 6.12.*; 6.13 ≤ *
    After
    Linux: 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 1a0aecabff72a95d240e6d7645949bfe0620dcd7, 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 29eac3eca72d4c2a71122050c37cd7d8f73ac4f3, 2b188cc1bb857a9d4701ae59aa7768b5124e262e < aaa90844afd499c9142d0199dfda74439314c013, 2b188cc1bb857a9d4701ae59aa7768b5124e262e < 0c0a4eae26ac78379d0c1db053de168a8febc6c9, 5.1 · Fixed: Linux: < 5.1, 6.6.160 ≤ 6.6.*, 6.11.11 ≤ 6.11.*, 6.12.2 ≤ 6.12.*, 6.13 ≤ *
    CNA ↗
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-53187 · cve.blacktree.nl