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

usb: typec: tipd: Free IRQ only if it was requested before

Linux · Linux

3.3LowCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Low 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 severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.21% 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.11.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 6 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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 5 Oct 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-50057 · CSAF 2.0 · revision 31 · interimSUSE Product Security TeamCVE-2024-50057
498 known not affected

The vendor explicitly states that these products are not 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-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-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-macros 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 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tipd: Free IRQ only if it was requested before In polling mode, if no IRQ was requested there is no need to free it. Call devm_free_irq() only if client->irq is set. This fixes the warning caused by the tps6598x module removal: WARNING: CPU: 2 PID: 333 at kernel/irq/devres.c:144 devm_free_irq+0x80/0x8c ... ... Call trace: devm_free_irq+0x80/0x8c tps6598x_remove+0x28/0x88 [tps6598x] i2c_device_remove+0x2c/0x9c device_remove+0x4c/0x80 device_release_driver_internal+0x1cc/0x228 driver_detach+0x50/0x98 bus_remove_driver+0x6c/0xbc driver_unregister+0x30/0x60 i2c_del_driver+0x54/0x64 tps6598x_i2c_driver_exit+0x18/0xc3c [tps6598x] __arm64_sys_delete_module+0x184/0x264 invoke_syscall+0x48/0x110 el0_svc_common.constprop.0+0xc8/0xe8 do_el0_svc+0x20/0x2c el0_svc+0x28/0x98 el0t_64_sync_handler+0x13c/0x158 el0t_64_sync+0x190/0x194
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2024-50057 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: usb: typec: tipd: Free IRQ only if it was requested before
70 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 8
  • kernel as a component of Red Hat Enterprise Linux 8
  • kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8
  • kernel-core as a component of Red Hat Enterprise Linux 8
  • kernel-cross-headers as a component of Red Hat Enterprise Linux 8
  • kernel-debug as a component of Red Hat Enterprise Linux 8
  • kernel-debug-core as a component of Red Hat Enterprise Linux 8
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8
Summary
A flaw was found in the Linux kernel's USB Type-C (tipd) driver. When the tps6598x module is removed, the system attempts to free an Interrupt Request (IRQ) even if one was not previously allocated. This improper resource handling can lead to a system warning and potential instability, which may result in a denial of service.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-44809

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 actionPatch only the product branches with a verified fix

Low 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: usb: typec: tipd: Free IRQ only if it was requested before In polling mode, if no IRQ was requested there is no need to free it. Call devm_free_irq() only if client->irq is set. This fixes the warning caused by the tps6598x module removal: WARNING: CPU: 2 PID: 333 at kernel/irq/devres.c:144 devm_free_irq+0x80/0x8c ... ... Call trace: devm_free_irq+0x80/0x8c tps6598x_remove+0x28/0x88 [tps6598x] i2c_device_remove+0x2c/0x9c device_remove+0x4c/0x80 device_release_driver_internal+0x1cc/0x228 driver_detach+0x50/0x98 bus_remove_driver+0x6c/0xbc driver_unregister+0x30/0x60 i2c_del_driver+0x54/0x64 tps6598x_i2c_driver_exit+0x18/0xc3c [tps6598x] __arm64_sys_delete_module+0x184/0x264 invoke_syscall+0x48/0x110 el0_svc_common.constprop.0+0xc8/0xe8 do_el0_svc+0x20/0x2c el0_svc+0x28/0x98 el0t_64_sync_handler+0x13c/0x158 el0t_64_sync+0x190/0x194

What

In the Linux kernel, the following vulnerability has been resolved: usb: typec: tipd: Free IRQ only if it was requested before In polling mode, if no IRQ was requested there is no need to free it. Call devm_free_irq() only if client->irq is set. This fixes the warning caused by the tps6598x module removal: WARNING: CPU: 2 PID: 333 at kernel/irq/devres.c:144 devm_free_irq+0x80/0x8c ... ... Call trace: devm_free_irq+0x80/0x8c tps6598x_remove+0x28/0x88 [tps6598x] i2c_device_remove+0x2c/0x9c device_remove+0x4c/0x80 device_release_driver_internal+0x1cc/0x228 driver_detach+0x50/0x98 bus_remove_driver+0x6c/0xbc driver_unregister+0x30/0x60 i2c_del_driver+0x54/0x64 tps6598x_i2c_driver_exit+0x18/0xc3c [tps6598x] __arm64_sys_delete_module+0x184/0x264 invoke_syscall+0x48/0x110 el0_svc_common.constprop.0+0xc8/0xe8 do_el0_svc+0x20/0x2c el0_svc+0x28/0x98 el0t_64_sync_handler+0x13c/0x158 el0t_64_sync+0x190/0x194

Why

The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.

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: usb: typec: tipd: Free IRQ only if it was requested before In polling mode, if no IRQ was requested there is no need to free it. Call devm_free_irq() only if client->irq is set. This fixes the warning caused by the tps6598x module removal: WARNING: CPU: 2 PID: 333 at kernel/irq/devres.c:144 devm_free_irq+0x80/0x8c ... ... Call trace: devm_free_irq+0x80/0x8c tps6598x_remove+0x28/0x88 [tps6598x] i2c_device_remove+0x2c/0x9c device_remove+0x4c/0x80 device_release_driver_internal+0x1cc/0x228 driver_detach+0x50/0x98 bus_remove_driver+0x6c/0xbc driver_unregister+0x30/0x60 i2c_del_driver+0x54/0x64 tps6598x_i2c_driver_exit+0x18/0xc3c [tps6598x] __arm64_sys_delete_module+0x184/0x264 invoke_syscall+0x48/0x110 el0_svc_common.constprop.0+0xc8/0xe8 do_el0_svc+0x20/0x2c el0_svc+0x28/0x98 el0t_64_sync_handler+0x13c/0x158 el0t_64_sync+0x190/0x194

Why

The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.

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 → Release of Invalid Pointer or Reference → 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-763 ↗

CWE-763: Release of Invalid Pointer or Reference. The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.

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:L

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.ALowAvailability impact: A successful attack can cause a limited 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-763
A

Official authority intelligence

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

BSI · German · WID-SEC-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 ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241023Security Bulletin 23 Oct 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 23 Oct 2024, published on 23 October 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2024-49994 Référence CVE CVE-2024-50009 https://www.cve.org/CVERecord?id=CVE-2024-50009 Référence CVE CVE-2024-50012 https://www.cve.org/CVERecord?id=CVE-2024-50012 Référence CVE CVE-2024-50014 https://www.cve.org/CVERecord?id=CVE-2024-50014 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-50028 https://www.cve.org/CVERecord?id=CVE-2024-50028 Référence CVE CVE-2024-50034 https://www.cve.org/CVERecord?id=CVE-2024-50034 Référence CVE CVE-2024-50048 https://www.cve.org/CVERecord?id=CVE-2024-50048 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50098 https://www.cve.org/CVERecord?id=CVE-2024-50098 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50112 https://www.cve.org/CVERecord?id=CVE-2024-50112 Référence CVE CVE-2024-50135 https://www.cve.org/CVERecord?id=CVE-2024-50135 Référence CVE CVE-2024-50138 https://www.cve.org/CVERecord?id=CVE-2024-50138 Référence CVE CVE-2024-50146 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-49994 Référence CVE CVE-2024-50009 https://www.cve.org/CVERecord?id=CVE-2024-50009 Référence CVE CVE-2024-50012 https://www.cve.org/CVERecord?id=CVE-2024-50012 Référence CVE CVE-2024-50014 https://www.cve.org/CVERecord?id=CVE-2024-50014 Référence CVE CVE-2024-50017 https://www.cve.org/CVERecord?id=CVE-2024-50017 Référence CVE CVE-2024-50028 https://www.cve.org/CVERecord?id=CVE-2024-50028 Référence CVE CVE-2024-50034 https://www.cve.org/CVERecord?id=CVE-2024-50034 Référence CVE CVE-2024-50048 https://www.cve.org/CVERecord?id=CVE-2024-50048 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50098 https://www.cve.org/CVERecord?id=CVE-2024-50098 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50112 https://www.cve.org/CVERecord?id=CVE-2024-50112 Référence CVE CVE-2024-50135 https://www.cve.org/CVERecord?id=CVE-2024-50135 Référence CVE CVE-2024-50138 https://www.cve.org/CVERecord?id=CVE-2024-50138 Référence CVE CVE-2024-50146 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-50044 Référence CVE CVE-2024-50045 https://www.cve.org/CVERecord?id=CVE-2024-50045 Référence CVE CVE-2024-50046 https://www.cve.org/CVERecord?id=CVE-2024-50046 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=CVE-2024-50047 Référence CVE CVE-2024-50048 https://www.cve.org/CVERecord?id=CVE-2024-50048 Référence CVE CVE-2024-50049 https://www.cve.org/CVERecord?id=CVE-2024-50049 Référence CVE CVE-2024-50051 https://www.cve.org/CVERecord?id=CVE-2024-50051 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50065 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-50044 Référence CVE CVE-2024-50045 https://www.cve.org/CVERecord?id=CVE-2024-50045 Référence CVE CVE-2024-50046 https://www.cve.org/CVERecord?id=CVE-2024-50046 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=CVE-2024-50047 Référence CVE CVE-2024-50048 https://www.cve.org/CVERecord?id=CVE-2024-50048 Référence CVE CVE-2024-50049 https://www.cve.org/CVERecord?id=CVE-2024-50049 Référence CVE CVE-2024-50051 https://www.cve.org/CVERecord?id=CVE-2024-50051 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50065 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-50044 Référence CVE CVE-2024-50045 https://www.cve.org/CVERecord?id=CVE-2024-50045 Référence CVE CVE-2024-50046 https://www.cve.org/CVERecord?id=CVE-2024-50046 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=CVE-2024-50047 Référence CVE CVE-2024-50048 https://www.cve.org/CVERecord?id=CVE-2024-50048 Référence CVE CVE-2024-50049 https://www.cve.org/CVERecord?id=CVE-2024-50049 Référence CVE CVE-2024-50051 https://www.cve.org/CVERecord?id=CVE-2024-50051 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50065 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-50043 Référence CVE CVE-2024-50044 https://www.cve.org/CVERecord?id=CVE-2024-50044 Référence CVE CVE-2024-50045 https://www.cve.org/CVERecord?id=CVE-2024-50045 Référence CVE CVE-2024-50046 https://www.cve.org/CVERecord?id=CVE-2024-50046 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=CVE-2024-50047 Référence CVE CVE-2024-50048 https://www.cve.org/CVERecord?id=CVE-2024-50048 Référence CVE CVE-2024-50049 https://www.cve.org/CVERecord?id=CVE-2024-50049 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50065 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-50043 Référence CVE CVE-2024-50044 https://www.cve.org/CVERecord?id=CVE-2024-50044 Référence CVE CVE-2024-50045 https://www.cve.org/CVERecord?id=CVE-2024-50045 Référence CVE CVE-2024-50046 https://www.cve.org/CVERecord?id=CVE-2024-50046 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=CVE-2024-50047 Référence CVE CVE-2024-50048 https://www.cve.org/CVERecord?id=CVE-2024-50048 Référence CVE CVE-2024-50049 https://www.cve.org/CVERecord?id=CVE-2024-50049 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50057 https://www.cve.org/CVERecord?id=CVE-2024-50057 Référence CVE CVE-2024-50058 https://www.cve.org/CVERecord?id=CVE-2024-50058 Référence CVE CVE-2024-50059 https://www.cve.org/CVERecord?id=CVE-2024-50059 Référence CVE CVE-2024-50060 https://www.cve.org/CVERecord?id=CVE-2024-50060 Référence CVE CVE-2024-50061 https://www.cve.org/CVERecord?id=CVE-2024-50061 Référence CVE CVE-2024-50062 https://www.cve.org/CVERecord?id=CVE-2024-50062 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2024-50064 https://www.cve.org/CVERecord?id=CVE-2024-50064 Référence CVE CVE-2024-50065 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-011144Linux の 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
Linux: 0a4c005bd1715d8b32a368ed5516a6ee7e603d18 < b72bf5cade51ba4055c8a8998d275e72e6b521ce, 0a4c005bd1715d8b32a368ed5516a6ee7e603d18 < 4d4b23c119542fbaed2a16794d3801cb4806ea02, 0a4c005bd1715d8b32a368ed5516a6ee7e603d18 < db63d9868f7f310de44ba7bea584e2454f8b4ed0, 4.15
Fixed
Linux: < 4.15, 6.6.57 ≤ 6.6.*, 6.11.4 ≤ 6.11.*, 6.12 ≤ *
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 21 Oct 2024 · Last source change 11 May 2026, 20:44 UTC · CWE-763 · Release of Invalid Pointer or Reference

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-44809
Product sourceCNA
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

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

Material change intelligence

What changed after publication

View recent updates ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-50057 · cve.blacktree.nl