Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.63% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2019
CVE-2019-19062High confidence
Affected product: Missing Release of Memory after Effective Lifetime
Unknown · Unknown
4.7MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium 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 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Low, lowered one band.downgradedsince 5 Aug 2024
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
- Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
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.
- Canonical Ubuntu Security: 1 affected package state with no published fix
Distribution package intelligence
5 package statesRelease-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.
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 release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.4.6-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.4.6-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.4.6-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.4.6-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-raspi-realtime | Affected, 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 feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative 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.
CVE-2019-19062 · CSAF 2.0 · revision 46 · interimSUSE Product Security TeamCVE-2019-19062
The vendor explicitly identifies these products as affected by this CVE.
- kernel-default as component of HPE Helion OpenStack 8
- kernel-default-base as component of HPE Helion OpenStack 8
- kernel-default-devel as component of HPE Helion OpenStack 8
- kernel-default-kgraft as component of HPE Helion OpenStack 8
- kernel-devel as component of HPE Helion OpenStack 8
- kernel-macros as component of HPE Helion OpenStack 8
- kernel-source as component of HPE Helion OpenStack 8
- kernel-source-azure as component of HPE Helion OpenStack 8
- kernel-default as component of SUSE CaaS Platform 4.0
- kernel-default-base as component of SUSE CaaS Platform 4.0
- kernel-default-devel as component of SUSE CaaS Platform 4.0
- kernel-devel as component of SUSE CaaS Platform 4.0
- Summary
- A memory leak in the crypto_report() function in crypto/crypto_user_base.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering crypto_report_alg() failures, aka CID-ffdde5932042.
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
A memory leak in the crypto_report() function in crypto/crypto_user_base.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering crypto_report_alg() failures, aka CID-ffdde5932042.
What
A memory leak in the crypto_report() function in crypto/crypto_user_base.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering crypto_report_alg() failures, aka CID-ffdde5932042.
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 local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.
What
A memory leak in the crypto_report() function in crypto/crypto_user_base.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering crypto_report_alg() failures, aka CID-ffdde5932042.
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 local access may attempt exploitation with low privileges. 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 No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 → Missing Release of Memory after Effective Lifetime → disrupt the affected service
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- 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:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:HCommon 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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.
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
- kernel-default as component of HPE Helion OpenStack 8
- kernel-default-base as component of HPE Helion OpenStack 8
- kernel-default-devel as component of HPE Helion OpenStack 8
- kernel-default-kgraft as component of HPE Helion OpenStack 8
- kernel-devel as component of HPE Helion OpenStack 8
- kernel-macros as component of HPE Helion OpenStack 8
- kernel-source as component of HPE Helion OpenStack 8
- kernel-source-azure as component of HPE Helion OpenStack 8
- kernel-default as component of SUSE CaaS Platform 4.0
- kernel-default-base as component of SUSE CaaS Platform 4.0
- kernel-default-devel as component of SUSE CaaS Platform 4.0
- kernel-devel as component of SUSE CaaS Platform 4.0
- kernel-macros as component of SUSE CaaS Platform 4.0
- kernel-source as component of SUSE CaaS Platform 4.0
- reiserfs-kmp-default as component of SUSE CaaS Platform 4.0
- kernel-default as component of SUSE Enterprise Storage 6
- kernel-source as component of SUSE Enterprise Storage 6
- kernel-source-azure as component of SUSE Enterprise Storage 6
- kernel-source-azure as component of SUSE Enterprise Storage 7
- kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-source-azure as component of SUSE Linux Enterprise High Performance Computing 12 SP4
- kernel-devel-azure as component of SUSE Linux Enterprise High Performance Computing 12 SP5
- kernel-source-azure as component of SUSE Linux Enterprise High Performance Computing 12 SP5
- kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1-LTSS
- and 131 more
- 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 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 FIRST · tracked since 2026-09-01
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2019-8701
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2019-8701 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2019-8701"}
- Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/ffdde5932042600c6807d46c1550b28b0db6a3bc; added remediation: github.com/ffdde5932042600c6807d46c1550b28b0db6a3bc; removed vendor advisory: lists.fedoraproject.org/O3PSDE6PTOTVBK2YTKB2TFQP2SUBVSNF; removed vendor advisory: lists.fedoraproject.org/PY7LJMSPAGRIKABJPDKQDTXYW3L5RX2T; 7 further removals.github.com ↗
- Before
- vendor advisory: lists.fedoraproject.org/O3PSDE6PTOTVBK2YTKB2TFQP2SUBVSNF · vendor advisory: lists.fedoraproject.org/PY7LJMSPAGRIKABJPDKQDTXYW3L5RX2T · vendor advisory: lists.opensuse.org/msg00029.html · 6 more references
- After
- patch: github.com/ffdde5932042600c6807d46c1550b28b0db6a3bc · remediation: github.com/ffdde5932042600c6807d46c1550b28b0db6a3bc
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- 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.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.github.com ↗
- Before
- Awaiting fix
- After
- Patch available
- SeveritySeverity changed from Unknown to Medium.NIST NVD ↗
- Before
- Unknown
- After
- Medium
- CVSS scoreCVSS score changed from not recorded to 4.7 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H).NIST NVD ↗
- Before
- not recorded
- After
- 4.7 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H)
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release or patch reference recorded
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.