BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2019
CVE-2019-19071High confidence

Affected product: Missing Release of Memory after Effective Lifetime

Unknown · Unknown

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state 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 severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 3.84% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown Unknown 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: Within 30 daysRemediation target: Within 180 days

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 1 structured product or package state 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.

5 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 1 affected package state 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.5.4.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.4.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.4.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.4.6-1Debian Security Tracker ↗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
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-2019-8710

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

A memory leak in the rsi_send_beacon() function in drivers/net/wireless/rsi/rsi_91x_mgmt.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering rsi_prepare_beacon() failures, aka CID-d563131ef23c.

What

A memory leak in the rsi_send_beacon() function in drivers/net/wireless/rsi/rsi_91x_mgmt.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering rsi_prepare_beacon() failures, aka CID-d563131ef23c.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

A memory leak in the rsi_send_beacon() function in drivers/net/wireless/rsi/rsi_91x_mgmt.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering rsi_prepare_beacon() failures, aka CID-d563131ef23c.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

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
a network path → Missing Release of Memory after Effective Lifetime → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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-401 ↗

CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-401
A

Official authority intelligence

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

BSI · German · WID-SEC-2023-0198Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

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

d?id=CVE-2019-19059 Référence CVE CVE-2019-19060 https://www.cve.org/CVERecord?id=CVE-2019-19060 Référence CVE CVE-2019-19061 https://www.cve.org/CVERecord?id=CVE-2019-19061 Référence CVE CVE-2019-19062 https://www.cve.org/CVERecord?id=CVE-2019-19062 Référence CVE CVE-2019-19063 https://www.cve.org/CVERecord?id=CVE-2019-19063 Référence CVE CVE-2019-19065 https://www.cve.org/CVERecord?id=CVE-2019-19065 Référence CVE CVE-2019-19066 https://www.cve.org/CVERecord?id=CVE-2019-19066 Référence CVE CVE-2019-19068 https://www.cve.org/CVERecord?id=CVE-2019-19068 Référence CVE CVE-2019-19069 https://www.cve.org/CVERecord?id=CVE-2019-19069 Référence CVE CVE-2019-19071 https://www.cve.org/CVERecord?id=CVE-2019-19071 Référence CVE CVE-2019-19072 https://www.cve.org/CVERecord?id=CVE-2019-19072 Référence CVE CVE-2019-19073 https://www.cve.org/CVERecord?id=CVE-2019-19073 Référence CVE CVE-2019-19074 https://www.cve.org/CVERecord?id=CVE-2019-19074 Référence CVE CVE-2019-19075 https://www.cve.org/CVERecord?id=CVE-2019-19075 Référence CVE CVE-2019-19076 https://www.cve.org/CVERecord?id=CVE-2019-19076 Référence CVE CVE-2019-19077 https://www.cve.org/CVERecord?id=CVE-2019-19077 Référence CVE CVE-2019-19078 https://www.cve.org/CVERecord?id=CVE-2019-19078 Référence CVE CVE-2019-19079 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2020-AVI-331Multiples vulnérabilités dans Google Android

d?id=CVE-2019-14076 Référence CVE CVE-2019-14080 https://www.cve.org/CVERecord?id=CVE-2019-14080 Référence CVE CVE-2019-14091 https://www.cve.org/CVERecord?id=CVE-2019-14091 Référence CVE CVE-2019-14092 https://www.cve.org/CVERecord?id=CVE-2019-14092 Référence CVE CVE-2019-14094 https://www.cve.org/CVERecord?id=CVE-2019-14094 Référence CVE CVE-2019-16275 https://www.cve.org/CVERecord?id=CVE-2019-16275 Référence CVE CVE-2019-17666 https://www.cve.org/CVERecord?id=CVE-2019-17666 Référence CVE CVE-2019-18683 https://www.cve.org/CVERecord?id=CVE-2019-18683 Référence CVE CVE-2019-18786 https://www.cve.org/CVERecord?id=CVE-2019-18786 Référence CVE CVE-2019-19071 https://www.cve.org/CVERecord?id=CVE-2019-19071 Référence CVE CVE-2019-19526 https://www.cve.org/CVERecord?id=CVE-2019-19526 Référence CVE CVE-2019-19529 https://www.cve.org/CVERecord?id=CVE-2019-19529 Référence CVE CVE-2019-19543 https://www.cve.org/CVERecord?id=CVE-2019-19543 Référence CVE CVE-2019-19767 https://www.cve.org/CVERecord?id=CVE-2019-19767 Référence CVE CVE-2019-2219 https://www.cve.org/CVERecord?id=CVE-2019-2219 Référence CVE CVE-2019-9460 https://www.cve.org/CVERecord?id=CVE-2019-9460 Référence CVE CVE-2020-0095 https://www.cve.org/CVERecord?id=CVE-2020-0095 Référence CVE CVE-2020-0113 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
CERT-FR · French · CERTFR-2020-AVI-096Multiples vulnérabilités dans le noyau linux d'Ubuntu

d?id=CVE-2019-18885 Référence CVE CVE-2019-19050 https://www.cve.org/CVERecord?id=CVE-2019-19050 Référence CVE CVE-2019-19051 https://www.cve.org/CVERecord?id=CVE-2019-19051 Référence CVE CVE-2019-19056 https://www.cve.org/CVERecord?id=CVE-2019-19056 Référence CVE CVE-2019-19057 https://www.cve.org/CVERecord?id=CVE-2019-19057 Référence CVE CVE-2019-19062 https://www.cve.org/CVERecord?id=CVE-2019-19062 Référence CVE CVE-2019-19063 https://www.cve.org/CVERecord?id=CVE-2019-19063 Référence CVE CVE-2019-19066 https://www.cve.org/CVERecord?id=CVE-2019-19066 Référence CVE CVE-2019-19068 https://www.cve.org/CVERecord?id=CVE-2019-19068 Référence CVE CVE-2019-19071 https://www.cve.org/CVERecord?id=CVE-2019-19071 Référence CVE CVE-2019-19077 https://www.cve.org/CVERecord?id=CVE-2019-19077 Référence CVE CVE-2019-19078 https://www.cve.org/CVERecord?id=CVE-2019-19078 Référence CVE CVE-2019-19082 https://www.cve.org/CVERecord?id=CVE-2019-19082 Référence CVE CVE-2019-19227 https://www.cve.org/CVERecord?id=CVE-2019-19227 Référence CVE CVE-2019-19241 https://www.cve.org/CVERecord?id=CVE-2019-19241 Référence CVE CVE-2019-19252 https://www.cve.org/CVERecord?id=CVE-2019-19252 Référence CVE CVE-2019-19332 https://www.cve.org/CVERecord?id=CVE-2019-19332 Référence CVE CVE-2019-19602 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, un déni de service et une atteinte à la confidentialité des données.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2019-012028Linux Kernel における有効期限後のメモリの解放の欠如に関する脆弱性

Linux Kernel には、有効期限後のメモリの解放の欠如に関する脆弱性が存在します。 ベンダは、本脆弱性を CID-d563131ef23c として公開しています。

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
n/a
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 18 Nov 2019 · Last source change 5 Aug 2024, 02:09 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

CVE recordCVE.org · 5.1
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-09-01
European sourceENISA EUVD · EUVD-2019-8710
Product sourceUnavailable
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. ENISA EUVD mappingEUVD-2019-8710 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2019-8710"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/d563131ef23cbc756026f839a82598c8445bc45f; added remediation: github.com/d563131ef23cbc756026f839a82598c8445bc45f; removed vendor advisory: lists.fedoraproject.org/O3PSDE6PTOTVBK2YTKB2TFQP2SUBVSNF; removed vendor advisory: lists.fedoraproject.org/PY7LJMSPAGRIKABJPDKQDTXYW3L5RX2T; 4 further removals.
    Before
    vendor advisory: lists.fedoraproject.org/O3PSDE6PTOTVBK2YTKB2TFQP2SUBVSNF · vendor advisory: lists.fedoraproject.org/PY7LJMSPAGRIKABJPDKQDTXYW3L5RX2T · vendor advisory: usn.ubuntu.com/4258-1 · 3 more references
    After
    patch: github.com/d563131ef23cbc756026f839a82598c8445bc45f · remediation: github.com/d563131ef23cbc756026f839a82598c8445bc45f
    github.com ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  4. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    github.com ↗
  5. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    NIST NVD ↗
  6. CVSS scoreCVSS score changed from not recorded to 7.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
    Before
    not recorded
    After
    7.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
    NIST NVD ↗
  7. Catalogue recordCVE added to the BlackTree catalogue.
    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-2019-19071 · cve.blacktree.nl