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

vsock: Update rx_bytes on read_skb()

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

19 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 Sept 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 record ↗Source updated 11 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 11 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 11 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 11 Sept 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 record ↗Source updated 11 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 11 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 11 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 11 Sept 2026
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-44671

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: vsock: Update rx_bytes on read_skb() Make sure virtio_transport_inc_rx_pkt() and virtio_transport_dec_rx_pkt() calls are balanced (i.e. virtio_vsock_sock::rx_bytes doesn't lie) after vsock_transport::read_skb(). While here, also inform the peer that we've freed up space and it has more credit. Failing to update rx_bytes after packet is dequeued leads to a warning on SOCK_STREAM recv(): [ 233.396654] rx_queue is empty, but rx_bytes is non-zero [ 233.396702] WARNING: CPU: 11 PID: 40601 at net/vmw_vsock/virtio_transport_common.c:589

What

In the Linux kernel, the following vulnerability has been resolved: vsock: Update rx_bytes on read_skb() Make sure virtio_transport_inc_rx_pkt() and virtio_transport_dec_rx_pkt() calls are balanced (i.e. virtio_vsock_sock::rx_bytes doesn't lie) after vsock_transport::read_skb(). While here, also inform the peer that we've freed up space and it has more credit. Failing to update rx_bytes after packet is dequeued leads to a warning on SOCK_STREAM recv(): [ 233.396654] rx_queue is empty, but rx_bytes is non-zero [ 233.396702] WARNING: CPU: 11 PID: 40601 at net/vmw_vsock/virtio_transport_common.c:589

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: vsock: Update rx_bytes on read_skb() Make sure virtio_transport_inc_rx_pkt() and virtio_transport_dec_rx_pkt() calls are balanced (i.e. virtio_vsock_sock::rx_bytes doesn't lie) after vsock_transport::read_skb(). While here, also inform the peer that we've freed up space and it has more credit. Failing to update rx_bytes after packet is dequeued leads to a warning on SOCK_STREAM recv(): [ 233.396654] rx_queue is empty, but rx_bytes is non-zero [ 233.396702] WARNING: CPU: 11 PID: 40601 at net/vmw_vsock/virtio_transport_common.c:589

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: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.
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-2855IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-3367Linux 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 nicht näher beschriebene Auswirkungen zu erzielen.

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

d?id=CVE-2024-50153 Référence CVE CVE-2024-50155 https://www.cve.org/CVERecord?id=CVE-2024-50155 Référence CVE CVE-2024-50157 https://www.cve.org/CVERecord?id=CVE-2024-50157 Référence CVE CVE-2024-50158 https://www.cve.org/CVERecord?id=CVE-2024-50158 Référence CVE CVE-2024-50160 https://www.cve.org/CVERecord?id=CVE-2024-50160 Référence CVE CVE-2024-50162 https://www.cve.org/CVERecord?id=CVE-2024-50162 Référence CVE CVE-2024-50163 https://www.cve.org/CVERecord?id=CVE-2024-50163 Référence CVE CVE-2024-50164 https://www.cve.org/CVERecord?id=CVE-2024-50164 Référence CVE CVE-2024-50165 https://www.cve.org/CVERecord?id=CVE-2024-50165 Référence CVE CVE-2024-50169 https://www.cve.org/CVERecord?id=CVE-2024-50169 Référence CVE CVE-2024-50172 https://www.cve.org/CVERecord?id=CVE-2024-50172 Référence CVE CVE-2024-50182 https://www.cve.org/CVERecord?id=CVE-2024-50182 Référence CVE CVE-2024-50186 https://www.cve.org/CVERecord?id=CVE-2024-50186 Référence CVE CVE-2024-50189 https://www.cve.org/CVERecord?id=CVE-2024-50189 Référence CVE CVE-2024-50197 https://www.cve.org/CVERecord?id=CVE-2024-50197 Référence CVE CVE-2024-50200 https://www.cve.org/CVERecord?id=CVE-2024-50200 Référence CVE CVE-2024-50207 https://www.cve.org/CVERecord?id=CVE-2024-50207 Référence CVE CVE-2024-50215 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-50158 Référence CVE CVE-2024-50159 https://www.cve.org/CVERecord?id=CVE-2024-50159 Référence CVE CVE-2024-50160 https://www.cve.org/CVERecord?id=CVE-2024-50160 Référence CVE CVE-2024-50162 https://www.cve.org/CVERecord?id=CVE-2024-50162 Référence CVE CVE-2024-50163 https://www.cve.org/CVERecord?id=CVE-2024-50163 Référence CVE CVE-2024-50164 https://www.cve.org/CVERecord?id=CVE-2024-50164 Référence CVE CVE-2024-50166 https://www.cve.org/CVERecord?id=CVE-2024-50166 Référence CVE CVE-2024-50167 https://www.cve.org/CVERecord?id=CVE-2024-50167 Référence CVE CVE-2024-50168 https://www.cve.org/CVERecord?id=CVE-2024-50168 Référence CVE CVE-2024-50169 https://www.cve.org/CVERecord?id=CVE-2024-50169 Référence CVE CVE-2024-50170 https://www.cve.org/CVERecord?id=CVE-2024-50170 Référence CVE CVE-2024-50171 https://www.cve.org/CVERecord?id=CVE-2024-50171 Référence CVE CVE-2024-50172 https://www.cve.org/CVERecord?id=CVE-2024-50172 Référence CVE CVE-2024-50179 https://www.cve.org/CVERecord?id=CVE-2024-50179 Référence CVE CVE-2024-50180 https://www.cve.org/CVERecord?id=CVE-2024-50180 Référence CVE CVE-2024-50182 https://www.cve.org/CVERecord?id=CVE-2024-50182 Référence CVE CVE-2024-50183 https://www.cve.org/CVERecord?id=CVE-2024-50183 Référence CVE CVE-2024-50184 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-50158 Référence CVE CVE-2024-50159 https://www.cve.org/CVERecord?id=CVE-2024-50159 Référence CVE CVE-2024-50160 https://www.cve.org/CVERecord?id=CVE-2024-50160 Référence CVE CVE-2024-50162 https://www.cve.org/CVERecord?id=CVE-2024-50162 Référence CVE CVE-2024-50163 https://www.cve.org/CVERecord?id=CVE-2024-50163 Référence CVE CVE-2024-50164 https://www.cve.org/CVERecord?id=CVE-2024-50164 Référence CVE CVE-2024-50166 https://www.cve.org/CVERecord?id=CVE-2024-50166 Référence CVE CVE-2024-50167 https://www.cve.org/CVERecord?id=CVE-2024-50167 Référence CVE CVE-2024-50168 https://www.cve.org/CVERecord?id=CVE-2024-50168 Référence CVE CVE-2024-50169 https://www.cve.org/CVERecord?id=CVE-2024-50169 Référence CVE CVE-2024-50170 https://www.cve.org/CVERecord?id=CVE-2024-50170 Référence CVE CVE-2024-50171 https://www.cve.org/CVERecord?id=CVE-2024-50171 Référence CVE CVE-2024-50172 https://www.cve.org/CVERecord?id=CVE-2024-50172 Référence CVE CVE-2024-50180 https://www.cve.org/CVERecord?id=CVE-2024-50180 Référence CVE CVE-2024-50182 https://www.cve.org/CVERecord?id=CVE-2024-50182 Référence CVE CVE-2024-50183 https://www.cve.org/CVERecord?id=CVE-2024-50183 Référence CVE CVE-2024-50184 https://www.cve.org/CVERecord?id=CVE-2024-50184 Référence CVE CVE-2024-50185 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-50160 Référence CVE CVE-2024-50161 https://www.cve.org/CVERecord?id=CVE-2024-50161 Référence CVE CVE-2024-50162 https://www.cve.org/CVERecord?id=CVE-2024-50162 Référence CVE CVE-2024-50163 https://www.cve.org/CVERecord?id=CVE-2024-50163 Référence CVE CVE-2024-50164 https://www.cve.org/CVERecord?id=CVE-2024-50164 Référence CVE CVE-2024-50165 https://www.cve.org/CVERecord?id=CVE-2024-50165 Référence CVE CVE-2024-50166 https://www.cve.org/CVERecord?id=CVE-2024-50166 Référence CVE CVE-2024-50167 https://www.cve.org/CVERecord?id=CVE-2024-50167 Référence CVE CVE-2024-50168 https://www.cve.org/CVERecord?id=CVE-2024-50168 Référence CVE CVE-2024-50169 https://www.cve.org/CVERecord?id=CVE-2024-50169 Référence CVE CVE-2024-50170 https://www.cve.org/CVERecord?id=CVE-2024-50170 Référence CVE CVE-2024-50171 https://www.cve.org/CVERecord?id=CVE-2024-50171 Référence CVE CVE-2024-50172 https://www.cve.org/CVERecord?id=CVE-2024-50172 Référence CVE CVE-2024-50173 https://www.cve.org/CVERecord?id=CVE-2024-50173 Référence CVE CVE-2024-50174 https://www.cve.org/CVERecord?id=CVE-2024-50174 Référence CVE CVE-2024-50175 https://www.cve.org/CVERecord?id=CVE-2024-50175 Référence CVE CVE-2024-50176 https://www.cve.org/CVERecord?id=CVE-2024-50176 Référence CVE CVE-2024-50177 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-50160 Référence CVE CVE-2024-50161 https://www.cve.org/CVERecord?id=CVE-2024-50161 Référence CVE CVE-2024-50162 https://www.cve.org/CVERecord?id=CVE-2024-50162 Référence CVE CVE-2024-50163 https://www.cve.org/CVERecord?id=CVE-2024-50163 Référence CVE CVE-2024-50164 https://www.cve.org/CVERecord?id=CVE-2024-50164 Référence CVE CVE-2024-50165 https://www.cve.org/CVERecord?id=CVE-2024-50165 Référence CVE CVE-2024-50166 https://www.cve.org/CVERecord?id=CVE-2024-50166 Référence CVE CVE-2024-50167 https://www.cve.org/CVERecord?id=CVE-2024-50167 Référence CVE CVE-2024-50168 https://www.cve.org/CVERecord?id=CVE-2024-50168 Référence CVE CVE-2024-50169 https://www.cve.org/CVERecord?id=CVE-2024-50169 Référence CVE CVE-2024-50170 https://www.cve.org/CVERecord?id=CVE-2024-50170 Référence CVE CVE-2024-50171 https://www.cve.org/CVERecord?id=CVE-2024-50171 Référence CVE CVE-2024-50172 https://www.cve.org/CVERecord?id=CVE-2024-50172 Référence CVE CVE-2024-50173 https://www.cve.org/CVERecord?id=CVE-2024-50173 Référence CVE CVE-2024-50174 https://www.cve.org/CVERecord?id=CVE-2024-50174 Référence CVE CVE-2024-50176 https://www.cve.org/CVERecord?id=CVE-2024-50176 Référence CVE CVE-2024-50177 https://www.cve.org/CVERecord?id=CVE-2024-50177 Référence CVE CVE-2024-50178 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50154 Référence CVE CVE-2024-50155 https://www.cve.org/CVERecord?id=CVE-2024-50155 Référence CVE CVE-2024-50156 https://www.cve.org/CVERecord?id=CVE-2024-50156 Référence CVE CVE-2024-50157 https://www.cve.org/CVERecord?id=CVE-2024-50157 Référence CVE CVE-2024-50158 https://www.cve.org/CVERecord?id=CVE-2024-50158 Référence CVE CVE-2024-50159 https://www.cve.org/CVERecord?id=CVE-2024-50159 Référence CVE CVE-2024-50160 https://www.cve.org/CVERecord?id=CVE-2024-50160 Référence CVE CVE-2024-50166 https://www.cve.org/CVERecord?id=CVE-2024-50166 Référence CVE CVE-2024-50167 https://www.cve.org/CVERecord?id=CVE-2024-50167 Référence CVE CVE-2024-50169 https://www.cve.org/CVERecord?id=CVE-2024-50169 Référence CVE CVE-2024-50171 https://www.cve.org/CVERecord?id=CVE-2024-50171 Référence CVE CVE-2024-50172 https://www.cve.org/CVERecord?id=CVE-2024-50172 Référence CVE CVE-2024-50175 https://www.cve.org/CVERecord?id=CVE-2024-50175 Référence CVE CVE-2024-50176 https://www.cve.org/CVERecord?id=CVE-2024-50176 Référence CVE CVE-2024-50177 https://www.cve.org/CVERecord?id=CVE-2024-50177 Référence CVE CVE-2024-50179 https://www.cve.org/CVERecord?id=CVE-2024-50179 Référence CVE CVE-2024-50180 https://www.cve.org/CVERecord?id=CVE-2024-50180 Référence CVE CVE-2024-50181 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-013315Linux の 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.
Patch available
Affected
Linux: 634f1a7110b439c65fd8a809171c1d2d28bcea6f < 66cd51de31c682a311c2fa25c580b7ea45859dd9, 634f1a7110b439c65fd8a809171c1d2d28bcea6f < e5ca2b98090b4bb1c393088c724af6c37812a829, 634f1a7110b439c65fd8a809171c1d2d28bcea6f < 3543152f2d330141d9394d28855cb90b860091d2, 6.4
Fixed
Linux: < 6.4, 6.6.59 ≤ 6.6.*, 6.11.6 ≤ 6.11.*, 6.12 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 7 Nov 2024 · Last source change 11 May 2026, 20:46 UTC · CWE not yet assigned

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-44671
Product sourceCNA
Remediation sourceCVE/CNA references
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-50169 · cve.blacktree.nl