Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.25% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2024
CVE-2024-46828High confidence
sched: sch_cake: fix bulk flow accounting logic for host fairness
Linux · Linux
7.1HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 18 structured product or package states 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 severityHigh→Operational priority:Medium, lowered one band.downgradedsince 5 Aug 2026
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 Linux Linux 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 18 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 3 affected or under-investigation product states without a fixed product state in the same current advisory
- Canonical Ubuntu Security: 15 affected package states with no published fix
Distribution package intelligence
19 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 15 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 release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | linux | Vendor fix publishedDebian records a fixed source-package version for this release. | 6.10.11-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. | 6.1.112-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. | 6.10.11-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. | 6.10.11-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | linux | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-aws | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-azure | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gcp | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gke | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-gkeop | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-ibm | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-lowlatency | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-nvidia-lowlatency | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-oem-6.8 | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-oracle | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-raspi | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-riscv | 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 |
| Ubuntu 24.04 LTSnoble · standard archive | linux-xilinx | 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
2 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-2024-46828 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: sched: sch_cake: fix bulk flow accounting logic for host fairness
The vendor explicitly identifies these products as affected by this CVE.
- kernel-rt as a component of Red Hat Enterprise Linux 9
- kernel-rt-core as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
- Summary
- A flaw was found in the `sch_cake` component of the Linux kernel. A local attacker could exploit a vulnerability in the bulk flow accounting logic, specifically during hash collision handling when host fairness is disabled. This can lead to an array out-of-bounds write due to a spurious decrement and wrap-around of a counter. If the `qdisc` (queueing discipline) is subsequently reconfigured to enable host fairness, the retained wrapped-around value is used as an array index, potentially causing a denial of service or information disclosure.
- 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.
SSA-355557 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-355557: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.2
The vendor explicitly identifies these products as affected by this CVE.
- RUGGEDCOM RST2428P (6GK6242-6PA00)
- SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
- SCALANCE XCM-/XRM-/XCH-/XRH-300 family
- Summary
- sched: sch_cake: fix bulk flow accounting logic for host fairness In sch_cake, we keep track of the count of active bulk flows per host, when running in dst/src host fairness mode, which is used as the round-robin weight when iterating through flows.
- Remediation
- Update to V3.2 or later version
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 18 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
In the Linux kernel, the following vulnerability has been resolved: sched: sch_cake: fix bulk flow accounting logic for host fairness In sch_cake, we keep track of the count of active bulk flows per host, when running in dst/src host fairness mode, which is used as the round-robin weight when iterating through flows. The count of active bulk flows is updated whenever a flow changes state. This has a peculiar interaction with the hash collision handling: when a hash collision occurs (after the set-associative hashing), the state of the hash bucket is simply updated to match the new packet that collided, and if host fairness is enabled, that also means assigning new per-host state to the flow. For this reason, the bulk flow counters of the host(s) assigned to the flow are decremented, before new state is assigned (and the counters, which may not belong to the same host anymore, are incremented again). Back when this code was introduced, the host fairness mode was always enabled, so the decrement was unconditional. When the configuration flags were introduced the *increment* was made conditional, but the *decrement* was not. Which of course can lead to a spurious decrement (and associated wrap-around to U16_MAX). AFAICT, when host fairness is disabled, the decrement and wrap-around happens as soon as a hash collision occurs (which is not that common in itself, due to the set-associative hashing). However, in most cases this is harmless, as the value is only used when host fairness mode is enabled. So in order to trigger an array overflow, sch_cake has to first be configured with host fairness disabled, and while running in this mode, a hash collision has to occur to cause the overflow. Then, the qdisc has to be reconfigured to enable host fairness, which leads to the array out-of-bounds because the wrapped-around value is retained and used as an array index. It seems that syzbot managed to trigger this, which is quite impressive in its own right. This patch fixes the issue by introducing the same conditional check on decrement as is used on increment. The original bug predates the upstreaming of cake, but the commit listed in the Fixes tag touched that code, meaning that this patch won't apply before that.
What
In the Linux kernel, the following vulnerability has been resolved: sched: sch_cake: fix bulk flow accounting logic for host fairness In sch_cake, we keep track of the count of active bulk flows per host, when running in dst/src host fairness mode, which is used as the round-robin weight when iterating through flows. The count of active bulk flows is updated whenever a flow changes state. This has a peculiar interaction with the hash collision handling: when a hash collision occurs (after the set-associative hashing), the state of the hash bucket is simply updated to match the new packet that collided, and if host fairness is enabled, that also means assigning new per-host state to the flow. For this reason, the bulk flow counters of the host(s) assigned to the flow are decremented, before new state is assigned (and the counters, which may not belong to the same host anymore, are incremented again). Back when this code was introduced, the host fairness mode was always enabled, so the decrement was unconditional. When the configuration flags were introduced the *increment* was made conditional, but the *decrement* was not. Which of course can lead to a spurious decrement (and associated wrap-around to U16_MAX). AFAICT, when host fairness is disabled, the decrement and wrap-around happens as soon as a hash collision occurs (which is not that common in itself, due to the set-associative hashing). However, in most cases this is harmless, as the value is only used when host fairness mode is enabled. So in order to trigger an array overflow, sch_cake has to first be configured with host fairness disabled, and while running in this mode, a hash collision has to occur to cause the overflow. Then, the qdisc has to be reconfigured to enable host fairness, which leads to the array out-of-bounds because the wrapped-around value is retained and used as an array index. It seems that syzbot managed to trigger this, which is quite impressive in its own right. This patch fixes the issue by introducing the same conditional check on decrement as is used on increment. The original bug predates the upstreaming of cake, but the commit listed in the Fixes tag touched that code, meaning that this patch won't apply before that.
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: sched: sch_cake: fix bulk flow accounting logic for host fairness In sch_cake, we keep track of the count of active bulk flows per host, when running in dst/src host fairness mode, which is used as the round-robin weight when iterating through flows. The count of active bulk flows is updated whenever a flow changes state. This has a peculiar interaction with the hash collision handling: when a hash collision occurs (after the set-associative hashing), the state of the hash bucket is simply updated to match the new packet that collided, and if host fairness is enabled, that also means assigning new per-host state to the flow. For this reason, the bulk flow counters of the host(s) assigned to the flow are decremented, before new state is assigned (and the counters, which may not belong to the same host anymore, are incremented again). Back when this code was introduced, the host fairness mode was always enabled, so the decrement was unconditional. When the configuration flags were introduced the *increment* was made conditional, but the *decrement* was not. Which of course can lead to a spurious decrement (and associated wrap-around to U16_MAX). AFAICT, when host fairness is disabled, the decrement and wrap-around happens as soon as a hash collision occurs (which is not that common in itself, due to the set-associative hashing). However, in most cases this is harmless, as the value is only used when host fairness mode is enabled. So in order to trigger an array overflow, sch_cake has to first be configured with host fairness disabled, and while running in this mode, a hash collision has to occur to cause the overflow. Then, the qdisc has to be reconfigured to enable host fairness, which leads to the array out-of-bounds because the wrapped-around value is retained and used as an array index. It seems that syzbot managed to trigger this, which is quite impressive in its own right. This patch fixes the issue by introducing the same conditional check on decrement as is used on increment. The original bug predates the upstreaming of cake, but the commit listed in the Fixes tag touched that code, meaning that this patch won't apply before that.
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 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 → 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:H/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.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.CHighConfidentiality impact: A successful attack can cause a major loss.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-rt as a component of Red Hat Enterprise Linux 9
- kernel-rt-core as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
- kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
- kernel-rt-devel as a component of Red Hat Enterprise Linux 9
- kernel-rt-devel-matched as a component of Red Hat Enterprise Linux 9
- kernel-rt-kvm as a component of Red Hat Enterprise Linux 9
- kernel-rt-modules as a component of Red Hat Enterprise Linux 9
- kernel-rt-modules-core as a component of Red Hat Enterprise Linux 9
- kernel-rt-modules-extra as a component of Red Hat Enterprise Linux 9
- kernel-rt-modules-internal as a component of Red Hat Enterprise Linux 9
- kernel-rt-modules-partner as a component of Red Hat Enterprise Linux 9
- kernel-rt-selftests-internal as a component of Red Hat Enterprise Linux 9
- kernel-rt.src as a component of Red Hat Enterprise Linux 9
- Fixed
- kernel-64k-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-64k-debug-devel-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-64k-debug-devel-matched-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-64k-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-64k-devel-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-64k-devel-matched-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-devel-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-devel-0:5.14.0-570.12.1.el9_6.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-devel-0:5.14.0-570.12.1.el9_6.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-devel-0:5.14.0-570.12.1.el9_6.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-devel-matched-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-devel-matched-0:5.14.0-570.12.1.el9_6.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-devel-matched-0:5.14.0-570.12.1.el9_6.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debug-devel-matched-0:5.14.0-570.12.1.el9_6.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debuginfo-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debuginfo-0:5.14.0-570.12.1.el9_6.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debuginfo-0:5.14.0-570.12.1.el9_6.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debuginfo-0:5.14.0-570.12.1.el9_6.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debuginfo-common-aarch64-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debuginfo-common-ppc64le-0:5.14.0-570.12.1.el9_6.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debuginfo-common-s390x-0:5.14.0-570.12.1.el9_6.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-debuginfo-common-x86_64-0:5.14.0-570.12.1.el9_6.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-devel-0:5.14.0-570.12.1.el9_6.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-devel-0:5.14.0-570.12.1.el9_6.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-devel-0:5.14.0-570.12.1.el9_6.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
- kernel-devel-0:5.14.0-570.12.1.el9_6.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- and 275 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 27 Sept 2024 · Last source change 5 Aug 2026, 11:38 UTC · CWE not yet assigned
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2024-42089
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
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.